Attempting to emerge poppler-0.5.0, I had the following failure. Emerging
libglade allowed poppler to merge successfully.
Making all in test
make[2]: Entering directory
`/tmp/portage/poppler-0.5.0/work/poppler-0.5.0/test'
if x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../poppler -I..
-I../poppler
then mv -f ".deps/gtk-splash-test.Tpo" ".deps/gtk-splash-test.Po"; else rm -f
".deps/gtk
cc1plus: note: -freorder-blocks-and-partition does not work with exceptions
cc1plus: note: -freorder-blocks-and-partition does not work with exceptions
/bin/sh ../libtool --tag=CXX --mode=link x86_64-pc-linux-gnu-g++ -Wall
-Wno-unused -mar
mkdir .libs
x86_64-pc-linux-gnu-g++ -Wall -Wno-unused -march=k8 -Os -pipe
-fomit-frame-pointer -fren
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.0-beta20060113/../../../../x86_64-pc-linux-gnu/bin/
collect2: ld returned 1 exit status
make[2]: *** [gtk-splash-test] Error 1
make[2]: Leaving directory `/tmp/portage/poppler-0.5.0/work/poppler-0.5.0/test'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/portage/poppler-0.5.0/work/poppler-0.5.0'
make: *** [all] Error 2
While investigating that, I discovered that while an emerge -pvuD poppler says
-cairo for USE, it ends up with cairo in the dependency graph (equery g
poppler|grep cairo) anyway. Since both cairo and glade are gtk/gnome
technology related, perhaps the two dependency errors are connected?
emerge info to be attached.
Created an attachment (id=77735) [details]
emerge info
I'm way out front, with gcc-4.1-beta and running an unreleased 2006.0 profile,
but that shouldn't affect dependencies such as this, in any way I can see, so I
went ahead and filed the bug.
Duncan
