Prof A Olowofoyeku (The African Chief) wrote:
What environment are you using to build? Perhaps the "c:/mingw" prefix is a problem.
I'm using msys. Usually it deals well with "c:/".
Attached is an amended version of the script that I use (I build under the Mingw + MSYS environment). The script is based on the output of "gcc -v" which shows the configure parameters that were used to build gcc.
Thanks! Could you give me some instructions on how to use the script? Where in my directory tree should I put it? Should I unpack the gpc and gcc tarballs in a certain manner before? (E.g. unpack gpc right into the gcc-3.2.1 dir tree or something?)
My first attempts were fruitless: Putting the script into the gcc subdirectory of gcc-3.2.1 (seemed logical to me, since you're calling ../configure in the script) yielded the error message:
make: *** No rule to make target `../libiberty/libiberty.a', needed by `gengenrtl.exe'. Stop.
Changing the "../configure" into "./configure" and putting the script into gcc-3.2.1/ first seemed to run well first, but it aborted after a while complaining about undefined references to the libgpc. Changing the --prefix clause from "/mingw" into "/c/mingw" doesn't change things here. After I `made clean' and repeated with these adjustments, the system headers (e.g. time.h) weren't found anymore.
What now?
Thank you,
Markus