Re: [Mingw-msys] need help compiling gcc for windows

[Luke D. <cod...@ho...>]

----- Original Message ----- 
From: "Sheryl Canter" <sh...@pe...>
To: <min...@li...>
Sent: Wednesday, October 08, 2003 9:16 PM
Subject: Re: [Mingw-msys] need help compiling gcc for windows


> Yes, I know the slashes are missing, but I can't figure out why. I changed
> nothing in the MSYS defaults except to add CC=gcc to the profile file.
There
> are no backslashes in the path to the compiler.
>
> I've tried it with CC defined and without. It doesn't work either way.
When
> I define it this way, it seems to work. Typing "gcc -v" shows compiler
info.
> I'm also tried defining CC with a full path (forward slashes), but that
> doesn't work either.
>
> Here is the output of msysinfo all. I very much hope you can find a clue
in
> here. I've spent 18 hours on this, and I can't get it to work.
>
>     - Sheryl

If you need a quick solution you should probably try building a
Cygwin-hosted cross compiler. Personally I haven't built GCC version 3.3.1
with MSYS but I don't know why it would be different to other versions like
3.2.3. Have you succeeded with running configure scripts for packages other
than GCC? (because the way conftest is used should be the same) If you have
time you might look at the configure script to see exactly where it is
getting the path with backslashes from. Are you using the GCC source from
the MinGW download page or the official FSF release? I can't see an obvious
cause in the information you provided. To rule out something in your PATH
that might be conflicting, try:

PATH=.:/usr/local/bin:/mingw/bin:/bin

...in MSYS just before running configure. Does removing the
"--with-local-prefix" option make a difference? On the MinGW download page
is a script gcc-3.3.1-build.sh that has recommended options for configuring
GCC, so you may also try that (except using your desired --prefix).

Has anyone else built GCC 3.3.1 with MSYS? (I'll see if I can try tomorrow)

Luke

>
> ------------------------
>
[snip]
>
> ----- Original Message ----- 
> From: Luke Dunstan
> To: min...@li...
> Sent: Wednesday, October 08, 2003 3:10 AM
> Subject: Re: [Mingw-msys] need help compiling gcc for windows
>
>
>
> That error seems strange to me, and it is due to backslashes somehow
getting
> into a command line when they shouldn't. You normally don't need to set CC
> or CXX environment variables so remove these first. Please provide the
> output of "msysinfo all".
>
> Luke
>
> ----- Original Message ----- 
> From: Sheryl Canter
> To: min...@li...
> Sent: Wednesday, October 08, 2003 2:02 PM
> Subject: [Mingw-msys] need help compiling gcc for windows
>
>
> I'm trying to use MSYS with MINGW to compile gcc for Windows. If I'm ever
> able to get this to work, I would then like to cross compile for a Linux
> target. But I can't get this to work.
>
> In my profile file, I have this line:
>
> CC=gcc CXX=gcc
>
> This seems to be correct because when I type just $CC on a line in MSys it
> lists the correct file:
>
> $ $CC
> gcc.exe: no input files
>
> I also have my mingw directory correctly bound to MSYS in fstab:
>
> C:/mingw   /mingw
>
> The directory /c/mingw/bin is in my path.
>
> But when I try to configure gcc, I get this:
>
> Administrator@TPA21P /c/gcc-objdir
> $
>
c:/Software/gcc/gcc-3.3.1/configure --prefix=c:/gcc-3.3.1 --with-local-prefi
> x
> =c:/gcc/3.3.1
> Configuring for a i686-pc-mingw32 host.
> *** This configuration is not supported in the following subdirectories:
>      target-libffi target-boehm-gc target-zlib target-libjava
>     (Any other directories should still work fine.)
> Created "Makefile" in /c/gcc-objdir using "mh-frag"
> c:/Software/gcc/gcc-3.3.1/configure: c:mingwbingcc.exe: command not found
> *** The command 'c:mingwbingcc.exe -o conftest -g   conftest.c' failed.
> *** You must set the environment variable CC to a working compiler.
>
>
> I'm at my wits end over this. I've been at it all day and all evening, and
> half the night. Please tell me what I'm doing wrong.
>
>     - Sheryl
>