public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@cygnus.com>
To: hjl@lucon.org (H.J. Lu)
Cc: egcs@cygnus.com, wilson@cygnus.com
Subject: Re: A patch for dejagnu
Date: Thu, 12 Mar 1998 17:00:00 -0000	[thread overview]
Message-ID: <199803130100.RAA22598@rtl.cygnus.com> (raw)
In-Reply-To: <m0yCpT3-00058JC@ocean.lucon.org>

	+	    # We search ${target_alias} last since it is only valid
	+	    # when we are running dejagnu on an installed gcc. We
	+	    # don't want to get it by accident.

This is due to an unfortunate difference between the Cygnus source tree and
the EGCS source tree.  In EGCS, we build libraries in a subdirectory called
`libraries'.  In the Cygnus source tree, we build libraries in a subdirectory
called `${target_alias}'.  Hence searching target_alias first is correct
for the Cygnus sources, but not correct for EGCS.

Historical info: The Cygnus source tree creates the subdirectory only if
we are doing a cross, in which case --target=foo must have been specified,
and using foo for the subdirectory name was reasonable.  EGCS always creates
the subdirectory, so as to make multilibbed native builds work.  Since there
is usually no --target=foo option, using target_alias is unsafe, as it might
not be a valid filename.  I changed EGCS to use libraries instead, but this
change never got propagated back into the Cygnus sources.

I probably should make an attempt to get this `libraries' change into the
Cygnus sources, so that the two source trees will be consistent, and then
we can make a dejagnu that will work for both of them.

Jim

  reply	other threads:[~1998-03-12 17:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-11  9:39 H.J. Lu
1998-03-12 17:00 ` Jim Wilson [this message]
1998-03-16 20:04   ` Jeffrey A Law
1998-05-28  6:19 none Jeffrey A Law
1998-05-28 17:47 ` A patch for dejagnu H.J. Lu

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=199803130100.RAA22598@rtl.cygnus.com \
    --to=wilson@cygnus.com \
    --cc=egcs@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).