From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Roland McGrath <roland@hack.frob.com>
Cc: <libc-ports@sourceware.org>
Subject: Re: [PATCH roland/arm-irel-ldsodefs] ARM: add missing #include
Date: Wed, 08 Aug 2012 21:06:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1208082103200.31240@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20120808205649.526EB2C0DE@topped-with-meat.com>
On Wed, 8 Aug 2012, Roland McGrath wrote:
> The error hits csu/elf-init.c first, and I think it hit some other files
> later. I've attached elf-init.i from my failing compile in case you want
> to puzzle out how its include order differs from yours.
It looks like the issue with that file is specific to multi-arch-enabled
builds, which include extra headers in that file - and since there are no
multiarch/ sysdeps directories for ARM, multiarch is disabled by default
(there's not much point in enabling it without code in glibc to use it,
and the IFUNC support will still work for user shared libraries).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-08-08 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 20:19 Roland McGrath
2012-08-08 20:34 ` Joseph S. Myers
2012-08-08 20:57 ` Roland McGrath
2012-08-08 21:06 ` Joseph S. Myers [this message]
2012-08-08 21:11 ` Roland McGrath
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=Pine.LNX.4.64.1208082103200.31240@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=roland@hack.frob.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).