On Tue, Oct 18, 2011 at 7:53 PM, <meino.cra...@gmx.de> wrote:
> meino.cra...@gmx.de <meino.cra...@gmx.de> [11-10-19 04:48]:
>> Mark Knecht <markkne...@gmail.com> [11-10-19 04:40]:
>> > On Tue, Oct 18, 2011 at 7:28 PM, <meino.cra...@gmx.de> wrote:
>> > > Hi,
>> > >
>> > > this morning I got this (after update poppler and xorgserver had to be
>> > > updated):
>> > <SNIP>
>> > > It seems poppler wants a library which version is not available for
>> > > gentoo.
>> > >
>> > >
>> > > If there is need for more information (the mentioned logs for example)
>> > > I will it send it to the list.
>> > >
>> > > Best regards,
>> > > mcc
>> >
>> > On one of my machines I saw a different on the same version of
>> > poppler. I did an emerge -C poppler and then emerge -DuN @world and it
>> > picked up a newer version without complaining.
>> >
>> > HTH,
>> > Mark
>> >
>>
>> Hi Mark,
>>
>> thank you for your help ! :)
>>
>> I tried it and it results in this:
>>
>> solfire:/root>emerge -DuN @world
>> Calculating dependencies... done!
>> [ebuild N ~] app-text/poppler-0.18.0 USE="cairo cxx introspection
>> jpeg jpeg2k lcms png qt4 tiff utils xpdf-headers -cjk -curl -debug -doc"
>>
>> The following keyword changes are necessary to proceed:
>> #required by app-office/libreoffice-3.3.4, required by @selected,
>> required by @world (argument)
>> >=app-text/poppler-0.18.0 ~amd64
>>
>> NOTE: This --autounmask behavior can be disabled by setting
>> EMERGE_DEFAULT_OPTS="--autounmask=n" in make.conf.
>>
>> Use --autounmask-write to write choanges to config files (honoring
>> CONFIG_PROTECT).
>>
>>
>> Is this just another of those cases, where I have to unmask an item
>> and "dont mix 'em" ;) ???
>>
>> Best regards,
>> mcc
>>
>>
>>
>>
>>
>>
>>
>
> Hi Mark,
>
> ok, I unmasked poppler, and it give me that again:
>
>
>
> /var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0/glib/poppler-private.h:126:
> syntax error, unexpected ')', expecting ',' or ';' in ' time_t
> *gdate);' at ')'
> g-ir-scanner: compile: gcc -Wall -pthread -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -march=native -O2 -pipe -msse3
> -I/var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0
> -I/var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0/fofi
> -I/var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0/goo
> -I/var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0/poppler
> -I/var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0_build
> -I/var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0_build/poppler
> -I/usr/include -I/usr/include/freetype2
> -I/var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0/glib
> -I/var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0_build/glib
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/cairo
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/cairo
> -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng15
> -I/usr/include/libdrm -c -o
> /var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0_build/glib/tmp-introspectrj_6Cr/Poppler-0.18.o
>
> /var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0_build/glib/tmp-introspectrj_6Cr/Poppler-0.18.c
> g-ir-scanner: link: gcc -o
> /var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0_build/glib/tmp-introspectrj_6Cr/Poppler-0.18
> -march=native -O2 -pipe -msse3 -L. -Wl,-rpath=. -lpoppler-glib -pthread
> -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0
> /var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0_build/glib/tmp-introspectrj_6Cr/Poppler-0.18.o
> g-ir-scanner: Poppler: warning: 5 warnings suppressed (use --warn-all to
> see them)
> [ 79%] Built target gir-girs
> Scanning dependencies of target gir-typelibs
> [ 79%] Generating Poppler-0.18.typelib
> /usr/bin/g-ir-compiler: error while loading shared libraries: libffi.so.4:
> cannot open shared object file: No such file or directory
> make[2]: *** [glib/Poppler-0.18.typelib] Error 127
> make[1]: *** [glib/CMakeFiles/gir-typelibs.dir/all] Error 2
> make: *** [all] Error 2
> * ERROR: app-text/poppler-0.18.0 failed (compile phase):
> * emake failed
> *
> * If you need support, post the output of 'emerge --info
> =app-text/poppler-0.18.0',
> * the complete build log and the output of 'emerge -pqv
> =app-text/poppler-0.18.0'.
> * The complete build log is located at
> '/var/tmp/portage/app-text/poppler-0.18.0/temp/build.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/app-text/poppler-0.18.0/temp/environment'.
> * S: '/var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0'
>
> >>> Failed to emerge app-text/poppler-0.18.0, Log file:
>
> >>> '/var/tmp/portage/app-text/poppler-0.18.0/temp/build.log'
>
> * Messages for package app-text/poppler-0.18.0:
>
> * ERROR: app-text/poppler-0.18.0 failed (compile phase):
> * emake failed
> *
> * If you need support, post the output of 'emerge --info
> =app-text/poppler-0.18.0',
> * the complete build log and the output of 'emerge -pqv
> =app-text/poppler-0.18.0'.
> * The complete build log is located at
> '/var/tmp/portage/app-text/poppler-0.18.0/temp/build.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/app-text/poppler-0.18.0/temp/environment'.
> * S: '/var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0'
>
> libffi remains the same as in the previous post of mine...
>
> Best regards,
> mcc
I'm not seeing any of that here. A couple of questions:
1) What version of portage are you using? I'm at 2.2.0_alpha69. See my
portage.keywords file from yesterday about how I unmask portage. For
me it's a weird one...
2) Do you have libffi installed? Maybe it's a case of the new poppler
needs libffi but the ebuild isn't emerging it?
c2stable ~ # eix -I libffi
[I] dev-libs/libffi
Available versions: 3.0.9-r2 3.0.10 **3.0.11_rc1 {debug static-libs test}
Installed versions: 3.0.10(01:58:46 PM 10/17/2011)(-debug
-static-libs -test)
Homepage: http://sourceware.org/libffi/
Description: a portable, high level programming interface
to various calling conventions.
[I] virtual/libffi
Available versions: 0
Installed versions: 0(10:42:58 AM 04/13/2010)
Description: Virtual for dev-libs/libffi
Found 2 matches.
c2stable ~ #
That sort of seems to be the case according to equery as poppler isn't
shown below as depending on libffi. I possibly have it because I went
the opposite on this recent -perl/-python news item and have them set.
Just guessing about that though.
c2stable ~ # equery depends libffi
* These packages depend on libffi:
dev-lang/python-2.7.1-r1 (virtual/libffi)
dev-lang/python-3.1.3-r1 (virtual/libffi)
dev-libs/gobject-introspection-0.10.8 (virtual/libffi)
dev-python/pygobject-2.28.6 (libffi ? virtual/libffi)
virtual/libffi-0 (dev-libs/libffi)
c2stable ~ #
So, if you don't have libffi installed then emerge it and try again
with poppler after that. If poppler then emerges correctly then
consider filing a bug report if you feel that's appropriate.
Good luck. I won't be around much longer tonight. I'll catch up with
you tomorrow.
Cheers,
Mark
