-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Luke Stras wrote: > My original message appears to have gotten lost in the moderation > queue -- probably due to an oversized attachment. I've pulled the > attachment, and am trying again... > > (note to moderators: my original message can now be safely discarded) >
too late > On Fri, Jul 31, 2009 at 7:53 PM, Alexander Hansen wrote: > >> Yeah, you're going to need to look a bit earlier in the build for some >> other error. Instead of completely failing on that error, the build >> procedure continued on with an incomplete package. >> >> It's also a good idea to mention things like your architecture, OS >> version, and Xcode version. > > Indeed. > > Highwind:~ stras$ uname -a > Darwin Highwind.local 9.7.0 Darwin Kernel Version 9.7.0: Tue Mar 31 > 22:52:17 PDT 2009; root:xnu-1228.12.14~1/RELEASE_I386 i386 > > [OS X 10.5] 10.5.7, that is. > > Highwind:~ stras$ gcc -v > Using built-in specs. > Target: i686-apple-darwin9 > Configured with: /var/tmp/gcc/gcc-5484~1/src/configure > --disable-checking -enable-werror --prefix=/usr --mandir=/share/man > --enable-languages=c,objc,c++,obj-c++ > --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ > --with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib > --build=i686-apple-darwin9 --with-arch=apple --with-tune=generic > --host=i686-apple-darwin9 --target=i686-apple-darwin9 > Thread model: posix > gcc version 4.0.1 (Apple Inc. build 5484) > > [XCode 3.1] On Leopard and later 'xcodebuild -version | head -n 1' gives the Xcode version. I personally don't ever remember the conversions between different gcc-4.0.1 builds and their corresponding Xcode versions. The minor digits are often important, especially for Xcode: there is a huge difference between 3.1.1 and 3.1.2 and 3.1.3 in terms of how things build on Fink. > > I've put a full build log at > <http://delta.utias-sfl.net/~lstras/taglib.log>; this comes from > > sudo fink install taglib > > (since the update was failing, I thought that I would just try to > install the package; it fails identically to the update). As it should. If a package builds differently depending on what is installed, e.g. during a mass update, then it is somewhat broken by our standards and requires fixing. > > There's nothing obviously wrong in the log -- at least, not that I > could spot. If someone else notices what's going on, I will be very > grateful. > > Thanks. I get an identical failure. Unfortunately, since this is a cmake-based build system, it's not very verbose in its output. I built this same version at one point, so something must have changed on my system that causes it not to build. I'll see if I can come up with anything obvious. - -- Alexander Hansen Fink User Liaison -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkp3HlsACgkQB8UpO3rKjQ941wCgoCG/kq4jdWyskipovcMPgdn7 s34AoKSzyB74pXvRfdpNuTov0CmnFyGE =AEe6 -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
