Re: Issue when testing with --as-needed enabled

[Thomas Andrejak]

Hello

Does someone has any updates on this ?

Thanks

Regards

Le mar. 1 déc. 2020 à 13:56, Thomas Andrejak <thomas.andrejak@gmail.com> a écrit :

Hello

Can you explain what GCC options can interfere with this ?

Thanks

Regards

Le dim. 29 nov. 2020 à 00:18, Thomas Andrejak <thomas.andrejak@gmail.com> a écrit :

Hello

Thanks for your answer

On debian 9 /10 / testing

Regards

Le ven. 27 nov. 2020 à 21:34, Bruno Haible <bruno@clisp.org> a écrit :

Thomas Andrejak wrote:
> Few years ago, we had an issue when--as-needed was enabled. There has been
> a patch for this :
> https://github.com/coreutils/gnulib/commit/426320901d46b1f3b63ba1ec8e9e60cb0e28cb77
>
> But, event with this patch, I still have build failure and I need to do
> some patches like that :
> https://salsa.debian.org/totol-guest/libprelude/-/blob/master/debian/patches/013-fix-test_rwlock1.patch
>
> I don't know how to dig on this bug.
>
> Output :
> FAIL: test-rwlock1
> ==================
> Unexpected outcome 3
> FAIL test-rwlock1 (exit status: 134)
>
> Can someone help me on this ?

On which OS (distro) do you see this? I'm asking because different distros
have configured GCC differently, and these are the details that matter
regarding --as-needed.

Bruno