This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [MinGW] Set NATIVE_SYSTEM_HEADER_DIR relative to configured prefix

On 12/17/06, Bob Rossi <> wrote:
> You're not using "/mingw" as the value for "--prefix". I remember
> stuff not working because of this, though I cannot be sure if that
> indeed is the problem here.

Duh! OK, I'll try that change. Do I need to do this for binutils also?

The tools in binutils (ld, as, etc.) are directly invoked by GCC with the correct parameters while compiling. Therefore, I don't think you need to do this.

Do I even need to build binutils? The only reason I am, is because you
did it on your web page when cross compiling.

It's not necessary - you should be able to use the latest pre-compiled native binutils binaries available from the MinGW site. I needed to compile it for the cross-compiling case since I needed binutils running on Linux creating binaries for MinGW. I admit that I did not really need it for the crossed-native-compiling case, but I was just being masochistic. :-)

I haven't used the "--with-local-prefix" option and I don't
know if it is interfering with anything here. Note that Danny
also posts his build script every time he uploads a new
MinGW GCC release and you can see for yourself just how
the released GCC for MinGW is built. For example, for
GCC 3.4.2, the build script is:

You can find this on the files page for

Finally, I must admit that building GCC for MinGW natively
on Windows with MSYS was just a diversion for me. I
used to always build GCC for MinGW using the crossed-native
compilation process that I have outlined in the document
that I linked to earlier.


Ranjit Mathew      Email: rmathew AT gmail DOT com

Bangalore, INDIA. Web:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]