On Oct 24, 2008, at 8:54 AM, Ben Rooney wrote: > Trying to install gnucash2 on MacOS 10.4.11. > Using Package manager version: 0.28.6 > Distribution version: selfupdate-rsync Fri Oct 24 10:56:15 2008, > 10.4, powerpc > > Have successfully done fink selfudate, and upgrade-all with no extra > packages being added. But when I try and install gnucash2 it fails on > evince. > > Failed: phase compiling: evince-2.20.2-5 failed > > When I try and just install evince it fails in the same way. > Having searched through the archive I checked that GS was the right > version > > checking for Ghostscript version...... found 8 > > This is the error report: > > collect2: ld returned 1 exit status > make[2]: *** [libevince-properties-page.la] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > ### execution of /var/tmp/tmp.1.Erpzi3 failed, exit code 2 > Removing runtime build-lock... > Removing build-lock package... > /sw/bin/dpkg-lockwait -r fink-buildlock-evince-2.20.2-5 > (Reading database ... 84973 files and directories currently > installed.) > Removing fink-buildlock-evince-2.20.2-5 ... > Failed: phase compiling: evince-2.20.2-5 failed > > > during the configuration phase it reports screens full of stuff as > per norm. Only the following are reported as 'no' > checking for g77... no > checking for xlf... no > checking for f77... no > checking for frt... no > checking for pgf77... no > checking for cf77... no > checking for fort77... no > checking for fl32... no > checking for af77... no > checking for xlf90... no > checking for f90... no > checking for pgf90... no > checking for pghpf... no > checking for epcf90... no > checking if gcc supports -fno-rtti -fno-exceptions... no > checking if gcc static flag -static works... no > checking if g++ static flag -static works... no > checking for ngettext in libc... no > checking execinfo.h usability... no > checking execinfo.h presence... no > checking for execinfo.h... no > > Not quite sure where else to look. Any help would be hugely > appreciated. > > Many thanks > Ben > >
Your "error report" isn't really useful. You're reporting what the build system is saying after the real error, and many different problems could potentially give the same message there. Check your output and find where the error messages _start_, then post starting with the line from the compiler/linker that occurs immediately before that. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Fink-beginners mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.beginners
