l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
September 2: Social gathering
Next Installfest:
TBD
Latest News:
Aug. 18: Discounts to "Velocity" in NY; come to tonight's "Photography" talk
Page last updated:
2002 Mar 20 19:31

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
RE: [vox-tech] Need help with bad Perl
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [vox-tech] Need help with bad Perl



Hi Pete,

I read the Install for Perl and it had so many "options" that it left me
totally overwhelmed. That is why I thought it was not trivial at least
compared to installing an OS.  These days installing Linux (at least
Caldera) is a piece of cake. I just re-read the Perl Install file and I
guess I did not understand the instructions correctly and as in many other
occasions you are right.  I'll give it a try otherwise I'll get a copy of
Debian He He!

Thanks a lot Pete!

Alfredo

BTW #1 The 7.2 is for another machine that eventually will run the Database.
Right now I am just running tests on a discarded PC before I am allowed to
touch the "real" one.

BTW #2 my boss got a kick out of you answer ;-)

-----Original Message-----
From: Peter Jay Salzman [mailto:p@dirac.org] 
Sent: Wednesday, March 20, 2002 12:57 PM
To: vox-tech@lists.lugod.org
Subject: Re: [vox-tech] Need help with bad Perl


begin ALLO (Alfredo Lopez) <ald@novozymesbiotech.com> 
> 
> I found out that according to one of the Bioinformatics wizards at 
> Cold Spring Harbor the problem is Perl:
> 
> "This problem has been reported under some versions of SuSE and RedHat 
> Linux (it appears to be related to a particular RPM distribution of 
> Perl).  Perl was built incorrectly, causing some but not all loadable 
> modules to fail. The only solution I know of is to rebuild Perl 
> correctly from scratch and reinstall all previously-installed 
> modules."
 
their explanation doesn't say much, but it DOES say that the problem ain't
perl.  the problem is with suse and redhat's package of perl.

> Has anybody experienced this?  Is there a way to get around this other 
> than building Perl.  I don't know but for an inexperienced user like 
> me, rebuilding Perl is not a trivial exercise.

and how do you know this...experience?

how do you know that building perl isn't as easy as:

tar jxvf perl.tar.bz2
cd perl
./configure
make
make install


> BTY I am using the latest
> version of Caldera (Workstation 3.1) and I am getting next Friday a 
> copy of RedHat 7.2. But I am almost sure 7.2 will have the same 
> problem.

something is terribly wrong here.  you're not willing to install perl from
source code, but you ARE willing to install a new operating system.

do you see the irony here?  :-)

pete

ps- if you still think installing an operating system is easier than
installing perl from source, i think your best recourse is to install
debian. _______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.