From: "H . J . Lu" <hjl@lucon.org>
To: DJ Delorie <dj@redhat.com>
Cc: gdb@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: The canadian cross build is broken
Date: Tue, 26 Mar 2002 13:53:00 -0000 [thread overview]
Message-ID: <20020326135334.A8928@lucon.org> (raw)
In-Reply-To: <200203262149.g2QLnIK14130@greed.delorie.com>; from dj@redhat.com on Tue, Mar 26, 2002 at 04:49:18PM -0500
On Tue, Mar 26, 2002 at 04:49:18PM -0500, DJ Delorie wrote:
>
> > What multiple host frags? I am not sure what you meant by that.
>
> Oops, nevermind. I see where you moved that logic to. You need to
> check for $frag being empty before adding it to $frags though.
Why? Here is the fragment. $frag won't be empty. The default one is
mh-${host_cpu}pic:
if [ "${shared}" = "yes" ]; then
case "${host}" in
*-*-cygwin*) ;;
alpha*-*-linux*) frag=mh-elfalphapic ;;
arm*-*-*) frag=mh-armpic ;;
hppa*-*-*) frag=mh-papic ;;
i[3456]86-*-*) frag=mh-x86pic ;;
mips*-*-linux*) frag=mh-mipspic ;;
powerpc*-*-aix*) ;;
powerpc*-*-*) frag=mh-ppcpic ;;
sparc*-*-*) frag=mh-sparcpic ;;
*) frag=mh-${host_cpu}pic ;;
esac
frags="${frags} ${libiberty_topdir}/config/${frag}"
fi
Later, we check if it exists:
for frag in ${frags}; do
if [ -f ${frag} ]; then
echo "Appending ${frag} to xhost-mkfrag"
echo "# Following fragment copied from ${frag}" >> temp-frag
cat ${frag} >> temp-frag
fi
done
before appending it. Did I miss something?
H.J.
H.J.
next prev parent reply other threads:[~2002-03-26 21:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 22:52 H . J . Lu
2002-03-23 7:29 ` Andrew Cagney
2002-03-23 10:14 ` H . J . Lu
2002-03-25 9:50 ` DJ Delorie
2002-03-25 14:15 ` DJ Delorie
2002-03-26 13:24 ` H . J . Lu
2002-03-26 13:35 ` DJ Delorie
2002-03-26 13:42 ` H . J . Lu
2002-03-26 13:49 ` DJ Delorie
2002-03-26 13:53 ` H . J . Lu [this message]
2002-03-26 14:00 ` DJ Delorie
2002-03-26 14:36 ` H . J . Lu
2002-03-26 14:49 ` DJ Delorie
2002-03-26 14:59 ` H . J . Lu
2002-03-26 15:30 ` DJ Delorie
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=20020326135334.A8928@lucon.org \
--to=hjl@lucon.org \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.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