From: Tim Prince <timothyprince@sbcglobal.net>
To: ross.cameron@linuxpro.co.za
Cc: gcc-help@gcc.gnu.org
Subject: Re: GCC compile issues
Date: Sat, 24 Jun 2006 01:58:00 -0000 [thread overview]
Message-ID: <449C9C25.1040503@sbcglobal.net> (raw)
In-Reply-To: <449C6533.5060808@linuxpro.co.za>
Ross Cameron wrote:
> Hi there all,... I'm getting the following error output when running
> "make install" of gcc-4.1.1
>
> ----- CUT -----
> make[1]: Entering directory `/media/LFS/gcc-build/gcc-4.1.1'
> /bin/sh ./mkinstalldirs /tools /tools
> /bin/sh: line 0: cd: host-x86_64-unknown-linux-gnu/fixincludes: No
> such file or directory
> make[1]: *** [install-fixincludes] Error 1
> make[1]: Leaving directory `/media/LFS/gcc-build/gcc-4.1.1'
> make: *** [install] Error 2
> ----- CUT -----
>
> I successfully compiled binutils-2.17.50.0.2 immediately prior to this.
>
> I am using the compilation instructions from the LFS (aka Linux From
> Scratch) project.
Much more relevant would be what steps you did take, how did they differ
from recommendations on gcc.gnu.org, ...
If you skipped the configure and make steps, you won't get much
sympathy. You didn't even reveal what host and target systems you are
interested in.
prev parent reply other threads:[~2006-06-24 1:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 22:04 Ross Cameron
2006-06-24 1:58 ` Tim Prince [this message]
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=449C9C25.1040503@sbcglobal.net \
--to=timothyprince@sbcglobal.net \
--cc=gcc-help@gcc.gnu.org \
--cc=ross.cameron@linuxpro.co.za \
--cc=tprince@myrealbox.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).