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: other/6773: gcc-3.1 make install fails using cross compiler Date: Wed, 22 May 2002 15:16:00 -0000 [thread overview] Message-ID: <20020522221602.9929.qmail@sources.redhat.com> (raw) The following reply was made to PR other/6773; it has been noted by GNATS. From: Phil Edwards <phil@jaj.com> To: jeff.deifik@jpl.nasa.gov Cc: gcc-gnats@gcc.gnu.org Subject: Re: other/6773: gcc-3.1 make install fails using cross compiler Date: Wed, 22 May 2002 18:09:14 -0400 On Wed, May 22, 2002 at 09:15:09PM -0000, jeff.deifik@jpl.nasa.gov wrote: > make install fails to install the include directory tree > The problem is one level of "../" in the install-sh path > is missing in several places. I couldn't read the typescript attached (GNATS is very very good about completely destroying the MIME attachments), but this is a classic symptom of configuring and building in the source directory instead of a separate build directory. In-source builds are supposed to work in theory, but tend to be fragile and break often. Did you do an in-source build? If so, can you try a separate objdir? 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-05-22 22:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-22 15:16 Phil Edwards [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-12 10:51 steven 2003-05-12 0:06 Dara Hazeghi 2003-05-10 23:46 Dara Hazeghi 2002-05-22 14:16 jeff.deifik
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=20020522221602.9929.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: linkBe 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).