This is the mail archive of the
mailing list for the Cygwin project.
Re: gcc-4.5 notes
- From: Reini Urban <rurban at x-ray dot at>
- To: cygwin at cygwin dot com
- Date: Wed, 25 Aug 2010 16:20:10 +0200
- Subject: Re: gcc-4.5 notes
- References: <1281990025.7012.82.camel@YAAKOV04>
Aside from Yaakov's notes I have nothing to fix.
Just to add that it is working fine for me. I've rebuilt
some of my perls with extensive testsuites and everything
so far was fine.
Yaakov's tests are obviously better than mine.
May I ask when can we expect gcc-4.5.0 going stable?
Because I want the pending perl-5.10.1-4 update which changes
cc from gcc to gcc-4 and fixes some more minor stuff to be done
with the new gcc-4.5.x.
But if it's more than one week I'll revert to the old compiler.
2010/8/16 Yaakov (Cygwin/X):
> Several notes about gcc-4.5.0:
> 1) I'm using a new FIONREAD patch for Classpath which solves several
> issues. ?Matching patch for gcc-4.5 attached.
> 2) fix-libtool-scripts-for-latest-gcc-runtimes.sh doesn't actually do
> anything; 's|echo sed|sed|g' fixes that.
> 3) libgnat import libs are missing:
> $ gnatmake hello.adb -bargs -shared
> gcc -c hello.adb
> gnatbind -shared -x hello.ali
> gnatlink hello.ali -shared-libgcc
> cannot find -lgnat-4.5
> collect2: ld returned 1 exit status
> gnatlink: error when calling /usr/bin/gcc.exe
> gnatmake: *** link failed.
> Looking at gcc/ada/gcc-interface/Makefile.in, it looks like there is
> supposed to be a adalib/libgnat-4.5.dll.a symlink, but it's not quite
> right. ?Patch for 4.5.1 attached.
> 4) After creating said symlink, the resulting binary outputs "Hello,
> world!" but does not exit, and requires kill -f to terminate. ?The same
> code linked statically (IOW w/o "-bargs -shared") runs and exits
> 5) Several -4-suffixed programs have no unversioned alternatives; this
> includes: aot-compile, gccbug, jcf-dump, rebuild-gcj-db. ?(Of course, if
> we drop gcc3, or at least its alternatives, then gcc4 can be
> unversioned, making this point moot.)
> 6) Are the gcj tools working? ?If not, perhaps they should just be
> dropped until they get figured out. ?An alternative would be for me to
> ITP my Classpath-based stack.
> 7) jni.h and jni_md.h should probably be shipped with gcc4-java instead
> of gcc4-core.
> 8) It would be helpful if gcc4-core would provide a libffi.pc pkg-config
> file, since for us this is *the* libffi.
http://phpwiki.org/? ? ? ? ?? http://murbreak.at/
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple