Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1102621 > unrolled thread

Bug#1010755: qbs: FTBFS on riscv64

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1010755: qbs: FTBFS on riscv64 Bo YU <tsu.yubo@gmail.com> - 2022-05-09 12:00 +0200
    Bug#1010755: qbs: FTBFS on riscv64 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> - 2022-05-09 15:30 +0200
      Bug#1010755: qbs: FTBFS on riscv64 Bo YU <tsu.yubo@gmail.com> - 2022-05-09 16:40 +0200
        Bug#1010755: qbs: FTBFS on riscv64 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> - 2022-05-09 17:00 +0200
          Bug#1010755: qbs: FTBFS on riscv64 Lisandro Damián Nicanor Pérez Meyer <perezmeyer@gmail.com> - 2022-05-10 04:00 +0200

#1102621 — Bug#1010755: qbs: FTBFS on riscv64

Package: qbs
Version: 1.22.1-1
Severity: normal
User: debian-riscv@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-riscv@lists.debian.org, riscv64@buildd.debian.org

Dear Maintainer,

It is odd that the build fails on riscv64 arch from buildd:

```
...
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below
dpkg-gensymbols: warning: debian/libqbscore1.22/DEBIAN/symbols doesn't match completely debian/libqbscore1.22.symbols
--- debian/libqbscore1.22.symbols (libqbscore1.22_1.22.1-1_riscv64)
+++ dpkg-gensymbols8XkRIb	2022-05-07 10:47:44.042026568 +0000
@@ -3334,7 +3334,7 @@
(optional=templinst)_ZN5QListISt10shared_ptrIN3qbs8Internal17DependencyScannerEEEC1ERKS5_@Base 1.22.0
(optional=templinst)_ZN5QListISt10shared_ptrIN3qbs8Internal17DependencyScannerEEEC2ERKS5_@Base 1.22.0
_ZN6QDebuglsEPKc@Base 1.22.0
- _ZN6QDebuglsERK7QString@Base 1.22.0
+#MISSING: 1.22.1-1# _ZN6QDebuglsERK7QString@Base 1.22.0
_ZN7QStringD1Ev@Base 1.22.0
_ZN7QStringD2Ev@Base 1.22.0
(optional=templinst)_ZN7QVectorISt10shared_ptrIN3qbs8Internal15ResolvedProductEEE6appendERKS4_@Base 1.22.0
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:13: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2
```

The full buildd log is here:
https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=riscv64&ver=1.22.1-1&stamp=1651920477&raw=0

But I want to fix it on locally and build it on riscv64 hardware without any modifies:

```
...
I: Lintian run was successful.

+------------------------------------------------------------------------------+
| Post Build                                                                   |
+------------------------------------------------------------------------------+


+------------------------------------------------------------------------------+
| Cleanup                                                                      |
+------------------------------------------------------------------------------+

Purging /<<BUILDDIR>>
Not cleaning session: cloned chroot in use

+------------------------------------------------------------------------------+
| Summary                                                                      |
+------------------------------------------------------------------------------+

Build Architecture: riscv64
Build Type: binary
Build-Space: 1656292
Build-Time: 4321
Distribution: sid-riscv64-sbuild
Host Architecture: riscv64
Install-Time: 209
Job: /home/vimer/05/143_qbs/qbs_1.22.0-4.dsc
Lintian: warn
Machine Architecture: riscv64
Package: qbs
Package-Time: 4640
Source-Version: 1.22.0-4
Space: 1656292
Status: successful
Version: 1.22.0-4
--------------------------------------------------------------------------------
Finished at 2022-05-09T09:26:26Z
Build needed 01:17:20, 1656292k disk space
```
The reason for this result may be similar to:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010509

Anyway, if you need me to do more tests on riscv64 hardware, please tell me

BR,
Bo

[toc] | [next] | [standalone]

#1102632

Hello Bo!

On 5/9/22 11:52, Bo YU wrote:
> ```
> ...
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below
> dpkg-gensymbols: warning: debian/libqbscore1.22/DEBIAN/symbols doesn't match completely debian/libqbscore1.22.symbols
> --- debian/libqbscore1.22.symbols (libqbscore1.22_1.22.1-1_riscv64)
> +++ dpkg-gensymbols8XkRIb	2022-05-07 10:47:44.042026568 +0000
> @@ -3334,7 +3334,7 @@
> (optional=templinst)_ZN5QListISt10shared_ptrIN3qbs8Internal17DependencyScannerEEEC1ERKS5_@Base 1.22.0
> (optional=templinst)_ZN5QListISt10shared_ptrIN3qbs8Internal17DependencyScannerEEEC2ERKS5_@Base 1.22.0
> _ZN6QDebuglsEPKc@Base 1.22.0
> - _ZN6QDebuglsERK7QString@Base 1.22.0
> +#MISSING: 1.22.1-1# _ZN6QDebuglsERK7QString@Base 1.22.0
> _ZN7QStringD1Ev@Base 1.22.0
> _ZN7QStringD2Ev@Base 1.22.0
> (optional=templinst)_ZN7QVectorISt10shared_ptrIN3qbs8Internal15ResolvedProductEEE6appendERKS4_@Base 1.22.0
> dh_makeshlibs: error: failing due to earlier errors
> make: *** [debian/rules:13: binary-arch] Error 25
> dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2
> ```

This error just means that the symbols file(s) have to be updated, see [1].

Adrian

