From: Steve Munroe <sjmunroe@us.ibm.com>
To: Richard Henderson <rth@twiddle.net>
Cc: libc-hacker@sourceware.org, libc-hacker-owner@sourceware.org
Subject: Re: incorrect double search paths w/ ieee754/ldbl-opt
Date: Tue, 13 Mar 2007 17:53:00 -0000 [thread overview]
Message-ID: <OF90DC6706.6F0B66C7-ON8625729D.0060A2A8-8625729D.0061F521@us.ibm.com> (raw)
In-Reply-To: <20070313171853.GA5781@twiddle.net>
Richard Henderson <rth@twiddle.net> wrote on 03/13/2007 12:18:53 PM:
> Putting ieee754/ldbl-opt in sysdeps/unix/sysv/linux/*/Implies results in
> that directory being searched before the sysdeps/cpu/fpu directory.
>
> Any suggestions for how to rearrange things so that the native fpu stuff
> comes first?
>
This is similar to the problem I had with the powerpc-cpu add-on.
I added Implies in ./sysdeps/unix/sysv/linux/*/fpu/
with refs to the native sysdeps/<cpu>/fpu dirs
Steven J. Munroe
Linux on Power Toolchain Architect
IBM Corporation, Linux Technology Center
next prev parent reply other threads:[~2007-03-13 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 17:19 Richard Henderson
2007-03-13 17:53 ` Steve Munroe [this message]
2007-03-13 21:43 ` Richard Henderson
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=OF90DC6706.6F0B66C7-ON8625729D.0060A2A8-8625729D.0061F521@us.ibm.com \
--to=sjmunroe@us.ibm.com \
--cc=libc-hacker-owner@sourceware.org \
--cc=libc-hacker@sourceware.org \
--cc=rth@twiddle.net \
/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).