perl and modules

[Tulan W. Hu]

Do I need to rebuild all the perl modules after I
upgrade my perl to a newer version?

Thanks for answering my question in advance.

[Iain Truskett]

* Tulan W. Hu <twhu@lucent.com>:

> Do I need to rebuild all the perl modules after I
> upgrade my perl to a newer version?

It's usually best to. In most cases it's necessary.
It should be immediately obvious when you try to
use any of said modules.


cheers,
--
Iain. <http://eh.org/~koschei/>

[Eric J. Roode]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Tulan W. Hu" <twhu@lucent.com> wrote in news:bljqrq
$8va@netnews.proxy.lucent.com:

> Do I need to rebuild all the perl modules after I
> upgrade my perl to a newer version?
>
> Thanks for answering my question in advance.

Sorry I couldn't answer it in advance. ;-)

Usually, you need to rebuild any binary modules (ie, modules that need to
be compiled with a C compiler), because most Perl releases aren't binary-
compatible with previous versions. (I hear, however, that 5.8.1 is b-c
with 5.8.0).

For pure-perl modules, there is an option during the configure phase where
you can tell the build process to retain directories from earlier perl
versions in the new version's @INC, so those modules don't necessarily need
to be reinstalled.

- --
Eric
$_ = reverse sort $ /. r , qw p ekca lre uJ reh
ts p , map $ _. $ " , qw e p h tona e and print

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBP311amPeouIeTNHoEQLhVQCgkXSGiU2a+4PgFXxwW52uUV sOENcAoJ5Q
5M+yuqpLqPlPnmdqJgSQpwiE
=h4e+
-----END PGP SIGNATURE-----

[Tulan W. Hu]

"Eric J. Roode" <REMOVEsdnCAPS@comcast.net> >

> > Do I need to rebuild all the perl modules after I
> > upgrade my perl to a newer version?
> >
> > Thanks for answering my question in advance.

>
> Sorry I couldn't answer it in advance. ;-)
>
> Usually, you need to rebuild any binary modules (ie, modules that need to
> be compiled with a C compiler), because most Perl releases aren't binary-
> compatible with previous versions. (I hear, however, that 5.8.1 is b-c
> with 5.8.0).
>
> For pure-perl modules, there is an option during the configure phase where
> you can tell the build process to retain directories from earlier perl
> versions in the new version's @INC, so those modules don't necessarily

need

> to be reinstalled.

I understand that if I upgrade perl from 5.6 to 5.8, then I need to rebuild
the
modules and put them to the new @INC. I have built the modules for the
perl 5.8.1-rc4, and now I'm having the released 5.8.1. Do I still need to
rebuild the modules?
I thought that even the binary modules should be ok because I'm using the
same version of gcc and all library locations are the same too. The command
"perl Makefile.PL" just create the Makefile for me with correct the build
flags. I have tried a couple of modules, but it does not seem the rebuild
process makes any difference.

[Walt Mankowski]

In article <bljv0l$aeb@netnews.proxy.lucent.com>, Tulan W. Hu wrote:

> I understand that if I upgrade perl from 5.6 to 5.8, then I need to rebuild
> the
> modules and put them to the new @INC. I have built the modules for the
> perl 5.8.1-rc4, and now I'm having the released 5.8.1. Do I still need to
> rebuild the modules?
> I thought that even the binary modules should be ok because I'm using the
> same version of gcc and all library locations are the same too. The command
> "perl Makefile.PL" just create the Makefile for me with correct the build
> flags. I have tried a couple of modules, but it does not seem the rebuild
> process makes any difference.

5.8.0 and 5.8.1 are binary-compatible with each other, so if that was
your upgrade path you'd be fine. Since they didn't change anything
in 5.8.1, it's highly unlikely there'd be anything different in one of
the release candidates.

I'd recommend not rebuilding them by default and running some tests with
the official 5.8.1 and the modules you built with rc4. If everything's
fine, then you don't need to rebuild them.

Walt