On Aug 1, 2012, at 4:42 AM, Daniel Macks <[email protected]> wrote:
> On Tue, 31 Jul 2012 20:47:49 -0400, Daniel Johnson > <[email protected]> wrote: > >> On Jul 31, 2012, at 4:23 PM, Beat Zahnd <[email protected]> wrote: >> >> > Yes, same effect with just 1 build job. >> > > Thanks, Beat >> > On Jul 31, 2012, at 10:14 PM, Alexander Hansen >> <[email protected]> wrote: >> > >> I'll cc the maintainer. I know that he has Mountain Lion. >> >> >> Did you try reducing the number of build jobs to 1? "Unable to open >> >> file..." errors frequently come up when packages aren't set up to build >> >> in multiple threads (though the build worked for me with 4 build jobs on >> >> 10.7/Xcode 4.4). >> >> >> -- >> Alexander Hansen, Ph.D. >> >> Fink User Liaison >> >> My package updates: http://finkakh.wordpress.com/ >> > libvpx does indeed fail to build on 10.8. Turns out it needs GNU >> grep in order to build which I added as a BuildDepends. I also >> updated it to the latest upstream version. > > Now fails on 10.6/i386: > > #!/bin/bash -ev > > let version=`uname -r | cut -d . -f 1` > uname -r | cut -d . -f 1 > #if [ $version -gt 9 ]; then > # let version=9 > #fi > > if [ "i386" = "powerpc" ]; then > ./configure --prefix=/sw --target=ppc32-darwin${version}-gcc > elif [ "i386" = "i386" ]; then > if [ $version = "8" ]; then > ./configure --prefix=/sw > --target=x86-darwin${version}-gcc --disable-postproc > else > ./configure --prefix=/sw > --target=x86-darwin${version}-gcc > fi > else > ./configure --prefix=/sw --target=i386-darwin${version}-gcc > fi > Configuring selected codecs > enabling vp8_encoder > enabling vp8_decoder > Configuring for target 'x86-darwin10-gcc' > enabling x86 > enabling runtime_cpu_detect > enabling mmx > enabling sse > enabling sse2 > enabling sse3 > enabling ssse3 > enabling sse4_1 > using yasm > enabling postproc > Unable to invoke compiler: gcc _dir} -mmacosx-version-min=10.6 -m32 > -arch i386 > > Configuration failed. This could reflect a misconfiguration of your > toolchains, improper options selected, or another problem. If you > don't see any useful error messages above, the next step is to look > at the configure error log file (config.err) to determine what > configure was trying to do when it died. > ### execution of /tmp/fink.G4G1Q failed, exit code 1 > > (sorry for any gremlins in this paste...my email client sucks.) > > Is the logic reversed for i386 vs x86_64 in the CompileScript --target > flag control? I tried flipping it, but now it fails with: > > ./configure --prefix=/sw --target=i386-darwin${version}-gcc > > Configuring selected codecs > enabling vp8_encoder > enabling vp8_decoder > Unrecognized toolchain 'i386-darwin10-gcc' > > Not sure what else to try. I'm as shocked as you that a hand-written > confgure script and build toolchain isn't working portably... I know, right? And it has to be x86 not i386. It seems the build system defaults to x86_64 on 10.6 for some reason, so I made it think it's on darwin9 when it's actually darwin10. See if that helps, otherwise I'm not sure what else to do. Daniel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Fink-users mailing list [email protected] List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
