Re^2: New optimizations in GCC 4.0 and Perl

Until you have the system and kernel compiling well, I would say that Perl and mod_perl should be considered of lesser importance.

I messed a bit with Linux From Scratch in the past, and I remained impressed by the fact that GCC 3.x hasn't ever been officially supported for kernel compilation. In LFS, in fact, they suggest installing a parallel GCC 2.95.3, which is officially supported by the kernel guys.

While I don't know if this still holds true currently (as I said, I did it some 4-5 months ago), I would certainly be VERY concerned to compile the base system with a brand newly-versioned compiler; I'd rather begin with less pervasive stuff such modules or Perl itself, reversing the path you suggest, using a compiler located in an ad-hoc, out-of-standard paths and probably installing this newly-compiled Perl itself into an isolated branch of the filesystem.

Just my 2c worth tip, anyway.

Update: corrected English syntax in one sentence, thanks blyman.

Flavio (perl -e 'print(scalar(reverse("\nti.xittelop\@oivalf")))')

Don't fool yourself.

Comment on Re^2: New optimizations in GCC 4.0 and Perl

Replies are listed 'Best First'.
Re^3: New optimizations in GCC 4.0 and Perl by samizdat (Vicar) on Apr 22, 2005 at 17:00 UTC
That's why I specified a 'mule' system, Flavio. For any system other than a raw throwaway, I agree heartily. My compatriot who has bee nworking his way up through the 3's on SPARC/Solaris is going to start working with it (4.0) and let me know. He will, of course, use your approach, because the systems he admins have too many $millions riding on them. :D	[reply]