On Oct 25, 2007, at 12:03, Marcus Vinicius Eiffle Duarte wrote:
Hey, folks!
I downloaded and installed MacPorts 1.5 on my PowerMac G5. I
successfulyy installed a few ports (Dia, EasyTag, Bluefish, Ginac),
but did not succeed in installing Planner. The problem occurs
during building of autoconf-2.61. From the error message (see
snippet below), I figured out that the problem involves the
libSystemStubs, so I manually added "-lSystemStubs" to autoconf's
Makefile. However, I got the exact same error message when tried to
build autoconf again.
Does anyone know how can I successfully build it? I am running
MacOSX 10.4.10.
Thanks in advance,
--
Marcus Vinicius Eiffle Duarte
[EMAIL PROTECTED]
Niterói, RJ, Brasil
<snippet>
macctp8:~ ctp8$ sudo port install -d -p -f -v autoconf
Password:
---> Building autoconf with target all
Error: Target org.macports.build returned: shell command " cd "/opt/
local/var/macports/build/_Users_ctp8_MacPorts_dports_devel_autoconf/
work/autoconf- 2.61" && make all " returned error 2
Command output: Making all in bin
autom4te_perllibdir='..'/lib AUTOM4TE_CFG='../lib/
autom4te.cfg' ../bin/autom4te -B '..'/lib -B '..'/
lib --language M4sh --cache '' --melt ./autoconf.as -o
autoconf.in
dyld: lazy symbol binding failed: Symbol not found: _sprintf$LDBLStub
Referenced from: /opt/local/lib/perl5/5.8.8/darwin-2level/auto/
Data/Dumper/Dumper.bundle
Expected in: dynamic lookup
dyld: Symbol not found: _sprintf$LDBLStub
Referenced from: /opt/local/lib/perl5/5.8.8/darwin-2level/auto/
Data/Dumper/Dumper.bundle
Expected in: dynamic lookup
make[1]: *** [ autoconf.in] Trace/BPT trap
make: *** [all-recursive] Error 1
Error: Status 1 encountered during processing.
</snippet>
It looks like this problem has come up before. It was a problem with
gcc versions. See my previous response and see if the solution
mentioned there helps you:
http://lists.macosforge.org/pipermail/macports-users/2007-April/
002440.html
If you are still using MacPorts 1.5.0, you should upgrade to the
latest (currently 1.5.2) using "sudo port selfupdate". MacPorts has
been cleaned up to automatically use the right gcc, but I believe
that was after 1.5.0.
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
