public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/7090: libstdc++ configure script fails to find install-sh when cross-compiling
Date: Thu, 20 Jun 2002 15:08:00 -0000 [thread overview]
Message-ID: <20020620215603.8105.qmail@sources.redhat.com> (raw)
The following reply was made to PR libstdc++/7090; it has been noted by GNATS.
From: Phil Edwards <phil@jaj.com>
To: Scott Wood <scott@gw.timesys.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/7090: libstdc++ configure script fails to find install-sh when cross-compiling
Date: Thu, 20 Jun 2002 17:52:39 -0400
On Thu, Jun 20, 2002 at 05:22:40PM -0400, Scott Wood wrote:
> On Thu, Jun 20, 2002 at 04:11:51PM -0400, Phil Edwards wrote:
> > On Thu, Jun 20, 2002 at 07:35:05PM -0000, scott@timesys.com wrote:
> > > >How-To-Repeat:
> > > ./configure --target=powerpc-linux
> > > make
> >
> > Could you try building in a separate build directory and lets us know what
> > happens?
>
> It works. Is building within the gcc directory no longer supported?
It's supported, but fragile, and patches to make it cleaner have been
rejected. The next point release (3.1.1) should have this fixed.
Note that building in a separate directory is /strongly/ recommended by
the installation docs.
Phil
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams
next reply other threads:[~2002-06-20 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 15:08 Phil Edwards [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-20 18:06 pme
2002-06-20 14:27 Scott Wood
2002-06-20 13:35 Phil Edwards
2002-06-20 13:08 scott
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=20020620215603.8105.qmail@sources.redhat.com \
--to=phil@jaj.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).