From: Thomas Andrejak <thomas.andrejak@gmail.com>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: Issue when testing with --as-needed enabled
Date: Sun, 29 Nov 2020 00:18:43 +0100 [thread overview]
Message-ID: <CABjmheO_FdyiDwVw=_f8R5TGOwzec1sRtDYdm-yZxkWV6hBBpQ@mail.gmail.com> (raw)
In-Reply-To: <1712786.L2PYDFIFIf@omega>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
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
>
>
[-- Attachment #2: Type: text/html, Size: 1747 bytes --]
next prev parent reply other threads:[~2020-11-28 23:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 9:45 Issue when testing with --as-needed enabled Thomas Andrejak
2020-11-27 20:34 ` Bruno Haible
2020-11-28 23:18 ` Thomas Andrejak [this message]
2020-12-01 12:56 ` Thomas Andrejak
2020-12-29 22:29 ` Thomas Andrejak
2021-01-24 11:38 ` Jeffrey Walton
2021-01-03 22:34 ` Bruno Haible
2021-01-23 22:53 ` Thomas Andrejak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABjmheO_FdyiDwVw=_f8R5TGOwzec1sRtDYdm-yZxkWV6hBBpQ@mail.gmail.com' \
--to=thomas.andrejak@gmail.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).