| 1 |
On Fri, Jul 31, 2009 at 9:51 PM, ABCD<en.ABCD@×××××.com> wrote: |
| 2 |
> Kevin O'Gorman wrote: |
| 3 |
> |
| 4 |
>> I've got portage's dev-perl/XML-Parser-2.36, but nevertheless several |
| 5 |
>> packages have started to fail during emerge for lack of Perl's |
| 6 |
>> XML::Parser. |
| 7 |
>> Even the simple script fails to run under perl: |
| 8 |
>>> #!/usr/bin/perl -w |
| 9 |
>>> |
| 10 |
>>> use XML::Parser; |
| 11 |
>>> |
| 12 |
>>> print "yes\n"; |
| 13 |
>> |
| 14 |
>> Do I have to get it from CPAN? |
| 15 |
>> |
| 16 |
>> Consider libgksu; here's the end of the emerge output, where |
| 17 |
>> XML::Parser is required by intltool: |
| 18 |
>> |
| 19 |
>> checking for perl... /usr/bin/perl |
| 20 |
>> checking for XML::Parser... configure: error: XML::Parser perl module |
| 21 |
>> is required for intltool |
| 22 |
>> |
| 23 |
>> !!! Please attach the following file when seeking support: |
| 24 |
>> !!! /var/tmp/portage/x11-libs/libgksu-2.0.9/work/libgksu-2.0.9/config.log |
| 25 |
>> * |
| 26 |
>> * ERROR: x11-libs/libgksu-2.0.9 failed. |
| 27 |
>> * Call stack: |
| 28 |
>> * ebuild.sh, line 49: Called src_compile |
| 29 |
>> * environment, line 2896: Called gnome2_src_compile |
| 30 |
>> * environment, line 2264: Called gnome2_src_configure |
| 31 |
>> * environment, line 2278: Called econf '--enable-nls' |
| 32 |
>> '--disable-gtk-doc' |
| 33 |
>> * ebuild.sh, line 534: Called die |
| 34 |
>> * The specific snippet of code: |
| 35 |
>> * die "econf failed" |
| 36 |
>> * The die message: |
| 37 |
>> * econf failed |
| 38 |
>> * |
| 39 |
>> * If you need support, post the topmost build error, and the call |
| 40 |
>> stack if relevant. |
| 41 |
>> * A complete build log is located at |
| 42 |
>> '/var/tmp/portage/x11-libs/libgksu-2.0.9/temp/build.log'. |
| 43 |
>> * The ebuild environment file is located at |
| 44 |
>> '/var/tmp/portage/x11-libs/libgksu-2.0.9/temp/environment'. |
| 45 |
>> * |
| 46 |
>> |
| 47 |
>>>>> Failed to emerge x11-libs/libgksu-2.0.9, Log file: |
| 48 |
>> |
| 49 |
>>>>> '/var/tmp/portage/x11-libs/libgksu-2.0.9/temp/build.log' |
| 50 |
>> |
| 51 |
> |
| 52 |
> Have you recently changed the "ithreads" USE flag on dev-lang/perl? If so, |
| 53 |
> then you will need to remerge all ebuilds that installed files in |
| 54 |
> /usr/lib*/perl5/vendor_perl/${PERL_VER}/${CHOST%%-*}-linux if "ithreads" was |
| 55 |
> disabled, and /usr/lib*/perl5/vendor_perl/${PERL_VER}/${CHOST%%-*}-linux- |
| 56 |
> thread-multi if "ithreads" was enabled. |
| 57 |
> |
| 58 |
> Also, if you have recently upgraded perl, the same provisions apply. |
| 59 |
> |
| 60 |
> NOTE: In the above expansion, the following applies [sorry if you already |
| 61 |
> know this]: |
| 62 |
> |
| 63 |
> - "lib*" is lib on x86, lib64 on amd64 |
| 64 |
> - ${PERL_VER} is your perl version, probably 5.8.8 |
| 65 |
> - ${CHOST%%-*} is the part of the CHOST before the first "-": |
| 66 |
> * on x86, it will be one of i486, i586, or i686 |
| 67 |
> * on amd64, it will be x86_64 |
| 68 |
> |
| 69 |
> If you aren't on x86 or amd64, I assume you can figure it out :). |
| 70 |
|
| 71 |
This is helpful, as I do remember fooling with ithreads and not |
| 72 |
getting it completely right. I'm now emerging anything that has |
| 73 |
'perl' in the name or category. |
| 74 |
|
| 75 |
It has always baffled me, given this sensitivity, that all such |
| 76 |
packages don't just declare that they use the 'ithreads' USE flag, |
| 77 |
even if they don't explicitly. Then my usual emerge --newuse would do |
| 78 |
the Right Thing (TM). |
| 79 |
|
| 80 |
++ kevin |
| 81 |
|
| 82 |
-- |
| 83 |
Kevin O'Gorman, PhD |
Archives