On 7/2/2010 2:36 AM, JonY wrote: > Here are the GCC links. I hope I got them all.
mingw64-m32-libgcc1-4.6.20100619-1.tar.bz2 mingw64-m32-libgfortran3-4.6.20100619-1.tar.bz2 mingw64-m32-libgomp1-4.6.20100619-1.tar.bz2 mingw64-m32-libobjc2-4.6.20100619-1.tar.bz2 mingw64-m32-libssp0-4.6.20100619-1.tar.bz2 mingw64-m32-libstdc++6-4.6.20100619-1.tar.bz2 mingw64-m64-libgcc1-4.6.20100619-1.tar.bz2 mingw64-m64-libgfortran3-4.6.20100619-1.tar.bz2 mingw64-m64-libgomp1-4.6.20100619-1.tar.bz2 mingw64-m64-libobjc2-4.6.20100619-1.tar.bz2 mingw64-m64-libssp0-4.6.20100619-1.tar.bz2 mingw64-m64-libstdc++6-4.6.20100619-1.tar.bz2 mingw64-tc64-gcc4-4.6.20100619-1.tar.bz2 mingw64-tc64-gcc4-4.6.20100619-1-src.tar.bz2 mingw64-tc64-gcc4-g++-4.6.20100619-1.tar.bz2 mingw64-tc64-gcc4-objc-4.6.20100619-1.tar.bz2 mingw64-tc64-m32-libgfortran3-devel-4.6.20100619-1.tar.bz2 mingw64-tc64-m32-libgomp1-devel-4.6.20100619-1.tar.bz2 mingw64-tc64-m32-libobjc2-devel-4.6.20100619-1.tar.bz2 mingw64-tc64-m32-libssp0-devel-4.6.20100619-1.tar.bz2 mingw64-tc64-m32-libstdc++6-devel-4.6.20100619-1.tar.bz2 mingw64-tc64-m64-libgfortran3-devel-4.6.20100619-1.tar.bz2 mingw64-tc64-m64-libgomp1-devel-4.6.20100619-1.tar.bz2 mingw64-tc64-m64-libobjc2-devel-4.6.20100619-1.tar.bz2 mingw64-tc64-m64-libssp0-devel-4.6.20100619-1.tar.bz2 mingw64-tc64-m64-libstdc++6-devel-4.6.20100619-1.tar.bz2 Packaging looks good, but I haven't reviewed the setup.hints yet. Rebuiling from -src: well, I ran into a problem. cygport ... prep: ok cygport ... build: ok cygport ... install: errors in postinstall: > cp: cannot stat `/usr/src/devel/mingw64/gcc/r/mingw64-tc64-gcc4-4.6.20100619-1/inst/opt/mingw64/lib/gcc/x86_64-w64-mingw32/lib/libgcc_s.a': No such file or directory > cp: cannot stat `/usr/src/devel/mingw64/gcc/r/mingw64-tc64-gcc4-4.6.20100619-1/inst/opt/mingw64/lib/gcc/x86_64-w64-mingw32/lib32/libgcc_s.a': No such file or directory That's from this bit: # Remove redundant libgcc rm -f ${D}/opt/mingw64/lib/gcc/x86_64-w64-mingw32/lib/libgcc_s.a rm -f ${D}/opt/mingw64/lib/gcc/x86_64-w64-mingw32/lib32/libgcc_s.a # Workaround GCC install bug cp -pf ${D}/opt/mingw64/lib/gcc/x86_64-w64-mingw32/lib/libgcc_s.a ${D}/opt/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.0/ cp -pf ${D}/opt/mingw64/lib/gcc/x86_64-w64-mingw32/lib32/libgcc_s.a ${D}/opt/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.0/32/ I don't onder stand how the first two lines can be followed by the second two? I mean, how can you copy a file AFTER you remove it? So maybe the order of those should be reversed. > *** Warning: Cygwin README is missing You need a README file of some kind in CYGWIN-PATCHES. It will be installed as /usr/share/doc/Cygwin/mingw64-tc64-gcc4.README, and should contain cygwin-specific information about the port. > realpath: No such file or directory > /usr/lib/cygport/src_postinst.cygpart: line 586: [: !=: unary operator expected > opt/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.0/32/libgfortran.la This is part of __prep_libtool_modules(), and happens because: if [ "x${shouldnotlink}" != "xyes" ] Eg. this is the bit where "cygport munges libtool files" and you had already said you want to suppress this behavior -- and are waiting for my cygport patch. It looks like you really can't go any further with this until I write that patch, Yaakov accepts it, and a new cygport is released -- or you use a different workaround. I wonder what Dave Korn's gcc cygport does in this case? Anyway, then cygport goes off and sucks 100% of CPU so I had to kill it. -- Chuck