From: Joseph Myers <joseph@codesourcery.com>
To: Luis Machado <luis.machado@arm.com>
Cc: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>,
"binutils@sourceware.org" <binutils@sourceware.org>,
Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH] gprofng: PR29987 bfd/archive.c:1447: undefined reference to `filename_ncmp'
Date: Mon, 16 Jan 2023 19:28:56 +0000 [thread overview]
Message-ID: <50979a3b-2062-ef23-16e2-b0c9ecd0abf2@codesourcery.com> (raw)
In-Reply-To: <85078aba-407e-2576-7eb4-58a457924adc@arm.com>
On Mon, 16 Jan 2023, Luis Machado via Binutils wrote:
> Hi,
>
> I bisected a broken build on aarch64-linux Ubuntu 22.04 to this commit.
>
> It seems to cause a number of undefined references when building with
> --enable-targets=all.
I'm also seeing this with cross builds for x86_64-linux-gnu and
aarch64-linux-gnu targets.
https://sourceware.org/pipermail/libc-testresults/2023q1/010729.html
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-01-16 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 20:56 vladimir.mezentsev
2023-01-13 23:41 ` Vladimir Mezentsev
2023-01-16 14:10 ` Luis Machado
2023-01-16 19:28 ` Joseph Myers [this message]
2023-01-17 0:05 ` Vladimir Mezentsev
2023-01-17 10:21 ` Luis Machado
2023-01-18 3:35 ` Vladimir Mezentsev
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50979a3b-2062-ef23-16e2-b0c9ecd0abf2@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=luis.machado@arm.com \
--cc=nickc@redhat.com \
--cc=vladimir.mezentsev@oracle.com \
/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).