Erich schrieb:
> Tomasz Kondziola schrieb:
>> Hello all,
>> Today I've experienced  problem with gworkspace compilation.
>> I've used following entries from my portage.keyword:
>> # GNUStep
>> gnustep-libs/pdfkit                                 ~amd64
>> =gnustep-apps/gworkspace- 0.8.2          ~*
>>
>> During compilation process I received following message:
>>
>> [snip]
>> /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/../../../../x86_64-pc-linux-gnu/bin/ld:
>> cannot find -lPDFKit
>> collect2: ld returned 1 exit status
>> make[4]: *** [PdfViewer.inspector/./PdfViewer] Error 1
>> make[3]: *** [PdfViewer.all.bundle.variables] Error 2
>> make[3]: Leaving directory `/var/tmp/portage/gnustep-apps/gworkspace-
>> 0.8.2/work/GWorkspace-0.8.2/Inspector/ContentViewers/PdfViewer'
>> make[2]: *** [internal-all] Error 2
>> make[2]: Leaving directory
>> `/var/tmp/portage/gnustep-apps/gworkspace-0.8.2/work/GWorkspace-0.8.2/Inspector/ContentViewers'
>>
>> make[1]: *** [internal-all] Error 2
>> make[1]: Leaving directory
>> `/var/tmp/portage/gnustep-apps/gworkspace-0.8.2/work/GWorkspace-0.8.2/Inspector'
>> make: *** [internal-all] Error 2
>>
>> I've installed pdfkit earlier of course so I don't understand why
>> message about problems with PDFKit linking appeared.
> 
> Strange, to me it seems that PDFKit is not really needed by Gworkspace.
> Today I emerged gworkspace-0.8.3 and it did not pull in PDFKit. It
> emerged without any glitches during compilation. The only difference I
> can spot is that I do not have PDFKit installed (although it is in my
> package.keywords).
I must have been sleeping... ;-)

FYI: Just added pdfkit to the USE flags and emerged gworkspace-0.8.3
again. PDFKit and Gworkspace both emerged flawlessly.

Regards,
Erich
-- 
gentoo-gnustep@g.o mailing list