From: James HAUXWELL <james.hauxwell@st.com>
To: gcc-help@gcc.gnu.org
Subject: compilation problem
Date: Tue, 31 Jan 2006 09:42:00 -0000 [thread overview]
Message-ID: <43DF30F1.90304@st.com> (raw)
Hi,
I've gone through the installation instructions and read quit a lot, but
I am still unable to get a correct compile/installation.
I'm using
CYGWIN_NT-5.1 bri0203 1.5.19(0.150/4/2) 2006-01-18 11:15 i686 Cygwin
with gcc-4.2-20060121
I went to the test results mailing list and pulled the configure line
from a successful build, so I did the following
$ ./configure '--enable-languages=c' --enable-threads=posix
--enable-sjlj-exceptions --disable-libmudflap --disable-shared
--prefix=/usr/local/gcc42 --enable-bootstrap --disable-libgomp
--enable-languages=c
$ make bootstrap
wait 3 hours...
$ make install
everything seemed to succeed, apart from a message
make[3]: Leaving directory `/cygdrive/c/sources/gcc4.2/gcc-4.2-20060121'
/bin/sh: line 0: cd: stage3-gcc: No such file or directory
when I test the build after the install
$ gcc pestoes.c -mno-cygwin -v pestoes.exe
Using built-in specs.
Target: i686-pc-mingw32
Configured with: ./configure --enable-languages=c --enable-threads=posix
--enable-sjlj-exceptions --disable-libmudflap -
-disable-shared --prefix=/usr/local/gcc42 --enable-bootstrap
--disable-libgomp --enable-languages=c
Thread model: posix
gcc version 4.2.0 20060121 (experimental)
cc1 -quiet -v -D__MSVCRT__ -D__MINGW32__ -DWIN32 -D_WIN32 -D__WIN32
-D__WIN32__ -DWINNT -idirafter /usr/lib/../include/
w32api -idirafter ../../include/w32api pestoes.c -quiet -dumpbase
pestoes.c -mno-cygwin -mtune=generic -auxbase pestoes
-version -o /cygdrive/c/DOCUME~1/JAMESH~1/LOCALS~1/Temp/cc8TR2Uv.s
gcc: error trying to exec 'cc1': execvp: No such file or directory
and it looks like cc1.exe was not copied into the correct place (as well
as some more files). copying cc1.exe did not resolve this.
Anyone with some cygwin/gcc experience know what is going wrong, or if
my procedure is correct then do you have a build number that you have
tested and know works (by works I mean allows compilation at the end of
the process)
Cheers
Jim
next reply other threads:[~2006-01-31 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 9:42 James HAUXWELL [this message]
2006-01-31 9:53 ` Brian Dessent
-- strict thread matches above, loose matches on Subject: below --
2005-02-14 22:56 Boaz Lowenstein
2003-09-26 13:16 Compilation problem David Maquenne
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=43DF30F1.90304@st.com \
--to=james.hauxwell@st.com \
--cc=gcc-help@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).