1 |
On Tue, Oct 18, 2011 at 7:53 PM, <meino.cramer@×××.de> wrote: |
2 |
> meino.cramer@×××.de <meino.cramer@×××.de> [11-10-19 04:48]: |
3 |
>> Mark Knecht <markknecht@×××××.com> [11-10-19 04:40]: |
4 |
>> > On Tue, Oct 18, 2011 at 7:28 PM, <meino.cramer@×××.de> wrote: |
5 |
>> > > Hi, |
6 |
>> > > |
7 |
>> > > this morning I got this (after update poppler and xorgserver had to be |
8 |
>> > > updated): |
9 |
>> > <SNIP> |
10 |
>> > > It seems poppler wants a library which version is not available for |
11 |
>> > > gentoo. |
12 |
>> > > |
13 |
>> > > |
14 |
>> > > If there is need for more information (the mentioned logs for example) |
15 |
>> > > I will it send it to the list. |
16 |
>> > > |
17 |
>> > > Best regards, |
18 |
>> > > mcc |
19 |
>> > |
20 |
>> > On one of my machines I saw a different on the same version of |
21 |
>> > poppler. I did an emerge -C poppler and then emerge -DuN @world and it |
22 |
>> > picked up a newer version without complaining. |
23 |
>> > |
24 |
>> > HTH, |
25 |
>> > Mark |
26 |
>> > |
27 |
>> |
28 |
>> Hi Mark, |
29 |
>> |
30 |
>> thank you for your help ! :) |
31 |
>> |
32 |
>> I tried it and it results in this: |
33 |
>> |
34 |
>> solfire:/root>emerge -DuN @world |
35 |
>> Calculating dependencies... done! |
36 |
>> [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" |
37 |
>> |
38 |
>> The following keyword changes are necessary to proceed: |
39 |
>> #required by app-office/libreoffice-3.3.4, required by @selected, required by @world (argument) |
40 |
>> >=app-text/poppler-0.18.0 ~amd64 |
41 |
>> |
42 |
>> NOTE: This --autounmask behavior can be disabled by setting |
43 |
>> EMERGE_DEFAULT_OPTS="--autounmask=n" in make.conf. |
44 |
>> |
45 |
>> Use --autounmask-write to write choanges to config files (honoring CONFIG_PROTECT). |
46 |
>> |
47 |
>> |
48 |
>> Is this just another of those cases, where I have to unmask an item |
49 |
>> and "dont mix 'em" ;) ??? |
50 |
>> |
51 |
>> Best regards, |
52 |
>> mcc |
53 |
>> |
54 |
>> |
55 |
>> |
56 |
>> |
57 |
>> |
58 |
>> |
59 |
>> |
60 |
> |
61 |
> Hi Mark, |
62 |
> |
63 |
> ok, I unmasked poppler, and it give me that again: |
64 |
> |
65 |
> |
66 |
> /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 ')' |
67 |
> 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 |
68 |
> 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 |
69 |
> g-ir-scanner: Poppler: warning: 5 warnings suppressed (use --warn-all to see them) |
70 |
> [ 79%] Built target gir-girs |
71 |
> Scanning dependencies of target gir-typelibs |
72 |
> [ 79%] Generating Poppler-0.18.typelib |
73 |
> /usr/bin/g-ir-compiler: error while loading shared libraries: libffi.so.4: cannot open shared object file: No such file or directory |
74 |
> make[2]: *** [glib/Poppler-0.18.typelib] Error 127 |
75 |
> make[1]: *** [glib/CMakeFiles/gir-typelibs.dir/all] Error 2 |
76 |
> make: *** [all] Error 2 |
77 |
> * ERROR: app-text/poppler-0.18.0 failed (compile phase): |
78 |
> * emake failed |
79 |
> * |
80 |
> * If you need support, post the output of 'emerge --info =app-text/poppler-0.18.0', |
81 |
> * the complete build log and the output of 'emerge -pqv =app-text/poppler-0.18.0'. |
82 |
> * The complete build log is located at '/var/tmp/portage/app-text/poppler-0.18.0/temp/build.log'. |
83 |
> * The ebuild environment file is located at '/var/tmp/portage/app-text/poppler-0.18.0/temp/environment'. |
84 |
> * S: '/var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0' |
85 |
> |
86 |
> >>> Failed to emerge app-text/poppler-0.18.0, Log file: |
87 |
> |
88 |
> >>> '/var/tmp/portage/app-text/poppler-0.18.0/temp/build.log' |
89 |
> |
90 |
> * Messages for package app-text/poppler-0.18.0: |
91 |
> |
92 |
> * ERROR: app-text/poppler-0.18.0 failed (compile phase): |
93 |
> * emake failed |
94 |
> * |
95 |
> * If you need support, post the output of 'emerge --info =app-text/poppler-0.18.0', |
96 |
> * the complete build log and the output of 'emerge -pqv =app-text/poppler-0.18.0'. |
97 |
> * The complete build log is located at '/var/tmp/portage/app-text/poppler-0.18.0/temp/build.log'. |
98 |
> * The ebuild environment file is located at '/var/tmp/portage/app-text/poppler-0.18.0/temp/environment'. |
99 |
> * S: '/var/tmp/portage/app-text/poppler-0.18.0/work/poppler-0.18.0' |
100 |
> |
101 |
> libffi remains the same as in the previous post of mine... |
102 |
> |
103 |
> Best regards, |
104 |
> mcc |
105 |
|
106 |
I'm not seeing any of that here. A couple of questions: |
107 |
|
108 |
1) What version of portage are you using? I'm at 2.2.0_alpha69. See my |
109 |
portage.keywords file from yesterday about how I unmask portage. For |
110 |
me it's a weird one... |
111 |
|
112 |
2) Do you have libffi installed? Maybe it's a case of the new poppler |
113 |
needs libffi but the ebuild isn't emerging it? |
114 |
|
115 |
c2stable ~ # eix -I libffi |
116 |
[I] dev-libs/libffi |
117 |
Available versions: 3.0.9-r2 3.0.10 **3.0.11_rc1 {debug static-libs test} |
118 |
Installed versions: 3.0.10(01:58:46 PM 10/17/2011)(-debug |
119 |
-static-libs -test) |
120 |
Homepage: http://sourceware.org/libffi/ |
121 |
Description: a portable, high level programming interface |
122 |
to various calling conventions. |
123 |
|
124 |
[I] virtual/libffi |
125 |
Available versions: 0 |
126 |
Installed versions: 0(10:42:58 AM 04/13/2010) |
127 |
Description: Virtual for dev-libs/libffi |
128 |
|
129 |
Found 2 matches. |
130 |
c2stable ~ # |
131 |
|
132 |
That sort of seems to be the case according to equery as poppler isn't |
133 |
shown below as depending on libffi. I possibly have it because I went |
134 |
the opposite on this recent -perl/-python news item and have them set. |
135 |
Just guessing about that though. |
136 |
|
137 |
c2stable ~ # equery depends libffi |
138 |
* These packages depend on libffi: |
139 |
dev-lang/python-2.7.1-r1 (virtual/libffi) |
140 |
dev-lang/python-3.1.3-r1 (virtual/libffi) |
141 |
dev-libs/gobject-introspection-0.10.8 (virtual/libffi) |
142 |
dev-python/pygobject-2.28.6 (libffi ? virtual/libffi) |
143 |
virtual/libffi-0 (dev-libs/libffi) |
144 |
c2stable ~ # |
145 |
|
146 |
So, if you don't have libffi installed then emerge it and try again |
147 |
with poppler after that. If poppler then emerges correctly then |
148 |
consider filing a bug report if you feel that's appropriate. |
149 |
|
150 |
Good luck. I won't be around much longer tonight. I'll catch up with |
151 |
you tomorrow. |
152 |
|
153 |
Cheers, |
154 |
Mark |