Opened 20 years ago
Closed 19 years ago
#2988 closed defect (fixed)
BUG: p5-glib will not build on mac os x 10.3.9
Reported by: | tomaz.solc@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.0 |
Keywords: | Cc: | ||
Port: |
Description
I get the following error message when I try to install port "p5-glib":
darwin:~/darwinports/dports$ sudo port install p5-glib Password: ---> Building p5-glib with target all Error: Target com.apple.build returned: shell command "cd "/Users/tomaz/darwinports/dports/perl/ p5-glib/work/Glib-1.042" && make all" returned error 2 Command output: rm -f blib/arch/auto/Glib/Glib.bundle LD_RUN_PATH="/opt/local/lib" env MACOSX_DEPLOYMENT_TARGET=10.3 cc -L/opt/local/lib -bundle -undefined dynamic_lookup -L/usr/local/lib Glib.o GError.o GUtils.o GLog.o GType.o GBoxed.o GObject.o GValue.o GClosure.o GSignal.o GMainLoop.o GIOChannel.o GParamSpec.o gperl-gtypes.o -o blib/arch/auto/Glib/Glib.bundle -L/opt/local/lib -lgobject-2.0 -lgthread-2.0 ld: warning -prebind has no effect with -bundle ld: Glib.o illegal reference to symbol: _g_filename_from_uri defined in indirectly referenced dynamic library /opt/local/lib/libglib-2.0.0.dylib make: * [blib/arch/auto/Glib/Glib.bundle] Error 1
Updating my dports tree and upgrading all ports does not help. Computer is running on Mac OS X 10.3.9. Ports that "p5-glib" depends on (perl5.8, glib2, p5-extutils-depends, p5-extutils- pkgconfig) are installed and active (according to "port installed" command)
Change History (3)
comment:1 Changed 20 years ago by mww@…
Summary: | p5-glib will not build on mac os x 10.3.9 → BUG: p5-glib will not build on mac os x 10.3.9 |
---|
comment:2 Changed 19 years ago by olegb@…
comment:3 Changed 19 years ago by tomaz.solc@…
Resolution: | → fixed |
---|---|
Status: | new → closed |
It works now.
"p5-glib" installed successfully after upgrading "pkgconfig" and "glib2" ports and executing "port clean p5-glib"
Thank you.
it works here at least on 10.4.
Could this be a sign of the broken pkg-config we once had ?
Are you still having this problem (with an upgraded pkgconfig) ?