> [1] https://wiki.debian.org/UsingSymbolsFiles

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

[toc] | [prev] | [next] | [standalone]

#1102633

Hi John,

On Mon, May 9, 2022 at 9:22 PM John Paul Adrian Glaubitz
<glaubitz@physik.fu-berlin.de> wrote:
>
> Hello Bo!
>
> On 5/9/22 11:52, Bo YU wrote:
> > ```
> > ...
> > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below
> > dpkg-gensymbols: warning: debian/libqbscore1.22/DEBIAN/symbols doesn't match completely debian/libqbscore1.22.symbols
> > --- debian/libqbscore1.22.symbols (libqbscore1.22_1.22.1-1_riscv64)
> > +++ dpkg-gensymbols8XkRIb     2022-05-07 10:47:44.042026568 +0000
> > @@ -3334,7 +3334,7 @@
> > (optional=templinst)_ZN5QListISt10shared_ptrIN3qbs8Internal17DependencyScannerEEEC1ERKS5_@Base 1.22.0
> > (optional=templinst)_ZN5QListISt10shared_ptrIN3qbs8Internal17DependencyScannerEEEC2ERKS5_@Base 1.22.0
> > _ZN6QDebuglsEPKc@Base 1.22.0
> > - _ZN6QDebuglsERK7QString@Base 1.22.0
> > +#MISSING: 1.22.1-1# _ZN6QDebuglsERK7QString@Base 1.22.0
> > _ZN7QStringD1Ev@Base 1.22.0
> > _ZN7QStringD2Ev@Base 1.22.0
> > (optional=templinst)_ZN7QVectorISt10shared_ptrIN3qbs8Internal15ResolvedProductEEE6appendERKS4_@Base 1.22.0
> > dh_makeshlibs: error: failing due to earlier errors
> > make: *** [debian/rules:13: binary-arch] Error 25
> > dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2
> > ```
>
> This error just means that the symbols file(s) have to be updated, see [1].
>
Before I filed the bug, I realized the ftbfs issue might be with the
symbols file as you point.
`apt source qbs` and the debian/symbols file has the symbols:
```
_ZN6QDebuglsEPKc@Base 1.22.0
 _ZN6QDebuglsERK7QString@Base 1.22.0
 _ZN7QStringD1Ev@Base 1.22.0
 _ZN7QStringD2Ev@Base 1.22.0
```
It seems the symbols file is ok and I try to build it on riscv64
hardware locally and it is ok :)

Or I am misunderstanding the buildd log error hint？

BR,
Bo

> Adrian
>
> > [1] https://wiki.debian.org/UsingSymbolsFiles
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer
> `. `'   Physicist
>   `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>

[toc] | [prev] | [next] | [standalone]

#1102637

Hi Bo!

On 5/9/22 16:27, Bo YU wrote:
s error just means that the symbols file(s) have to be updated, see [1].
>>
> Before I filed the bug, I realized the ftbfs issue might be with the
> symbols file as you point.
> `apt source qbs` and the debian/symbols file has the symbols:
> ```
> _ZN6QDebuglsEPKc@Base 1.22.0
>  _ZN6QDebuglsERK7QString@Base 1.22.0
>  _ZN7QStringD1Ev@Base 1.22.0
>  _ZN7QStringD2Ev@Base 1.22.0
> ```
> It seems the symbols file is ok and I try to build it on riscv64
> hardware locally and it is ok :)
> 
> Or I am misunderstanding the buildd log error hint？

It might be that the symbols file mismatch is considered a fatal error on the buildd but
not for your local builds. Or the buildd was building with different build dependencies,
we can try to trigger a rebuild on the buildd.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

[toc] | [prev] | [next] | [standalone]

#1102677

Hi!

On Mon, 9 May 2022 at 11:51, John Paul Adrian Glaubitz
<glaubitz@physik.fu-berlin.de> wrote:
>
> Hi Bo!
>
> On 5/9/22 16:27, Bo YU wrote:
> s error just means that the symbols file(s) have to be updated, see [1].
> >>
> > Before I filed the bug, I realized the ftbfs issue might be with the
> > symbols file as you point.
> > `apt source qbs` and the debian/symbols file has the symbols:
> > ```
> > _ZN6QDebuglsEPKc@Base 1.22.0
> >  _ZN6QDebuglsERK7QString@Base 1.22.0
> >  _ZN7QStringD1Ev@Base 1.22.0
> >  _ZN7QStringD2Ev@Base 1.22.0
> > ```
> > It seems the symbols file is ok and I try to build it on riscv64
> > hardware locally and it is ok :)
> >
> > Or I am misunderstanding the buildd log error hint？
>
> It might be that the symbols file mismatch is considered a fatal error on the buildd but
> not for your local builds. Or the buildd was building with different build dependencies,
> we can try to trigger a rebuild on the buildd.

Missing non-optional symbols is fatal. But in this case:

$ c++filt _ZN6QDebuglsERK7QString
QDebug::operator<<(QString const&)

And:

$ grep -Rn QDebug /usr/include/qbs/*
/usr/include/qbs/tools/codelocation.h:90:QDebug operator<<(QDebug
debug, const CodeLocation &location);

As you can see the signatures do not match, so the missing symbol must
come from some private header and it's not exposed to the user.

The maintainer will probably add the required changes in the next
upload, as usual.

-- 
Lisandro Damián Nicanor Pérez Meyer
https://perezmeyer.com.ar/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web