From: Andy Howell <AndyHowell@austin.rr.com>
To: gcc-help@gcc.gnu.org
Cc: Sheryl Canter <sheryl@permutations.com>
Subject: Re: need help compiling gcc for Windows
Date: Thu, 09 Oct 2003 14:26:00 -0000 [thread overview]
Message-ID: <3F856FC9.9010707@austin.rr.com> (raw)
In-Reply-To: <03c001c38dec$e95efaa0$6401a8c0@tpa21p>
Sheryl Canter wrote:
> If no ideas on the problem below, then at least help me to find it myself?
>
> I'm knew to Unix and can't tell exactly what is happening when I issue the
> command "make bootstrap". If I knew what files were being executed, perhaps
> I could find the problem.
>
> Someone please help??
>
> - Sheryl
>
>
> ----- Original Message -----
> From: "Sheryl Canter" <sheryl@permutations.com>
> To: <gcc-help@gcc.gnu.org>
> Sent: Wednesday, October 08, 2003 5:15 PM
> Subject: Re: need help compiling gcc for Windows
>
>
> Please, somebody help me with this! I'm completely stuck.
>
> The configure is completing correctly (as far as I can tell), but the
> build didn't work. It works up to this point:
>
> ------------
> Bootstrapping the compiler
> make[1]: Entering directory `/c/gcc-objdir/gcc'
> make AR_FOR_TARGET="ar" \
> RANLIB_FOR_TARGET="ranlib" \
> CC="gcc" libdir=/c/gcc-3.3.1/lib LANGUAGES="c " \
> CFLAGS="-g " MAKEINFO="makeinfo --no-split" \
> MAKEINFOFLAGS="" COVERAGE_FLAGS=
> make[2]: Entering directory `/c/gcc-objdir/gcc'
> ./gengtype
> /c/gcc-srcdir/gcc-3.3.1/gcc/../include/ansidecl.h: No such file or directory
> make[2]: *** [s-gtype] Error 1
> make[2]: Leaving directory `/c/gcc-objdir/gcc'
> make[1]: *** [stage1_build] Error 2
> make[1]: Leaving directory `/c/gcc-objdir/gcc'
> make: *** [bootstrap] Error 2
> ------------
>
> That file spec with the error message looks a little strange, but it
> correctly points to the file. ansidecl.h can be found here:
>
> /c/gcc-srcdir/gcc-3.3.1/include/ansidecl.h
>
> Any idea why the build didn't work? How do I correct this problem?
>
> - Sheryl
>
Its been a long time since I built gcc, and never have done it on
windows...
Is gengtype a shell script? If so, cd to /c/gcc-objdir/gcc and run:
sh -x ./gengtype
This may give some idea why it is not finding the file.
If it is an binary executable, then if you have the "strace" command,
you could do
strace -o out ./gengtype
Look in the file 'out' to see what it doing. You could grep:
egrep 'open|stat' out
Which will show you the files that gengtype is trying to open or find
info on (stat).
Hope this helps.
Andy
next prev parent reply other threads:[~2003-10-09 14:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 13:15 cross compiling question Sheryl Canter
2003-10-08 2:27 ` need help compiling for Windows Sheryl Canter
2003-10-08 4:52 ` Sheryl Canter
2003-10-08 5:16 ` Philip Walford
2003-10-08 5:26 ` Sheryl Canter
2003-10-08 13:36 ` Sheryl Canter
2003-10-08 16:08 ` need help compiling gcc " Sheryl Canter
2003-10-08 21:15 ` Sheryl Canter
2003-10-08 22:38 ` Sheryl Canter
2003-10-09 14:26 ` Andy Howell [this message]
2003-10-09 15:20 ` Sheryl Canter
2003-10-09 15:23 ` Sheryl Canter
2003-10-09 18:48 ` Sheryl Canter
2003-10-09 21:53 ` Sheryl Canter
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=3F856FC9.9010707@austin.rr.com \
--to=andyhowell@austin.rr.com \
--cc=gcc-help@gcc.gnu.org \
--cc=sheryl@permutations.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).