Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: hjl@lucon.org
Cc: gdb@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: The canadian cross build is broken
Date: Tue, 26 Mar 2002 14:00:00 -0000	[thread overview]
Message-ID: <200203262200.g2QM0Rc14288@greed.delorie.com> (raw)
In-Reply-To: <20020326135334.A8928@lucon.org> (hjl@lucon.org)


> Why? Here is the fragment. $frag won't be empty. The default one is
> mh-${host_cpu}pic:

In some future cases, it may end up getting added twice, in other
cases, it's empty and may cause problems.  For example, for cygwin
frag remains set to its previous value (currently empty) so you end up
adding "config/" to the list of frags.

> if [ "${shared}" = "yes" ]; then
>   case "${host}" in
>     *-*-cygwin*)        ;;

> 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?

Some broken OSs may treat directories as meeting "test -f" :-(


  reply	other threads:[~2002-03-26 22:00 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
2002-03-26 14:00             ` DJ Delorie [this message]
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=200203262200.g2QM0Rc14288@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=hjl@lucon.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