[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue when testing with --as-needed enabled
|
From: |
Bruno Haible |
|
Subject: |
Re: Issue when testing with --as-needed enabled |
|
Date: |
Fri, 27 Nov 2020 21:34:06 +0100 |
|
User-agent: |
KMail/5.1.3 (Linux/4.4.0-193-generic; KDE/5.18.0; x86_64; ; ) |
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