Error compiling Perl-5.8.0

Rocker · Posted: Thu Dec 12, 2002 6:30 pm Post subject: Error compiling Perl-5.8.0

Hi,

everything went fine, till now. I'm in stage 2 and Gentoo is busy with compiling Perl. After about 3/4 till 1 hour (on a PIII-450) it stops with the following error:

doug-x07 · Posted: Thu Dec 12, 2002 7:31 pm Post subject:

Were you deliberately trying to install Perl-5.8.0 ? It should normally still be masked in the portage tree, see this thread . If you really want to install this version, it compiled for me by using less aggressive CFLAGS than ususal, unmerging all perl modules then emerging them again. You may find it wiser just to install perl-5.6.1-r7 instead unless you must absolutely have 5.8.0
_________________
#! /usr/bin/perl
if( @first != $succeed ) {
post { $question->forum && eval '$answers' };
try { $again } catch { $problem && $resolve };
bless $posters; }

Rocker · Posted: Thu Dec 12, 2002 10:50 pm Post subject:

It was asking for this package by himself, and started to download it. I don't now why it doesn't use version 5.6 if that's the normal way.

And how do I unemerge the other perl modules (how can i see which one I have?) and emerge them again? In case that's tho only option?

Or is there a method to skip the perl 5.8 modules in the emerge system?

BTW. I have taken a look, but is hasn't downloaded version 5.6xx, so I guess that it wasn't in the portage tree

Rocker · Posted: Thu Dec 12, 2002 10:54 pm Post subject:

I've copied the output (only the first few lines) from my 'emerge -p system', as you can see, it asked for version 5.8 by himself

These are the packages that I would merge, in order.

Calculating system dependencies ...done!
[ebuild N ] dev-python/python-fchksum-1.6.1
[ebuild N ] sys-devel/m4-1.4p
[ebuild N ] sys-apps/groff-1.17.2-r3
[ebuild N ] sys-libs/db-1.85-r1
[ebuild N ] sys-libs/db-3.2.9-r1
[ebuild N ] sys-libs/gdbm-1.8.0-r5
[ebuild N ] sys-devel/perl-5.8.0-r2
--- snip ---

Could it have something to do with an USE='perl' option in make.conf?

rac · Posted: Thu Dec 12, 2002 10:55 pm Post subject:

Do you have an ACCEPT_KEYWORDS line in make.conf?
_________________
For every higher wall, there is a taller ladder

Rocker · Posted: Thu Dec 12, 2002 11:04 pm Post subject:

No, what will this variable do?

Oh... and I have taken a closer look to my USE variable, and there is no keyword perl in it, but it is in the standard USE. So I guess that this shouldn't make a difference

rac · Posted: Thu Dec 12, 2002 11:08 pm Post subject:

Rocker · Posted: Thu Dec 12, 2002 11:14 pm Post subject:

_SkeLeToN_ · Posted: Thu Dec 12, 2002 11:19 pm Post subject:

i got the exact same behavior .... I emerge sync 2-3 times and emerge want to update perl to 5.8.x so I went on and emerge it. My system was already up and runnning and the next day emerge want to go back to 5.6 ... I didnt have the accept keyword I double check to make sure.

I had to re-emerge vim and gaim because of the new perl package ... but now I do not have any problem...

Since you are trying to install gentoo maybe 5.8 will fails but that I don't know.

rac · Posted: Thu Dec 12, 2002 11:20 pm Post subject:

Then this is extremely bizarre. Is this a fresh install, or an upgrade? Which stage did you start with? What does "emerge -V" say?

EDIT: If you read French (or even if you don't, as some of the interesting parts are in English), you might also be interested in pb installation perl 5.8.0-r2.
_________________
For every higher wall, there is a taller ladder

Rocker · Posted: Thu Dec 12, 2002 11:34 pm Post subject:

It's a fresh install, I started with it yesterday. I have done the first emerge sync yesterday evening, so about 30 hours ago.

I started to install from an existing system (LFS), so I don't have the life cd. I wanted to compile everything on my own machine, so started at stage 1.

I have done a new emerge sync 15 minutes ago (is it possible to do this again, or does this break any dependencies or whatever? I don't know because it's my first Gentoo install), and am now going to bootstrap again, but with CFLAGS set to -O2 instead of -O3.

After this emerge sync I looked at the dependencies of portage with a emerge -p portage, and it needed perl version 5.8.0

This is the output from an emerge -V

rac · Posted: Thu Dec 12, 2002 11:36 pm Post subject:

Rocker · Posted: Thu Dec 12, 2002 11:41 pm Post subject:

Rocker · Posted: Fri Dec 13, 2002 12:10 am Post subject:

Is it better to do an 'emerge rsync' instead of an 'emerge sync'? If I understand it well, this will clean up the /usr/portage dir first? So maybe this will give another result?

Just brainstorming... :wink:

rac · Posted: Fri Dec 13, 2002 12:24 am Post subject:

Rocker · Posted: Fri Dec 13, 2002 3:40 pm Post subject:

I've done a new emerge rsync this morning. This time it came with perl version 5.6.1. At this moment it's busy with it's emerge system, and has already passed the perl module, so the problem is fixed!

Timm · Posted: Fri Dec 13, 2002 7:07 pm Post subject:

A few days ago portage also told me to update to 5.8.0-r2. Today it told me to downgrade to 5.6.1-r9. Funny.

Oh yes, I don't use experimental/testing packages, which means that ACCEPT_KEYWORDS is commented out in /etc/make.conf

Curious · Posted: Fri Dec 13, 2002 9:24 pm Post subject:

The juggling might have been in response to this. I believe the fix was first established for 5.8, and then backported to earlier Perls.

-- Curious
Perl Hater.
_________________
Are you down with the Hawk?

doug-x07 · Posted: Fri Dec 13, 2002 10:35 pm Post subject:

Humm I maybe completely wrong about this as I'm not aware of how the developpers managing masking and unmasking packages in cvs. I just had a look through cvs and the perl-5.8.0-r2.ebuild was masked on 11th december. Before that it was unmasked for x86. I take it in that case emerge would have found it as the latest unmasked version if it was in the portage tree. Possible explanation?

I don't think the safe module bug is the origin of the changes, all that seems to have been done recently on perl-5.8.0 is lc support and reverting to make rather than emake. I checked the module on cpan and the bug fix has been in place since 5th October. Seeing as it is one of the base perl packages I don't think it impacts the actual ebuilds asthey just download the current official version from cpan. Maybe if you installed perl before then it might be an idea emerging again to have the security fix. Please correct me if any of my assumptions are wrong on the subject.
_________________
#! /usr/bin/perl
if( @first != $succeed ) {
post { $question->forum && eval '$answers' };
try { $again } catch { $problem && $resolve };
bless $posters; }