From: <dan...@ya...> - 2002-06-25 03:25:07
|
--- Luke Dunstan <cod...@ho...> wrote: > > The gcc-3_1-build.sh script on the files list is a good place to start, even > for 2.95.3. I suppose it also depends on whether you are using the Cygwin > environment + Cygwin compiler (which I believe is what the script is > intended for) The script was used from a cygwin bash shell, with cygwin utils in my path, but using "native" mingw compiler and binutils to bootstrap. I use a crippled ln.exe to force hard links, because native mingw toolchain doesn't work with symlinks in this environment. or MSYS environment + Mingw compiler. I have built GCC 3.1 > using MSYS+Mingw before, and the only real difference from the build script > provided was that I used a Win32 path like "--prefix=c:/foo/mingw" instead > of the POSIX one (--prefix=/mingw). You should have mingw-runtime and w32api > in the prefix directory before starting, and you will also need Bison. > You will also need Perl and Deja-Gnu for the testsuite. Danny > Luke > > ----- Original Message ----- > From: "Wu Yongwei" <ad...@ne...> > To: "MinGW-Users" <min...@li...> > Sent: Tuesday, June 25, 2002 10:34 AM > Subject: [Mingw-users] What is the Standard Procedure to Build MinGW GCC > > > > And options? I want info on both GCC 2.95 and GCC 3.1. > > > > Sorry I did not find a link. > > > > Best regards, > > > > Wu Yongwei > > > > ------------------------------------------------------- > Sponsored by: > ThinkGeek at http://www.ThinkGeek.com/ > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users http://www.sold.com.au - SOLD.com.au - Find yourself a bargain! |