public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Scott Wood <scott@timesys.com>
To: dj@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/7090: libstdc++ configure script fails to find install-sh when cross-compiling
Date: Tue, 29 Oct 2002 17:56:00 -0000 [thread overview]
Message-ID: <20021030015602.23672.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/7090; it has been noted by GNATS.
From: Scott Wood <scott@timesys.com>
To: DJ Delorie <dj@redhat.com>
Cc: scott@timesys.com, neroden@twcny.rr.com, gcc-gnats@gcc.gnu.org,
gcc-bugs@gcc.gnu.org
Subject: Re: bootstrap/7090: libstdc++ configure script fails to find install-sh when cross-compiling
Date: Tue, 29 Oct 2002 20:50:01 -0500
On Sat, Oct 26, 2002 at 11:38:15PM -0400, DJ Delorie wrote:
>
> > I still get the error with 3.2, in the configure script for libffi.
>
> The PR was against 3.1. Could you check 3.1, making sure that the
> sources you have include the patch listed in the PR? I'll also test
> 3.2, making sure that libffi gets involved.
I tried CVS of 3.1 from the day after that which was listed on the
patch, and I still get the error in libffi. 3.1.1 (as well as the
head of the 3.1 branch) gives:
./../../../configure: ./../../../configure: No such file or directory
configure: error: ./../../../configure failed for libU77
make: *** [configure-target-libf2c] Error 1
-Scott
next reply other threads:[~2002-10-30 1:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 17:56 Scott Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 12:16 H. J. Lu
2002-10-31 11:16 Joe Buck
2002-10-31 11:06 Scott Wood
2002-10-31 10:26 Joe Buck
2002-10-26 20:46 DJ Delorie
2002-10-26 20:36 Scott Wood
2002-10-25 18:26 DJ Delorie
2002-10-25 18:26 DJ Delorie
2002-10-25 16:46 Nathanael Nerode
2002-06-25 23:36 dj
2002-06-24 13:46 pme
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=20021030015602.23672.qmail@sources.redhat.com \
--to=scott@timesys.com \
--cc=dj@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.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).