public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: Roland McGrath <roland@hack.frob.com>,
	    Carlos O'Donell <carlos_odonell@mentor.com>,
	Andrew Haley <aph@redhat.com>,
	    libc-ports@sourceware.org, steve.mcintyre@linaro.org,
	    michael.hope@linaro.org
Subject: Re: [WIP] glibc: Use /lib/ld-linux-armhf.so.3 for ARM's -mfloat-abi=hard ABI.
Date: Sat, 05 May 2012 23:17:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1205052316420.3843@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CADZpyiwSnQmxsYRMW0zu2uusoq2xf4mVhTjZHUNs+aTq3herPg@mail.gmail.com>

On Sat, 5 May 2012, Carlos O'Donell wrote:

> Except that this idea doesn't work because the implicit rule uses
> -undef and I didn't notice that.
> 
> Therefore __ARM_PCS_VFP is *never* defined.
> 
> Thoughts?

That suggests going back to a preconfigure test (testing whether 
__ARM_PCS_VFP is defined) to select appropriate sysdeps directories with 
different shlib-versions files.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2012-05-05 23:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 17:27 New path for ld.so on ARM hard fp Andrew Haley
2012-04-13 17:29 ` Andrew Haley
2012-04-13 17:35   ` Roland McGrath
2012-04-14 16:35     ` Carlos O'Donell
2012-04-23  8:42       ` Andrew Haley
2012-04-26  3:41         ` Carlos O'Donell
2012-04-26 21:09         ` [WIP] glibc: Use /lib/ld-linux-armhf.so.3 for ARM's -mfloat-abi=hard ABI Carlos O'Donell
2012-04-26 21:43           ` Roland McGrath
2012-04-26 22:03           ` Joseph S. Myers
2012-04-26 22:07             ` Roland McGrath
2012-05-05 21:06               ` Carlos O'Donell
2012-05-05 21:48                 ` Joseph S. Myers
2012-05-05 21:52                 ` Carlos O'Donell
2012-05-05 23:17                   ` Joseph S. Myers [this message]
2012-05-06  2:18                     ` Carlos O'Donell
2012-05-06 12:13                       ` Joseph S. Myers
2012-05-06 21:36                         ` Carlos O'Donell
2012-05-06 22:41                           ` Joseph S. Myers
2012-05-07 18:47                   ` Roland McGrath
2012-05-07 18:57                     ` Carlos O'Donell
2012-05-07 19:55                       ` Roland McGrath
2012-05-07 20:00                         ` Carlos O'Donell
2012-05-07 20:00                           ` Carlos O'Donell
2012-05-07 19:11                     ` Joseph S. Myers
2012-05-07 19:41                       ` Roland McGrath
2012-05-07 20:52                         ` Joseph S. Myers
2012-05-07 21:31                           ` Roland McGrath
2012-05-01  4:48             ` Khem Raj
2012-05-01 10:09               ` Joseph S. Myers
2012-04-27  2:18           ` Mike Frysinger
2012-04-27 12:57             ` Carlos O'Donell
2012-04-19 19:49 ` New path for ld.so on ARM hard fp Joseph S. Myers

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.1205052316420.3843@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=aph@redhat.com \
    --cc=carlos@systemhalted.org \
    --cc=carlos_odonell@mentor.com \
    --cc=libc-ports@sourceware.org \
    --cc=michael.hope@linaro.org \
    --cc=roland@hack.frob.com \
    --cc=steve.mcintyre@linaro.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).