public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
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 21:11:00 -0000	[thread overview]
Message-ID: <20120808211127.F13DA2C0E3@topped-with-meat.com> (raw)
In-Reply-To: Joseph S. Myers's message of  Wednesday, 8 August 2012 21:06:27 +0000 <Pine.LNX.4.64.1208082103200.31240@digraph.polyomino.org.uk>

> 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 

I see.  I had --enable-multi-arch in my canonical generic set of configure
switches established for x86 and from when it was never the default.
Since it now defaults to on when it's useful, I'll change my configure lines.


Thanks,
Roland

      reply	other threads:[~2012-08-08 21:11 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
2012-08-08 21:11       ` Roland McGrath [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120808211127.F13DA2C0E3@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).