Re: Bug#1017979: mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.

2022-09-20 Thread Simon McVittie
Control: tags -1 + patch

On Tue, 23 Aug 2022 at 21:39:50 +0100, Simon McVittie wrote:
> On Tue, 23 Aug 2022 at 13:23:30 +0100, Simon McVittie wrote:
> > The final link fails with multiple definitions of the various atomic
> > builtins:
> > 
> > > (.text+0x0): multiple definition of `__sync_fetch_and_add_4'; 
> > > /home/smcv/mozjs91-armel/debian/build/armv5te-unknown-linux-gnueabi/release/libjsrust.a(compiler_builtins-23c2fc8f8ef06d87.compiler_builtins.bdb7b41d-cgu.153.rcgu.o):/usr/src/rustc-1.59.0/vendor/compiler_builtins/src/arm_linux.rs:94:
> > >  first defined here
> 
> Reported upstream as https://bugzilla.mozilla.org/show_bug.cgi?id=1786623

Workaround: link with -Wl,--allow-multiple-definition (thanks to Adrian
Bunk).

I think we're more likely to replace mozjs91 in gjs' dependencies with
mozjs102 and remove mozjs91 than we are to fix mozjs91, but I'm mentioning
this here in case it becomes necessary to use mozjs91 for some reason.
Linking with -Wl,--allow-multiple-definition seems like a less bad
workaround than using a non-default gcc.

smcv



Re: Bug#1017979: mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.

2022-08-23 Thread Simon McVittie
On Tue, 23 Aug 2022 at 16:44:54 -0400, Jeffrey Walton wrote:
> On Tue, Aug 23, 2022 at 4:40 PM Simon McVittie  wrote:
> > On Tue, 23 Aug 2022 at 13:23:30 +0100, Simon McVittie wrote:
> > > The final link fails with multiple definitions of the various atomic
> > > builtins:
> > >
> > > > (.text+0x0): multiple definition of `__sync_fetch_and_add_4'; 
> > > > /home/smcv/mozjs91-armel/debian/build/armv5te-unknown-linux-gnueabi/release/libjsrust.a(compiler_builtins-23c2fc8f8ef06d87.compiler_builtins.bdb7b41d-cgu.153.rcgu.o):/usr/src/rustc-1.59.0/vendor/compiler_builtins/src/arm_linux.rs:94:
> > > >  first defined here
> 
> Also see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104248#c2 (and
> more generally https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358).

Those are related, but seem like the opposite issue: I'm getting
a build failure because I somehow end up with two copies of
__sync_fetch_and_add_4, whereas those bugs are about having zero copies
of similar compiler-provided functions. We want exactly one copy :-)

Or are you saying that I'm getting these multiple definitions *because*,
unlike gcc-11, gcc-12 is automatically providing symbols like
__sync_fetch_and_add_4 in order to resolve those gcc bug reports?

In any case it seems to be possible to work around this by forcing gcc-11,
which is not great (toolchain maintainers dislike uses of a non-default
gcc) but arguably better than FTBFS.

smcv



Re: Bug#1017979: mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.

2022-08-23 Thread Jeffrey Walton
On Tue, Aug 23, 2022 at 4:40 PM Simon McVittie  wrote:
>
> Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1786623
> Control: affects -1 + src:mozjs102
>
> On Tue, 23 Aug 2022 at 13:23:30 +0100, Simon McVittie wrote:
> > The final link fails with multiple definitions of the various atomic
> > builtins:
> >
> > > (.text+0x0): multiple definition of `__sync_fetch_and_add_4'; 
> > > /home/smcv/mozjs91-armel/debian/build/armv5te-unknown-linux-gnueabi/release/libjsrust.a(compiler_builtins-23c2fc8f8ef06d87.compiler_builtins.bdb7b41d-cgu.153.rcgu.o):/usr/src/rustc-1.59.0/vendor/compiler_builtins/src/arm_linux.rs:94:
> > >  first defined here
>
> Reported upstream as https://bugzilla.mozilla.org/show_bug.cgi?id=1786623

Also see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104248#c2 (and
more generally https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358).

> > (For completeness: 91.10.0-1 and 91.12.0-1 have an additional failure
> > reason involving undefined references to
> > std::type_info::operator==(std::type_info const&) const, but I believe
> > that was fixed in 91.12.0-2 by removing an obsolete patch.)
>
> Correction, it was fixed by a patch removing an obsolete workaround.
> Reported as https://bugzilla.mozilla.org/show_bug.cgi?id=1786621 (but we
> already have a patch for this, so it's an upstream bug but not a Debian bug)

Jeff



Re: Bug#1017979: mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.

2022-08-23 Thread Simon McVittie
Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1786623
Control: affects -1 + src:mozjs102

On Tue, 23 Aug 2022 at 13:23:30 +0100, Simon McVittie wrote:
> The final link fails with multiple definitions of the various atomic
> builtins:
> 
> > (.text+0x0): multiple definition of `__sync_fetch_and_add_4'; 
> > /home/smcv/mozjs91-armel/debian/build/armv5te-unknown-linux-gnueabi/release/libjsrust.a(compiler_builtins-23c2fc8f8ef06d87.compiler_builtins.bdb7b41d-cgu.153.rcgu.o):/usr/src/rustc-1.59.0/vendor/compiler_builtins/src/arm_linux.rs:94:
> >  first defined here

Reported upstream as https://bugzilla.mozilla.org/show_bug.cgi?id=1786623

> (For completeness: 91.10.0-1 and 91.12.0-1 have an additional failure
> reason involving undefined references to
> std::type_info::operator==(std::type_info const&) const, but I believe
> that was fixed in 91.12.0-2 by removing an obsolete patch.)

Correction, it was fixed by a patch removing an obsolete workaround.
Reported as https://bugzilla.mozilla.org/show_bug.cgi?id=1786621 (but we
already have a patch for this, so it's an upstream bug but not a Debian bug)

smcv