From: Jim Wilson <wilson@chestnut.cygnus.com>
To: Derek Wildstar <dwild@nin.org>
Cc: egcs@cygnus.com, pcg@goof.com
Subject: Re: egcs v970828 builds fine on linux-i586libc1 =)
Date: Thu, 04 Sep 1997 20:37:00 -0000 [thread overview]
Message-ID: <199709050337.UAA07659@cygnus.com> (raw)
In-Reply-To: <Pine.LNX.3.96.970903033226.7480A-100000@argo.starforce.com>
The only thing I found with the build
was that it failed to find "../move-if-change". (once on each linux version
and several times on the sunos version, because of the deeper build path).
This is already fixed in the new snapshot. There was a missing MULTISRCTOP
in the libiberty path for move-if-change which caused a srcdir == objdir
build to fail.
Jim
next prev parent reply other threads:[~1997-09-04 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.970830045114.9291A-100000@argo.starforce.com>
1997-09-02 15:34 ` Jeffrey A Law
1997-09-04 20:10 ` Derek Wildstar
1997-09-04 20:26 ` Jeffrey A Law
1997-09-04 20:37 ` Jim Wilson [this message]
1997-08-30 11:27 libg++? Chip Salzenberg
1997-08-30 12:00 ` egcs v970828 builds fine on linux-i586libc1 =) Derek Wildstar
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=199709050337.UAA07659@cygnus.com \
--to=wilson@chestnut.cygnus.com \
--cc=dwild@nin.org \
--cc=egcs@cygnus.com \
--cc=pcg@goof.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).