Linux Kernel Version and Perl Compilation

[Wiggins D'Anconia]

Currently I am looking at a new hosting provider and already hit one strike where the Perl version they had listed on their "Packages" page differed from that installed, aka they listed 5.6.1 and have 5.6.0 installed which really tinkers my toys, but I may be able to let that one slip. I know there were substantial improvements from 5.6.0 to 5.6.1 but I am not sure any of them will affect my code, any in particular I should be on the look out for?

Now to my actual question, and this may be more a Linux question than Perl, but I thought I would see what the gurus have to say, could I run into issues with a Perl compiled on one kernel version aka 2.2.16 and it running under a different, specifically 2.4.9 (smp) kernel, and what types of issues? Will I have problems compiling or running modules (XS in particular) that I build against this Perl under the newer kernel?

It is this kind of stuff that I get sick of dealing with hosting providers about....

[url]http://danconia.org[/url]

[John W. Krahn]

Wiggins D'Anconia wrote:

>
> Currently I am looking at a new hosting provider and already hit one
> strike where the Perl version they had listed on their "Packages" page
> differed from that installed, aka they listed 5.6.1 and have 5.6.0
> installed which really tinkers my toys, but I may be able to let that
> one slip. I know there were substantial improvements from 5.6.0 to
> 5.6.1 but I am not sure any of them will affect my code, any in
> particular I should be on the look out for?

The perldelta.pod file in 5.6.1 will tell you the differences between
5.6.1 and 5.6.0.


John
--
use Perl;
program
fulfillment

[Steve Grazzini]

On Fri, Sep 12, 2003 at 12:30:44PM -0500, Wiggins d'Anconia wrote:

> I know there were substantial improvements from 5.6.0 to 5.6.1 but I
> am not sure any of them will affect my code, any in particular I should
> be on the look out for?

It's perfectly usable, but 5.6.0 did end up with a reputation for
bugginess... Check the perldelta for 5.6.1 to get an idea of what
some of the problems were.

> could I run into issues with a Perl compiled on one kernel version aka
> 2.2.16 and it running under a different, specifically 2.4.9 (smp) kernel,
> and what types of issues?

A kernel upgrade won't (er, shouldn't) cause any problems. If you're
changing the whole system, though, then you may need to configure and
recompile perl and the XS modules with the new system's compiler and
libraries.

--
Steve

[David]

Wiggins D'Anconia wrote:

> Now to my actual question, and this may be more a Linux question than
> Perl, but I thought I would see what the gurus have to say, could I run
> into issues with a Perl compiled on one kernel version aka 2.2.16 and it
> running under a different, specifically 2.4.9 (smp) kernel, and what types
> of issues? Will I have problems compiling or running modules (XS in
> particular) that I build against this Perl under the newer kernel?

i think this has more to do with xsubpp than the kernel. XS is not C, it's a
glue / layer between Perl and C. even in C, your code is probably not
talking to the kernel directly unless of course, you are doing kernel
development. you are talking to the C libraries which, supposely, is going
to make your code portable across different platforms. xsubpp is reponsible
to translate your XS code to C which again makes XS a lot more portable on
top of C. consider that all the modules in CPAN is distributed to a wide
audience, i believe very few authors would have the time and resource to
test their code on all platforms and yet xsubpp and the C libraries provide
all the abstraction to figure out the differences between those platforms
so the programmer don't have to worry too much about it.

i am no gurus or expert on that kind of stuff as i am myself fairly new to
it and still learning. you might get a better a answer if you submit your
question to perl.xs

david
--
$_=q,015001450154015401570040016701570162015401440 041,,*,=*|=*_,split+local$";
map{~$_&1&&{$,<<=1,$#.=qq~\x63\x68\x72\x28@_[$_..$||3])=>~}}0..s~.~~g-1;*_=*#,

goto=>print+eval