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: Sat, 23 Jan 2021 23:53:07 +0100 [thread overview]
Message-ID: <CABjmheNBo_49fg0k6WcnhNw6FGXB+V=n84tHOwAQEY8FoODFPQ@mail.gmail.com> (raw)
In-Reply-To: <3737833.uD18jXWYC1@omega>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
Hello
I'm sorry, I was not on the master branch. With an up to date gnulib
version, I do not have this issue anymore.
Thanks !
Regards
Le dim. 3 janv. 2021 à 23:34, Bruno Haible <bruno@clisp.org> a écrit :
> Hi,
>
> Thomas Andrejak wrote:
> > On debian 9 /10 / testing
> > ...
> > > > 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)
>
> I cannot reproduce this. I took a Debian 10.7 distribution, with gcc-8 as
> compiler package. I created a testdir for all of gnulib. I configured it
> in 3 ways:
> - the normal way,
> - with LDFLAGS="... -Wl,--as-needed"
> - with CFLAGS="... -Wl,--as-needed"
> and in all cases the build succeeded and all tests passed.
>
> So, you need to give *precise* instructions for how to reproduce it.
>
> Without reproducing, no one can give an analysis nor a fix.
>
> Bruno
>
>
[-- Attachment #2: Type: text/html, Size: 1945 bytes --]
prev parent reply other threads:[~2021-01-23 22:53 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
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 [this message]
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='CABjmheNBo_49fg0k6WcnhNw6FGXB+V=n84tHOwAQEY8FoODFPQ@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).