This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin 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] |
There is more work in store before it really works. All I have done is get rid of a few compile time errors and patch the testsuite. There are bugs in the libjava libraries. None of these patches are in the main 3.1 branch. All but the configure.host patch, which is required to build with unmodified binutils, are in the 3.2 branch. At present I bootstrap with a gcc/ada version of gcc-3.1 using the following options. Note that - ARFLAGS=crP is required to build libjava - you can't make gnatlib_and_tools without an ada bootstrap compiler You need dejagnu-1.4.2 to run the g++ tests. Even with that, "make check" will die a horrible death in libjava without a very nasty hack to /usr/share/dejagnu/remote.exp (below) to work around another problem - possibly a cygwin bug - that I haven't followed up. ########## gcc build and test script ######### #!/bin/sh export CYGWIN=check_case:strict export PATH=/usr/local/gcc-3_1/bin:/usr/bin /usr/local/src/gcc-3.1c/configure \ --prefix=/usr/local/gcc-3_1 \ --enable-threads=posix \ --enable-libgcj \ --enable-sjlj-exceptions \ --with-system-zlib \ --disable-nls \ --enable-version-specific-runtime-libs \ --without-included-gettext \ --disable-shared > configure.log 2>&1 make AR_FLAGS=crP bootstrap-lean > build.log 2>&1 || exit (cd gcc; make gnatlib_and_tools >> ../build.log 2>&1 ) make -k check > check.log 2>&1 make warning.log /usr/local/src/gcc-3.1c/contrib/test_summary -t -i warning.log > summary.txt -----Original Message----- From: Nicholas Wourms [mailto:nwourms@netscape.net] Sent: Monday, 10 June 2002 5:07 To: Billinghurst, David (CRTS) Subject: Re: gcj patches for cygwin gcc-3.1 David, Thanks for your hard work! I truly hope this will lead to the day when I can finally drop that crappy JDK with its !@#$ing windows path conventions. I think it is a bigger PITA then anything else. Cheers, Nicholas
Attachment:
remote.exp.diff
Description: remote.exp.diff
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |