Hi Dave, Hi Yaakov, On Aug 12 11:21, Yaakov (Cygwin/X) wrote: > On Fri, 2011-08-12 at 16:48 +0100, Dave Korn wrote: > > Thanks. I'm not too sure about not installing the .la files; won't that > > potentially lead to problems for libtool-using projects at link time? > > No, but that reminded me, the libtool fixup script needs a small tweak > to adjust. I just pushed that to Ports git. > > > I just started a build and test cycle using your updated patches+cygport > > script; since you have about a million packages to maintain, I may as well > > take care of releasing this and free you up for other stuff. > > OK. FHI, last month, I tried sending the following patches upstream: > > top-level: fix config.rpath for cygwin/mingw > http://gcc.gnu.org/ml/gcc-patches/2011-07/msg01578.html > http://sourceware.org/ml/binutils/2011-07/msg00181.html > http://sourceware.org/ml/gdb-patches/2011-07/msg00563.html > > cygwin/mingw: update LIBGCJ_SONAME > http://gcc.gnu.org/ml/gcc-patches/2011-07/msg01579.html > > libjava: add comment to libtool-version > http://gcc.gnu.org/ml/java-patches/2011-q3/msg00023.html > > AFAICS they've gone absolute nowhere. Maybe you'll have better luck.
here's a minor nit, but that bugs me for a while now. $ cc hello.c $ ./a.out bash: ./a.out: No such file or directory I would like to see that GCC for Cygwin creates the output file "a.out.exe", so the result is the same on Unix/Linux and Cygwin: $ cc hello.c $ ./a.out hello, world Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat