On Oct 31, 2008, at 16:32, Bart Masschelein wrote:
---> Configuring pango
Error: Target org.macports.configure returned: configure failure:
shell command " cd "/opt/local/var/macports/build/
_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_p
ango/work/pango-1.22.2" && ./configure --prefix=/opt/local --x-
includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib --enable-
static --enable-cairo " returned error 1
Command output: appending configuration tag "CXX" to libtool
checking for ld used by /usr/bin/g++-4.0... /usr/libexec/gcc/i686-
apple-darwin9/4.0.1/ld
checking if the linker (/usr/libexec/gcc/i686-apple-darwin9/4.0.1/
ld) is GNU ld... no
checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/i686-
apple-darwin9/4.0.1/ld) supports shared libraries... yes
checking for /usr/bin/g++-4.0 option to produce PIC... -fno-common
checking if /usr/bin/g++-4.0 PIC flag -fno-common works... yes
checking if /usr/bin/g++-4.0 static flag -static works... no
checking if /usr/bin/g++-4.0 supports -c -o file.o... yes
checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/i686-
apple-darwin9/4.0.1/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin9.5.0 dyld
(cached) (cached) checking how to hardcode library paths into
programs... immediate
appending configuration tag "F77" to libtool
checking for some Win32 platform... no
checking for perl5... no
checking for perl... perl
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking whether -R must be followed by a space... no
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for FONTCONFIG... no
checking Carbon/Carbon.h usability... yes
checking Carbon/Carbon.h presence... yes
checking for Carbon/Carbon.h... yes
checking for CAIRO... no
checking for GLIB... configure: error:
*** Glib 2.17.3 or better is required. The latest version of
*** Glib is always available from ftp://ftp.gtk.org/.
Note it's not finding fontconfig or cairo either, which are also
required by pango.
Then attach pango.txt.bz2 from your desktop to your reply.
Here you go, hope it is any help to you:
<pango.txt.bz2>
The output in your pango.txt is different from what you pasted above.
In pango.txt, it is finding fontconfig, cairo, glib2 and everything
else, and building correctly.
Not sure why it's different now than before, though it could easily
have been the Leopard Tcl environment variable bug, since it has so
many and varied symptoms:
http://trac.macports.org/wiki/
LeopardProblems#environmentvariablesbecomeblankbetweenconfigureandbuildp
hases
When I try upgrading now, using sudo port upgrade mono-addins, I
get the following:
---> Activating giflib 4.1.6_0
Error: Activating giflib 4.1.6_0 failed: Image error: /opt/local/
bin/gif2epsn is being used by the active libungif port. Please
deactivate this port first, or use the -f flag to force the
activation.
---> Activating pango 1.22.2_0
Error: Activating pango 1.22.2_0 failed: Image error: Another
version of this port (pango @1.22.0_0) is already active.
---> Activating pango 1.22.2_0
Error: Activating pango 1.22.2_0 failed: Image error: Another
version of this port (pango @1.22.0_0) is already active.
About the first error, is it in general ok to force the activation?
To me it sounds not recommendable.
No. Instead, you should deactivate libungif and then activate giflib.
There is unfortunately some confusion between giflib and libungif.
libungif was created while the GIF algorithm was still covered by a
patent. The patent has since expired, so now the full giflib is
preferred. But many ports still depend on libungif. Those that can
should be upgraded to use giflib. Those that can't should have bugs
filed with their developers.
The second error is more weird. After using your commands (sudo
port clean pango; sudo port -d install pango 2>&1 | tee ~/Desktop/
pango.txt; bzip2 ~/Desktop/pango.txt ), it went through, but it was
not able to activate. It should automatically desactivate the old
and install the new one, no?
No, since you used "install". If you had used "upgrade" instead, it
would have done so. So now you should:
sudo port deactivate pango @1.22.0_0
sudo port activate pango @1.22.2_0
sudo port clean pango
And what is the difference between my install and your commands?
You only put -d, which I assume is debug. Does -d do something else?
-d produces debug and verbose output. 2>&1 redirects stderr (where
the debug output appears) to stdout (so it will be piped to tee), and
tee sends the output to a file while also showing it on screen. bzip2
compresses the file.
Could all of this have to do with my attempt to upgrade mono-addins
myself, altering my local repository. I followed the guidelines of
MacPorts, and everything seemed to go as expected... Any ideas?
Modifying your local ports tree and upgrading mono-addins yourself
should have been fine.
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
