[19079] in Perl-Users-Digest
Perl-Users Digest, Issue: 1274 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Jul 11 03:22:11 2001
Date: Wed, 11 Jul 2001 00:21:33 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Message-Id: <994836093-v10-i1274@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Wed, 11 Jul 2001 Volume: 10 Number: 1274
Today's topics:
Re: environment variable in cgi (hao tran)
Re: environment variable in cgi <gnarinn@hotmail.com>
Re: environment variable in cgi (hao tran)
Re: environment variable in cgi <tony_curtis32@yahoo.com>
Re: environment variable in cgi <gnarinn@hotmail.com>
Re: environment variable in cgi (hao tran)
FAQ from Stupid Beginner about Perl!!! <gsmr@hotmail.com>
Re: FAQ from Stupid Beginner about Perl!!! (Smiley)
Re: FAQ from Stupid Beginner about Perl!!! nobull@mail.com
Re: FAQ from Stupid Beginner about Perl!!! <wyzelli@yahoo.com>
Re: FAQ from Stupid Beginner about Perl!!! (Smiley)
Re: FAQ from Stupid Beginner about Perl!!! <wyzelli@yahoo.com>
FAQ: How can I convince my sysadmin/supervisor/employee <faq@denver.pm.org>
FAQ: How can I get a binary version of Perl? <faq@denver.pm.org>
FAQ: I copied the Perl binary from one machine to anoth <faq@denver.pm.org>
FAQ: I don't have a C compiler on my system. How can I <faq@denver.pm.org>
FAQ: I grabbed the sources and tried to compile but gdb <faq@denver.pm.org>
FAQ: What machines support Perl? Where do I get it? <faq@denver.pm.org>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 9 Jul 2001 18:32:24 -0700
From: hao7@yahoo.com (hao tran)
Subject: Re: environment variable in cgi
Message-Id: <3913d5b4.0107091732.39053b3c@posting.google.com>
Hi all,
thank you for your help the script you gave me work. but I still
could not get what i want.
I add to the code you give me: print "$ENV{HOME}<br>\n"; but I don't
see anything on the web. when i run the script by command: perl
myscript.cgi, I saw it printed out but somehow it is not displayed on
the web.
thanks.
see-sig@from.invalid (David Efflandt) wrote in message news:<slrn9kh4u8.lh7.see-sig@typhoon.xnet.com>...
> On 6 Jul 2001 12:07:22 -0700, hao tran <hao7@yahoo.com> wrote:
> > Hi all,
> > I try to get the simple enviroment variable by $HOME = $ENV{HOME};
> > but the problem is it is not displayed on the browser like netscape.
> > (using print "Content-type:text/html\n\n")
>
> That variable likely does not exist in CGI unless you set it. See the
> docs for your webserver. Following is a quick and dirty little env.cgi I
> use to list the %ENV hash, but note that some variables you see may be
> optional or browser specific:
>
> #!/usr/bin/perl -w
> print "Content-type: text/plain\n\n";
> foreach (sort keys %ENV) { print "$_: $ENV{$_}\n"; }
> # following optional to tell what user is running your CGI on Unix:
> print "\nScript is running as ",`whoami`,"\n";
------------------------------
Date: Tue, 10 Jul 2001 09:47:02 +0000
From: gnari <gnarinn@hotmail.com>
Subject: Re: environment variable in cgi
Message-Id: <994758422.324156385380775.gnarinn@hotmail.com>
(please do not top-post)
In article <3913d5b4.0107091732.39053b3c@posting.google.com>,
hao tran <hao7@yahoo.com> wrote:
>I add to the code you give me: print "$ENV{HOME}<br>\n"; but I don't
>see anything on the web. when i run the script by command: perl
>myscript.cgi, I saw it printed out but somehow it is not displayed on
>the web.
Then it should be obvious it is not defined, isn't it?
What would you expect it to be, anyways?
When debugging like this, it is helpful to add a bit more output to make
it clearer. for example you could have used:
print "HOME=[$ENV{HOME}]<br>\n";
Then you would have seen:
HOME=[]
Making it obvious that the debug print was executed. Also, the
brackets make hidden things like spaces or newlines more visible.
Escaping the string can also be a good idea if the debug goes to
html.
gnari
------------------------------
Date: 10 Jul 2001 10:28:24 -0700
From: hao7@yahoo.com (hao tran)
Subject: Re: environment variable in cgi
Message-Id: <3913d5b4.0107100928.521bcd77@posting.google.com>
Sorry for not making it so clear. I can see the HOME variable defined
to my home directory not the undefined value printed out. somehow it
is not displayed on the web. I am thinking that there might be
problems with the browser getting the value but not in the script
itself. Thanks again.
gnari <gnarinn@hotmail.com> wrote in message news:<994758422.324156385380775.gnarinn@hotmail.com>...
> (please do not top-post)
>
> In article <3913d5b4.0107091732.39053b3c@posting.google.com>,
> hao tran <hao7@yahoo.com> wrote:
>
> >I add to the code you give me: print "$ENV{HOME}<br>\n"; but I don't
> >see anything on the web. when i run the script by command: perl
> >myscript.cgi, I saw it printed out but somehow it is not displayed on
> >the web.
>
> Then it should be obvious it is not defined, isn't it?
> What would you expect it to be, anyways?
>
> When debugging like this, it is helpful to add a bit more output to make
> it clearer. for example you could have used:
> print "HOME=[$ENV{HOME}]<br>\n";
>
> Then you would have seen:
> HOME=[]
>
> Making it obvious that the debug print was executed. Also, the
> brackets make hidden things like spaces or newlines more visible.
> Escaping the string can also be a good idea if the debug goes to
> html.
>
> gnari
------------------------------
Date: 10 Jul 2001 14:03:42 -0500
From: Tony Curtis <tony_curtis32@yahoo.com>
Subject: Re: environment variable in cgi
Message-Id: <87hewkfvxt.fsf@limey.hpcc.uh.edu>
[ PLEASE do not top-post ]
>> On 10 Jul 2001 10:28:24 -0700,
>> hao7@yahoo.com (hao tran) said:
> gnari <gnarinn@hotmail.com> wrote in message
> news:<994758422.324156385380775.gnarinn@hotmail.com>...
>> (please do not top-post)
>>
>> In article
>> <3913d5b4.0107091732.39053b3c@posting.google.com>,
>> hao tran <hao7@yahoo.com> wrote:
>>
>> >I add to the code you give me: print
>> "$ENV{HOME}<br>\n"; but I don't >see anything on the
>> web. when i run the script by command: perl
>> >myscript.cgi, I saw it printed out but somehow it is
>> not displayed on >the web.
>>
>> Then it should be obvious it is not defined, isn't it?
>> What would you expect it to be, anyways?
>>
>> When debugging like this, it is helpful to add a bit
>> more output to make it clearer. for example you could
>> have used: print "HOME=[$ENV{HOME}]<br>\n";
>>
>> Then you would have seen: HOME=[]
>>
>> Making it obvious that the debug print was
>> executed. Also, the brackets make hidden things like
>> spaces or newlines more visible. Escaping the string
>> can also be a good idea if the debug goes to html.
>>
>> gnari
> Sorry for not making it so clear. I can see the HOME
> variable defined to my home directory not the undefined
> value printed out. somehow it is not displayed on the
> web. I am thinking that there might be problems with
> the browser getting the value but not in the script
> itself. Thanks again.
The answer is contained within the above. HOME is not
defined in the environment inherited by CGI programs.
hth
t
--
Beep beep! Out of my way, I'm a motorist!
------------------------------
Date: Tue, 10 Jul 2001 19:12:19 +0000
From: gnari <gnarinn@hotmail.com>
Subject: Re: environment variable in cgi
Message-Id: <994792339.0208406420424581.gnarinn@hotmail.com>
(
please do not top-post.
by top-posting, i mean putting your answer at the top of the article,
and then quoting the whole of the article you are answering to after that.
now i will have to rearrange the article to be able to answer,
and usually that puts me off enough so that I do not bother
)
In article <3913d5b4.0107100928.521bcd77@posting.google.com>,
hao tran <hao7@yahoo.com> wrote: (rearranged and trimmed)
>gnari <gnarinn@hotmail.com> wrote in message news:<994758422.324156385380775.gnarinn@hotmail.com>...
>> In article <3913d5b4.0107091732.39053b3c@posting.google.com>,
>> hao tran <hao7@yahoo.com> wrote:
>>
>> >I add to the code you give me: print "$ENV{HOME}<br>\n"; but I don't
>> >see anything on the web. when i run the script by command: perl
>> >myscript.cgi, I saw it printed out but somehow it is not displayed on
>> >the web.
>>
>> Then it should be obvious it is not defined, isn't it?
>> What would you expect it to be, anyways?
>>
>Sorry for not making it so clear. I can see the HOME variable defined
>to my home directory not the undefined value printed out. somehow it
>is not displayed on the web. I am thinking that there might be
>problems with the browser getting the value but not in the script
>itself. Thanks again.
no, you do not understand. HOME is not defined whithin a CGI script.
I asked what do you expect it to be:
$HOME of the user that the web server is running as? this is typically
the user 'nobody' that does not have a home directory
should it be the $HOME of the owner of the cgi script?
should it be roots $HOME?
should it be the $HOME of the user of the web page? this of course is
impossible as he is not necessarily a user, and even if he is, which one?
should it be the DocumentRoot directory?
or the cgi-bin directory, assuming there is such a thing?
I think the real question to ask here is WHY do you want to
use $HOME in a cgi script?
gnari
k
------------------------------
Date: 10 Jul 2001 19:00:03 -0700
From: hao7@yahoo.com (hao tran)
Subject: Re: environment variable in cgi
Message-Id: <3913d5b4.0107101800.7ddcb864@posting.google.com>
Hi,
ok forget about HOME. suppose I have an environment variable that I
defined set MYNAME = hao7. I display it by echo $MYNAME and get hao7.
in the script i have: print "$ENV{MYNAME}\n"; I run the script and
get hao7 printed out. but to call this script from the browser, like
netscape, the environment variable not displayed. Thanks.
gnari <gnarinn@hotmail.com> wrote in message news:<994792339.0208406420424581.gnarinn@hotmail.com>...
> (
> please do not top-post.
> by top-posting, i mean putting your answer at the top of the article,
> and then quoting the whole of the article you are answering to after that.
>
> now i will have to rearrange the article to be able to answer,
> and usually that puts me off enough so that I do not bother
> )
>
>
> In article <3913d5b4.0107100928.521bcd77@posting.google.com>,
> hao tran <hao7@yahoo.com> wrote: (rearranged and trimmed)
>
> >gnari <gnarinn@hotmail.com> wrote in message news:<994758422.324156385380775.gnarinn@hotmail.com>...
> >> In article <3913d5b4.0107091732.39053b3c@posting.google.com>,
> >> hao tran <hao7@yahoo.com> wrote:
> >>
> >> >I add to the code you give me: print "$ENV{HOME}<br>\n"; but I don't
> >> >see anything on the web. when i run the script by command: perl
> >> >myscript.cgi, I saw it printed out but somehow it is not displayed on
> >> >the web.
> >>
> >> Then it should be obvious it is not defined, isn't it?
> >> What would you expect it to be, anyways?
> >>
> >Sorry for not making it so clear. I can see the HOME variable defined
> >to my home directory not the undefined value printed out. somehow it
> >is not displayed on the web. I am thinking that there might be
> >problems with the browser getting the value but not in the script
> >itself. Thanks again.
>
> no, you do not understand. HOME is not defined whithin a CGI script.
> I asked what do you expect it to be:
>
> $HOME of the user that the web server is running as? this is typically
> the user 'nobody' that does not have a home directory
>
> should it be the $HOME of the owner of the cgi script?
>
> should it be roots $HOME?
>
> should it be the $HOME of the user of the web page? this of course is
> impossible as he is not necessarily a user, and even if he is, which one?
>
> should it be the DocumentRoot directory?
> or the cgi-bin directory, assuming there is such a thing?
>
>
> I think the real question to ask here is WHY do you want to
> use $HOME in a cgi script?
>
> gnari
> k
------------------------------
Date: Mon, 9 Jul 2001 18:29:46 +0300
From: "Cindy" <gsmr@hotmail.com>
Subject: FAQ from Stupid Beginner about Perl!!!
Message-Id: <3b49ccfa$1@newsflash.abo.fi>
Typical Problem:
My CGI script runs from the command line but not the browser. (500 Server
Error)
Server Soft: vWebServer 1.2
Perl: ActivePerl 5.6.1
OS: Win98SE
Many many thanks,
------------------------------
Date: Mon, 09 Jul 2001 19:00:34 GMT
From: gurm@intrasof.com (Smiley)
Subject: Re: FAQ from Stupid Beginner about Perl!!!
Message-Id: <3b49fd8f.147758535@news1.on.sympatico.ca>
Cindy, Cindy, Cindy,
Look in the first few pages of any book teaching Perl CGI and you'll
probably find the answer - what have you been using to learn from
anyway?
Well, no matter. The answer's extremely simple. Before you can
output text to the browser you need to first set the header to tell
the browser what it's looking at. Just put the following line near
the beginning of your application and you'll be fine :
print "Content-type: text/html\n\n";
BTW - as a warning, some people can get really snotty when people ask
such a basic question without doing their homework first. I'm not one
of them, but all the same I'd suggest that you try consulting your
manual or a good online tutorial first before deciding that you need
help.
Hope that helps :)
On Mon, 9 Jul 2001 18:29:46 +0300, "Cindy" <gsmr@hotmail.com> wrote:
>Typical Problem:
>
>My CGI script runs from the command line but not the browser. (500 Server
>Error)
>
>Server Soft: vWebServer 1.2
>Perl: ActivePerl 5.6.1
>OS: Win98SE
>
>Many many thanks,
>
>
>
------------------------------
Date: 09 Jul 2001 18:01:27 +0100
From: nobull@mail.com
Subject: Re: FAQ from Stupid Beginner about Perl!!!
Message-Id: <u9hewm9guw.fsf@wcl-l.bham.ac.uk>
"Cindy" <gsmr@hotmail.com> trolls:
> My CGI script runs from the command line but not the browser. (500 Server
> Error)
Er.... see FAQ: "My CGI script runs from the command line but not the
browser. (500 Server Error)"
Hint: The FAQ is a list of frequently asked questions _with_
_answers_.
--
\\ ( )
. _\\__[oo
.__/ \\ /\@
. l___\\
# ll l\\
###LL LL\\
------------------------------
Date: Tue, 10 Jul 2001 09:23:50 +0930
From: "Wyzelli" <wyzelli@yahoo.com>
Subject: Re: FAQ from Stupid Beginner about Perl!!!
Message-Id: <3pr27.13$xO3.542@vic.nntp.telstra.net>
"Smiley" <gurm@intrasof.com> wrote in message
news:3b49fd8f.147758535@news1.on.sympatico.ca...
> Cindy, Cindy, Cindy,
>
> BTW - as a warning, some people can get really snotty when people ask
> such a basic question without doing their homework first. I'm not one
> of them, (snip)
YET...
:)
Wyzelli
--
($a,$b,$w,$t)=(' bottle',' of beer',' on the wall','Take one down, pass it
around');
$d='$_$a$s$b$w';$e='$_$a$s$b';sub d{$h=shift;$h=~s/\$(\w+)/${$1}/g;return$h}
sub
e{return(shift!=1)?'s':''}for(reverse(1..100)){$s=e($_);$f=d($d);$g=d($e);
$c.="$f\n$g\n$t\n";$_--;$s=e($_);$e=d($d);$c.="$e\n\n";}print"$c*hic*";
------------------------------
Date: Wed, 11 Jul 2001 08:13:08 GMT
From: gurm@intrasof.com (Smiley)
Subject: Re: FAQ from Stupid Beginner about Perl!!!
Message-Id: <3b4aaace.192109308@news1.on.sympatico.ca>
>> BTW - as a warning, some people can get really snotty when people ask
>> such a basic question without doing their homework first. I'm not one
>> of them, (snip)
>
>YET...
>
>:)
>
Hehe, so you think the stress of handling stupid questions from
beginner users is going to get to me eh?
I highly doubt it, I've tutored my less-programming-minded classmates
all throughout my school days. I just don't take this kind of thing
that seriously that I find the need to lash out about it.
I've known classmates though who were great programmers but extremely
snotty when they tried to teach concepts to people who didn't know as
much as them. Kind of like that dorky Nick Burns character on SNL -
though I don't think I've known anybody who was anywhere near that
bad.
Maybe you're right though. Trolling the newsgroups for no-nothing
newbies to put down sounds like a way to waste an afternoon if I have
nothing better to do ;)
------------------------------
Date: Wed, 11 Jul 2001 15:06:38 +0930
From: "Wyzelli" <wyzelli@yahoo.com>
Subject: Re: FAQ from Stupid Beginner about Perl!!!
Message-Id: <9wR27.25$BZ3.1688@vic.nntp.telstra.net>
"Smiley" <gurm@intrasof.com> wrote in message
news:3b4aaace.192109308@news1.on.sympatico.ca...
> >> BTW - as a warning, some people can get really snotty when people ask
> >> such a basic question without doing their homework first. I'm not one
> >> of them, (snip)
> >
> >YET...
> >
> >:)
> >
> Hehe, so you think the stress of handling stupid questions from
> beginner users is going to get to me eh?
>
> I highly doubt it, I've tutored my less-programming-minded classmates
> all throughout my school days. I just don't take this kind of thing
> that seriously that I find the need to lash out about it.
>
> I've known classmates though who were great programmers but extremely
> snotty when they tried to teach concepts to people who didn't know as
> much as them. Kind of like that dorky Nick Burns character on SNL -
> though I don't think I've known anybody who was anywhere near that
> bad.
>
> Maybe you're right though. Trolling the newsgroups for no-nothing
> newbies to put down sounds like a way to waste an afternoon if I have
> nothing better to do ;)
I have found that it is just easier to simply ignore the really silly
questions rather than flame them, but there are ones that are so damn
stupid, and so damn repetitive, that the urge to kill gets stronger and
stronger.
I guess most of us like helping others, and also the challenge of solving
other people's problems, but after a while (3 years in my case so far in
c.l.p.m, others far longer) the effort of weeding through the chaff of bad
questions to find the 'good' ones (for any particular definition of good)
becomes a bit of a put off.
Still, it is always easier to be polite, or simply ignore bad questions,
than start fires.
Or just drink more beer...
Wyzelli
--
($a,$b,$w,$t)=(' bottle',' of beer',' on the wall','Take one down, pass it
around');
$d='$_$a$s$b$w';$e='$_$a$s$b';sub d{$h=shift;$h=~s/\$(\w+)/${$1}/g;return$h}
sub
e{return(shift!=1)?'s':''}for(reverse(1..100)){$s=e($_);$f=d($d);$g=d($e);
$c.="$f\n$g\n$t\n";$_--;$s=e($_);$e=d($d);$c.="$e\n\n";}print"$c*hic*";
------------------------------
Date: Mon, 09 Jul 2001 18:17:03 GMT
From: PerlFAQ Server <faq@denver.pm.org>
Subject: FAQ: How can I convince my sysadmin/supervisor/employees to use version 5/5.005/Perl instead of some other language?
Message-Id: <zym27.83$T3.200250368@news.frii.net>
This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with every Standard Distribution of
Perl.
+
How can I convince my sysadmin/supervisor/employees to use version 5/5.005/Perl instead of some other language?
If your manager or employees are wary of unsupported software, or
software which doesn't officially ship with your operating system, you
might try to appeal to their self-interest. If programmers can be more
productive using and utilizing Perl constructs, functionality,
simplicity, and power, then the typical manager/supervisor/employee may
be persuaded. Regarding using Perl in general, it's also sometimes
helpful to point out that delivery times may be reduced using Perl
compared to other languages.
If you have a project which has a bottleneck, especially in terms of
translation or testing, Perl almost certainly will provide a viable,
quick solution. In conjunction with any persuasion effort, you should
not fail to point out that Perl is used, quite extensively, and with
extremely reliable and valuable results, at many large computer software
and hardware companies throughout the world. In fact, many Unix vendors
now ship Perl by default. Support is usually just a news-posting away,
if you can't find the answer in the *comprehensive* documentation,
including this FAQ.
See http://www.perl.org/advocacy/ for more information.
If you face reluctance to upgrading from an older version of perl, then
point out that version 4 is utterly unmaintained and unsupported by the
Perl Development Team. Another big sell for Perl5 is the large number of
modules and extensions which greatly reduce development time for any
given task. Also mention that the difference between version 4 and
version 5 of Perl is like the difference between awk and C++. (Well, OK,
maybe it's not quite that distinct, but you get the idea.) If you want
support and a reasonable guarantee that what you're developing will
continue to work in the future, then you have to run the supported
version. As of April 2001 that probably means running either of the
releases 5.6.1 (released in April 2001) or 5.005_03 (released in March
1999), although 5.004_05 isn't that bad if you absolutely need such an
old version (released in April 1999) for stability reasons. Anything
older than 5.004_05 shouldn't be used.
Of particular note is the massive bug hunt for buffer overflow problems
that went into the 5.004 release. All releases prior to that, including
perl4, are considered insecure and should be upgraded as soon as
possible.
In August 2000 in all Linux distributions a new security problem was
found in the optional 'suidperl' (not built or installed by default) in
all the Perl branches 5.6, 5.005, and 5.004, see
http://www.cpan.org/src/5.0/sperl-2000-08-05/
-
Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short. They represent an important
part of the Usenet tradition. They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.
If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile. If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.
Answers to questions about LOTS of stuff, mostly not related to
Perl, can be found by pointing your news client to
news:news.answers
or to the many thousands of other useful Usenet news groups.
Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release. It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.
The perlfaq manual page contains the following copyright notice.
AUTHOR AND COPYRIGHT
Copyright (c) 1997-1999 Tom Christiansen and Nathan
Torkington. All rights reserved.
This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.
02.00
--
This space intentionally left blank
------------------------------
Date: Tue, 10 Jul 2001 06:17:01 GMT
From: PerlFAQ Server <faq@denver.pm.org>
Subject: FAQ: How can I get a binary version of Perl?
Message-Id: <x5x27.106$T3.196184064@news.frii.net>
This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with every Standard Distribution of
Perl.
+
How can I get a binary version of Perl?
If you don't have a C compiler because your vendor for whatever reasons
did not include one with your system, the best thing to do is grab a
binary version of gcc from the net and use that to compile perl with.
CPAN only has binaries for systems that are terribly hard to get free
compilers for, not for Unix systems.
Some URLs that might help you are:
http://www.cpan.org/ports/
http://language.perl.com/info/software.html
Someone looking for a Perl for Win16 might look to Laszlo Molnar's djgpp
port in http://www.cpan.org/ports/#msdos , which comes with clear
installation instructions. A simple installation guide for MS-DOS using
Ilya Zakharevich's OS/2 port is available at
http://www.cs.ruu.nl/%7Epiet/perl5dos.html and similarly for Windows 3.1
at http://www.cs.ruu.nl/%7Epiet/perlwin3.html .
-
Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short. They represent an important
part of the Usenet tradition. They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.
If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile. If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.
Answers to questions about LOTS of stuff, mostly not related to
Perl, can be found by pointing your news client to
news:news.answers
or to the many thousands of other useful Usenet news groups.
Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release. It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.
The perlfaq manual page contains the following copyright notice.
AUTHOR AND COPYRIGHT
Copyright (c) 1997-1999 Tom Christiansen and Nathan
Torkington. All rights reserved.
This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.
02.02
--
This space intentionally left blank
------------------------------
Date: Tue, 10 Jul 2001 18:17:00 GMT
From: PerlFAQ Server <faq@denver.pm.org>
Subject: FAQ: I copied the Perl binary from one machine to another, but scripts don't work.
Message-Id: <wEH27.6$T3.172653056@news.frii.net>
This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with every Standard Distribution of
Perl.
+
I copied the Perl binary from one machine to another, but scripts don't work.
That's probably because you forgot libraries, or library paths differ.
You really should build the whole distribution on the machine it will
eventually live on, and then type "make install". Most other approaches
are doomed to failure.
One simple way to check that things are in the right place is to print
out the hard-coded @INC that perl looks through for libraries:
% perl -e 'print join("\n",@INC)'
If this command lists any paths that don't exist on your system, then
you may need to move the appropriate libraries to these locations, or
create symbolic links, aliases, or shortcuts appropriately. @INC is also
printed as part of the output of
% perl -V
You might also want to check out the section on "How do I keep my own
module/library directory?" in the perlfaq8 manpage.
-
Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short. They represent an important
part of the Usenet tradition. They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.
If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile. If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.
Answers to questions about LOTS of stuff, mostly not related to
Perl, can be found by pointing your news client to
news:news.answers
or to the many thousands of other useful Usenet news groups.
Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release. It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.
The perlfaq manual page contains the following copyright notice.
AUTHOR AND COPYRIGHT
Copyright (c) 1997-1999 Tom Christiansen and Nathan
Torkington. All rights reserved.
This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.
02.04
--
This space intentionally left blank
------------------------------
Date: Tue, 10 Jul 2001 12:17:02 GMT
From: PerlFAQ Server <faq@denver.pm.org>
Subject: FAQ: I don't have a C compiler on my system. How can I compile perl?
Message-Id: <2nC27.108$T3.188442624@news.frii.net>
This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with every Standard Distribution of
Perl.
+
I don't have a C compiler on my system. How can I compile perl?
Since you don't have a C compiler, you're doomed and your vendor should
be sacrificed to the Sun gods. But that doesn't help you.
What you need to do is get a binary version of gcc for your system
first. Consult the Usenet FAQs for your operating system for information
on where to get such a binary version.
-
Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short. They represent an important
part of the Usenet tradition. They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.
If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile. If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.
Answers to questions about LOTS of stuff, mostly not related to
Perl, can be found by pointing your news client to
news:news.answers
or to the many thousands of other useful Usenet news groups.
Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release. It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.
The perlfaq manual page contains the following copyright notice.
AUTHOR AND COPYRIGHT
Copyright (c) 1997-1999 Tom Christiansen and Nathan
Torkington. All rights reserved.
This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.
02.03
--
This space intentionally left blank
------------------------------
Date: Wed, 11 Jul 2001 00:17:01 GMT
From: PerlFAQ Server <faq@denver.pm.org>
Subject: FAQ: I grabbed the sources and tried to compile but gdbm/dynamic loading/malloc/linking/... failed. How do I make it work?
Message-Id: <1WM27.17$T3.172505088@news.frii.net>
This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with every Standard Distribution of
Perl.
+
I grabbed the sources and tried to compile but gdbm/dynamic loading/malloc/linking/... failed. How do I make it work?
Read the INSTALL file, which is part of the source distribution. It
describes in detail how to cope with most idiosyncrasies that the
Configure script can't work around for any given system or architecture.
-
Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short. They represent an important
part of the Usenet tradition. They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.
If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile. If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.
Answers to questions about LOTS of stuff, mostly not related to
Perl, can be found by pointing your news client to
news:news.answers
or to the many thousands of other useful Usenet news groups.
Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release. It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.
The perlfaq manual page contains the following copyright notice.
AUTHOR AND COPYRIGHT
Copyright (c) 1997-1999 Tom Christiansen and Nathan
Torkington. All rights reserved.
This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.
02.05
--
This space intentionally left blank
------------------------------
Date: Tue, 10 Jul 2001 00:17:01 GMT
From: PerlFAQ Server <faq@denver.pm.org>
Subject: FAQ: What machines support Perl? Where do I get it?
Message-Id: <1Qr27.102$T3.182917120@news.frii.net>
This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with every Standard Distribution of
Perl.
+
What machines support Perl? Where do I get it?
The standard release of Perl (the one maintained by the perl development
team) is distributed only in source code form. You can find this at
http://www.cpan.org/src/latest.tar.gz , which is in a standard Internet
format (a gzipped archive in POSIX tar format).
Perl builds and runs on a bewildering number of platforms. Virtually all
known and current Unix derivatives are supported (Perl's native
platform), as are other systems like VMS, DOS, OS/2, Windows, QNX, BeOS,
OS X, MPE/iX and the Amiga.
Binary distributions for some proprietary platforms, including Apple
systems, can be found http://www.cpan.org/ports/ directory. Because
these are not part of the standard distribution, they may and in fact do
differ from the base Perl port in a variety of ways. You'll have to
check their respective release notes to see just what the differences
are. These differences can be either positive (e.g. extensions for the
features of the particular platform that are not supported in the source
release of perl) or negative (e.g. might be based upon a less current
source release of perl).
-
Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short. They represent an important
part of the Usenet tradition. They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.
If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile. If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.
Answers to questions about LOTS of stuff, mostly not related to
Perl, can be found by pointing your news client to
news:news.answers
or to the many thousands of other useful Usenet news groups.
Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release. It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.
The perlfaq manual page contains the following copyright notice.
AUTHOR AND COPYRIGHT
Copyright (c) 1997-1999 Tom Christiansen and Nathan
Torkington. All rights reserved.
This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.
02.01
--
This space intentionally left blank
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
The Perl-Users Digest is a retransmission of the USENET newsgroup
comp.lang.perl.misc. For subscription or unsubscription requests, send
the single line:
subscribe perl-users
or:
unsubscribe perl-users
to almanac@ruby.oce.orst.edu.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
To request back copies (available for a week or so), send your request
to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
where x is the volume number and y is the issue number.
For other requests pertaining to the digest, send mail to
perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
sending perl questions to the -request address, I don't have time to
answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 1274
***************************************
