Opened 15 years ago

Closed 15 years ago

#6105 closed defect (invalid)

BUG: port metacity doesn't build under 10.4

Reported by: olaf@… Owned by: gnome-darwinports@…
Priority: Normal Milestone:
Component: ports Version: 1.0
Keywords: Cc:


$ sudo port build metacity ---> Configuring metacity Error: Target returned: configure failure: shell command "cd "/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_gnome_metacity/work/metacity-2.12.0" && CPPFLAGS="-I/opt/local/include -L/opt/local/lib" ./configure --prefix=/opt/local --mandir=/opt/local/share/man" returned error 1 Command output: checking execinfo.h presence... no checking for execinfo.h... no checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... no checking for bindtextdomain in -lintl... yes checking for ngettext in -lintl... yes checking for dgettext in -lintl... yes checking for bind_textdomain_codeset... yes checking for msgfmt... /opt/local/bin/msgfmt checking for dcgettext... yes checking for gmsgfmt... /opt/local/bin/msgfmt checking for xgettext... /opt/local/bin/xgettext checking for catalogs to be installed... am ar az be bg bn bs ca cs cy da de el en_CA en_GB es et eu fa fi fr ga gl gu he hi hr hu hy id is it ja ko lt lv mk ml mn ms nb ne nl nn no or pa pl pt pt_BR ro ru rw sl sk sq sr sr@Latn sv ta th tk tr uk vi wa xh zh_CN zh_TW checking for pkg-config... /opt/local/bin/pkg-config checking for glib-2.0 >= 2.6.0... yes checking ALL_CFLAGS... -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include checking ALL_LIBS... -L/opt/local/lib -lglib-2.0 -lintl -liconv checking for gtk+-2.0 >= 2.6.0... yes checking METACITY_MESSAGE_CFLAGS... -I/opt/local/include/gtk-2.0 -I/opt/local/lib/gtk-2.0/include -I/opt/local/include/atk-1.0 -I/opt/local/include/cairo -I/opt/local/include/pango-1.0 -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include checking METACITY_MESSAGE_LIBS... -L/opt/local/lib -L/usr/X11R6/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -ltiff -ljpeg -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lintl -liconv -lfreetype -lfontconfig -lXrender -lX11 -lpng12 -lz checking for gtk+-2.0 >= 2.6.0... yes checking METACITY_WINDOW_DEMO_CFLAGS... -I/opt/local/include/gtk-2.0 -I/opt/local/lib/gtk-2.0/include -I/opt/local/include/atk-1.0 -I/opt/local/include/cairo -I/opt/local/include/pango-1.0 -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include checking METACITY_WINDOW_DEMO_LIBS... -L/opt/local/lib -L/usr/X11R6/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -ltiff -ljpeg -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lintl -liconv -lfreetype -lfontconfig -lXrender -lX11 -lpng12 -lz configure: error: "Pango 1.2.0 or greater based on Xft2 is required"

Error: The following dependencies failed to build: py-gnome nautilus librsvg metacity py-gtk2 py-numeric py-orbit Error: /opt/local/bin/port: Status 1 encountered during processing.

Of course pango is installed:

s$ port installed pango The following ports are currently installed:

pango @1.10.1_0 (active)

Change History (2)

comment:1 Changed 15 years ago by rhwood@…

An email conversation about this bug:

Please send the output of "port installed" I am wondering if your pango was built differently than mine and if perhaps I will see that in the list of installed packages.

here it is. Maybe pango should have been installed in an xterm in

This seems to have solved the problem, metacity just builds that means it has passed the configuring phase that has failed earlier.

That should not have made a difference. If you have other build problems with X11-based ports and this works, please report them to the mailing list, along with the contents of your .profile and .xinitrc files.

The suspicious line in .profile is

TERM=xterm-color export TERM

Does this disturb the build? Usually I use

==== I am unable on two machines to reproduce this bug, and propose calling it a fluke.

comment:2 Changed 15 years ago by olaf@…

Resolution: invalid
Status: newclosed

It's been a local issue on my machine, thanks for Randalls support.

Note: See TracTickets for help on using tickets.