From: Roland McGrath <roland@hack.frob.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: <libc-ports@sourceware.org>
Subject: Re: [PATCH roland/arm-irel-ldsodefs] ARM: add missing #include
Date: Wed, 08 Aug 2012 20:57:00 -0000 [thread overview]
Message-ID: <20120808205649.526EB2C0DE@topped-with-meat.com> (raw)
In-Reply-To: Joseph S. Myers's message of Wednesday, 8 August 2012 20:34:14 +0000 <Pine.LNX.4.64.1208082031030.31240@digraph.polyomino.org.uk>
[-- Attachment #1: message body text --]
[-- Type: text/plain, Size: 992 bytes --]
> It's OK and adding missing #includes is one of the types of changes
> documented at <http://sourceware.org/glibc/wiki/Consensus> as not needing
> review, but what source file are you building to get this error and what
> header include order do you see when that file is built? It looks like
> (as indicated e.g. by the ordering in the .d files) all the files that end
> up including dl-irel.h get ldsodefs.h included first for me.
I know it's in the "obvious" category but I wanted to ping you just in case
this was uncovering some subtle problem in my build and you thought it
shouldn't be required. I'll put it in now since on basic "include what you
use" principles dl-irel.h ought to have the #include. But it may be
worthwhile to investigate it anyway.
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.
Thanks,
Roland
[-- Attachment #2: elf-init.i.bz2 --]
[-- Type: application/octet-stream, Size: 34575 bytes --]
next prev parent reply other threads:[~2012-08-08 20:57 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 [this message]
2012-08-08 21:06 ` Joseph S. Myers
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=20120808205649.526EB2C0DE@topped-with-meat.com \
--to=roland@hack.frob.com \
--cc=joseph@codesourcery.com \
--cc=libc-ports@sourceware.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).