[28546] in Perl-Users-Digest
Perl-Users Digest, Issue: 9910 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Oct 31 14:15:28 2006
Date: Tue, 31 Oct 2006 11:15:19 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 31 Oct 2006 Volume: 10 Number: 9910
Today's topics:
opening things without the O_LARGEFILE flag <aduitsis@gmail.com>
Re: opening things without the O_LARGEFILE flag <tzz@lifelogs.com>
Re: opening things without the O_LARGEFILE flag xhoster@gmail.com
Re: opening things without the O_LARGEFILE flag <aduitsis@gmail.com>
Re: Perl equivalent to unix script <tintin@invalid.invalid>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Printing and Formatting data from hash (or array) <joe@inwap.com>
Re: Printing and Formatting data from hash (or array) anno4000@radom.zrz.tu-berlin.de
Re: Printing and Formatting data from hash (or array) <glex_no-spam@qwest-spam-no.invalid>
Problem installing ExtUtils::Command from CPAN <vfoley@gmail.com>
Re: Problem installing ExtUtils::Command from CPAN <sisyphus1@nomail.afraid.org>
Re: Problem installing ExtUtils::Command from CPAN <vfoley@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 30 Oct 2006 14:51:56 -0800
From: "Athanasios" <aduitsis@gmail.com>
Subject: opening things without the O_LARGEFILE flag
Message-Id: <1162248716.185457.145320@h48g2000cwc.googlegroups.com>
Hi everyone,
I am trying to open the /dev/net/tun character device with perl.
In C, I would issue:
open("/dev/net/tun", O_RDWR)
and continue as usual.
However, when I try to use sysopen in perl like
sysopen(TUNNELDEV, "/dev/net/tun", O_RDWR);
from the strace (truss) output I can see that instead it tries to do:
open("/dev/net/tun", O_RDWR|O_LARGEFILE)
which for some VERY strange reason succeeds but the file descriptor is
left in a bad state, so it is really unusable. For anything I try to do
afterwards, I get a
EBADFD (File descriptor in bad state).
As I have come down to the systel call level, there is no other reason
for this problem that I can think of except the O_LARGEFILE flag.
Indeed, a simple C program works quite fine without that flag.
I also have tried to use POSIX::open but it still adds the flag.
The documentation clearly states that from perl 5.6 and forth, the
O_LARGEFILE will be used whenever possible. But I really need to bypass
this and generate an open system call without it.
Does anyone know any conceivable way to accomplish this? Any help will
be appreciated.
If I should take this question to another group or list more suitable
to get an answer, could you also please indicate that group?
Kind Regards,
Athanasios
(I know, I know, the tun/tap driver may be slightly broken in the
strict sense, but let's leave that outside for a moment.)
------------------------------
Date: Tue, 31 Oct 2006 01:11:35 +0000
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: opening things without the O_LARGEFILE flag
Message-Id: <g69iri1gugo.fsf@lifelogs.com>
On 30 Oct 2006, aduitsis@gmail.com wrote:
> The documentation clearly states that from perl 5.6 and forth, the
> O_LARGEFILE will be used whenever possible. But I really need to bypass
> this and generate an open system call without it.
>
> Does anyone know any conceivable way to accomplish this? Any help will
> be appreciated.
While there may be other more appropriate ways, you could use
Inline::C maybe?
Ted
------------------------------
Date: 31 Oct 2006 05:10:59 GMT
From: xhoster@gmail.com
Subject: Re: opening things without the O_LARGEFILE flag
Message-Id: <20061031001130.276$b9@newsreader.com>
"Athanasios" <aduitsis@gmail.com> wrote:
> Hi everyone,
>
> I am trying to open the /dev/net/tun character device with perl.
>
> In C, I would issue:
>
> open("/dev/net/tun", O_RDWR)
>
> and continue as usual.
>
> However, when I try to use sysopen in perl like
>
> sysopen(TUNNELDEV, "/dev/net/tun", O_RDWR);
>
> from the strace (truss) output I can see that instead it tries to do:
>
> open("/dev/net/tun", O_RDWR|O_LARGEFILE)
>
> which for some VERY strange reason succeeds but the file descriptor is
> left in a bad state, so it is really unusable. For anything I try to do
> afterwards, I get a
>
> EBADFD (File descriptor in bad state).
>
> As I have come down to the systel call level, there is no other reason
> for this problem that I can think of except the O_LARGEFILE flag.
> Indeed, a simple C program works quite fine without that flag.
Just to make sure it is absolutely nailed down, does the simple C program
stop working fine if you add the O_LARGEFILE in?
> I also have tried to use POSIX::open but it still adds the flag.
>
> The documentation clearly states that from perl 5.6 and forth, the
> O_LARGEFILE will be used whenever possible. But I really need to bypass
> this and generate an open system call without it.
Maybe you could compile perl without large file support?
Or write a small C server that will accept socket connections and
proxy /dev/net/tun over the socket.
Xho
--
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service $9.95/Month 30GB
------------------------------
Date: 31 Oct 2006 02:01:23 -0800
From: "Athanasios" <aduitsis@gmail.com>
Subject: Re: opening things without the O_LARGEFILE flag
Message-Id: <1162288883.321629.159100@m73g2000cwd.googlegroups.com>
xhoster@gmail.com wrote:
> "Athanasios" <aduitsis@gmail.com> wrote:
> > Hi everyone,
> >
> > I am trying to open the /dev/net/tun character device with perl.
> >
> > In C, I would issue:
> >
> > open("/dev/net/tun", O_RDWR)
> >
> > and continue as usual.
> >
> > However, when I try to use sysopen in perl like
> >
> > sysopen(TUNNELDEV, "/dev/net/tun", O_RDWR);
> >
> > from the strace (truss) output I can see that instead it tries to do:
> >
> > open("/dev/net/tun", O_RDWR|O_LARGEFILE)
> >
> > which for some VERY strange reason succeeds but the file descriptor is
> > left in a bad state, so it is really unusable. For anything I try to do
> > afterwards, I get a
> >
> > EBADFD (File descriptor in bad state).
> >
> > As I have come down to the systel call level, there is no other reason
> > for this problem that I can think of except the O_LARGEFILE flag.
> > Indeed, a simple C program works quite fine without that flag.
>
> Just to make sure it is absolutely nailed down, does the simple C program
> stop working fine if you add the O_LARGEFILE in?
I 'll confirm that shortly, I haven't tried it yet. But judging from
the system calls I see in truss, it almost surely won't work.
>
>
> > I also have tried to use POSIX::open but it still adds the flag.
> >
> > The documentation clearly states that from perl 5.6 and forth, the
> > O_LARGEFILE will be used whenever possible. But I really need to bypass
> > this and generate an open system call without it.
>
> Maybe you could compile perl without large file support?
>
> Or write a small C server that will accept socket connections and
> proxy /dev/net/tun over the socket.
Yes, these are valid options, as is the Inline::C idea which the
previous poster suggested. But the general idea is that there *should*
be a way to omit the O_LARGEFILE flag if needed.
Kind Regards,
Athanasios
>
> Xho
>
> --
> -------------------- http://NewsReader.Com/ --------------------
> Usenet Newsgroup Service $9.95/Month 30GB
------------------------------
Date: Tue, 31 Oct 2006 08:24:03 +1300
From: "Tintin" <tintin@invalid.invalid>
Subject: Re: Perl equivalent to unix script
Message-Id: <45464399$0$12066$88260bb3@free.teranews.com>
"Mike" <mikedawg@gmail.com> wrote in message
news:1162230727.836071.158630@k70g2000cwa.googlegroups.com...
> Ok. . . Well, I'm sure here comes another dumb question. I'm fairly
> handy with unix and unix scripting, however, I'm terrible at perl.
>
> What I'm looking to do with a perl script is the equivalent of the
> following unix (bash) script:
>
> cat tempfile1 | sort > newfile2; rm tempfile1
Handy at Unix, but still using UUOC?
--
Posted via a free Usenet account from http://www.teranews.com
------------------------------
Date: 31 Oct 2006 08:10:08 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.7 $)
Message-Id: <454704df$0$81355$ae4e5890@news.nationwide.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.7 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Mon, 30 Oct 2006 12:25:57 -0800
From: Joe Smith <joe@inwap.com>
Subject: Re: Printing and Formatting data from hash (or array)
Message-Id: <s4-dna3p3reS_dvYnZ2dnUVZ_tednZ2d@comcast.com>
Mike wrote:
> I found the example of this to print all the values
> I have in a hash, but it seems like it is a single array within the
> hash repeating (not printing multiple items in hash):
>
> while ( ($key,$value) = each %hash ) {
> print "$key => $value\n";
> }
>
> However, when I copy all the hash data to an array, and print the
> array, it doesn't show all the duplicated data.
That while() loop _will_ print out each key once and only once.
It does not produce any duplicates and does not skip anything.
Whatever you are doing in your program, it must be more than
what is being shown there. (I have seen this sort of problem
show up before, but it turns out the programmer had two
different instances of each() on the same hash in nested loops.)
Can you produce any code that we can run to duplicate your problem?
-Joe
------------------------------
Date: 31 Oct 2006 15:05:23 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: Printing and Formatting data from hash (or array)
Message-Id: <4qp71jFo7g1nU1@news.dfncis.de>
J. Gleixner <glex_no-spam@qwest-spam-no.invalid> wrote in comp.lang.perl.misc:
> Mike wrote:
[...]
> > print $temphash[$n];
> > $n++;
> > print "\t\t";
> > print $temphash[$n];
> > print "\n";
> > $n++;
> > }
>
> If that actually prints the values you want. You may put the print on
> one line:
>
> print "$tmphash[$n++]\t\t$temphash[$n++]\n";
You're accessing two different variables.
That's risky. Perl is, in principle, allowed to evaluate parts of
an expression in any sequence, so the results of the two ++ operations
are not well defined. I realize the current Perl produces the expected
result, and it's unlikely to change, but the behavior is undocumented.
A safe alternative is
print "$temphash[ $n]\t\t$temphash[ $n + 1]\n";
$n += 2;
but isn't a single statement anymore.
Anno
------------------------------
Date: Tue, 31 Oct 2006 10:01:20 -0600
From: "J. Gleixner" <glex_no-spam@qwest-spam-no.invalid>
Subject: Re: Printing and Formatting data from hash (or array)
Message-Id: <45477334$0$10305$815e3792@news.qwest.net>
anno4000@radom.zrz.tu-berlin.de wrote:
> J. Gleixner <glex_no-spam@qwest-spam-no.invalid> wrote in comp.lang.perl.misc:
>> If that actually prints the values you want. You may put the print on
>> one line:
>>
>> print "$tmphash[$n++]\t\t$temphash[$n++]\n";
>
> You're accessing two different variables.
>
> That's risky. Perl is, in principle, allowed to evaluate parts of
> an expression in any sequence, so the results of the two ++ operations
> are not well defined. I realize the current Perl produces the expected
> result, and it's unlikely to change, but the behavior is undocumented.
> A safe alternative is
>
> print "$temphash[ $n]\t\t$temphash[ $n + 1]\n";
> $n += 2;
>
> but isn't a single statement anymore.
Thanks for the correction Anno. I knew that and I guess I
was so focused on getting rid of all the print statements
that I over-looked it.
------------------------------
Date: 30 Oct 2006 20:43:11 -0800
From: "Vincent Foley" <vfoley@gmail.com>
Subject: Problem installing ExtUtils::Command from CPAN
Message-Id: <1162269791.526273.284920@h48g2000cwc.googlegroups.com>
Hello clpm,
I am trying to install the ExtUtils::Command module on my Ubuntu (Edgy
Eft) machine, but I seem to fall into a practical joke of some sort,
because I am told during the installation that CPAN.pm cannot install
ExtUtils::Command because ExtUtils/Command.pm isn't found in my @INC.
Could anyone help me out with this problem? The version of Perl used
on Edgy Eft is 5.8.8. For more information, I have included the entire
output of what happens when I try to do the installation.
Thanks,
Vincent.
cpan> install ExtUtils::Command
CPAN: Storable loaded ok
Going to read /home/vince/.cpan/Metadata
Database was generated on Thu, 26 Oct 2006 05:23:55 GMT
Running install for module ExtUtils::Command
Running make for R/RK/RKOBES/ExtUtils-Command-1.12.tar.gz
CPAN: Digest::MD5 loaded ok
CPAN: Compress::Zlib loaded ok
Checksum for
/home/vince/.cpan/sources/authors/id/R/RK/RKOBES/ExtUtils-Command-1.12.tar.gz
ok
Scanning cache /home/vince/.cpan/build for sizes
ExtUtils-Command-1.12/
ExtUtils-Command-1.12/t/
ExtUtils-Command-1.12/t/shell_exit.t
ExtUtils-Command-1.12/t/shell_command.t
ExtUtils-Command-1.12/t/eu_command.t
ExtUtils-Command-1.12/t/lib/
ExtUtils-Command-1.12/t/lib/TieOut.pm
ExtUtils-Command-1.12/META.yml
ExtUtils-Command-1.12/lib/
ExtUtils-Command-1.12/lib/ExtUtils/
ExtUtils-Command-1.12/lib/ExtUtils/Command.pm
ExtUtils-Command-1.12/lib/Shell/
ExtUtils-Command-1.12/lib/Shell/Command.pm
ExtUtils-Command-1.12/Changes
ExtUtils-Command-1.12/MANIFEST
ExtUtils-Command-1.12/Build.PL
ExtUtils-Command-1.12/Makefile.PL
ExtUtils-Command-1.12/README
Removing previously used /home/vince/.cpan/build/ExtUtils-Command-1.12
CPAN.pm: Going to build R/RK/RKOBES/ExtUtils-Command-1.12.tar.gz
Argument "6.30_01" isn't numeric in numeric ge (>=) at Makefile.PL line
22.
Checking if your kit is complete...
Looks good
Writing Makefile for ExtUtils::Command
Can't locate ExtUtils/Command.pm in @INC (@INC contains:
/home/vince/perl /home/vince/perl/lib/perl/5.8.7
/home/vince/perl/share/perl/5.8.7 /etc/perl /usr/local/lib/perl/5.8.8
/usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5
/usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .).
BEGIN failed--compilation aborted.
make: *** [blib/lib/ExtUtils/.exists] Error 2
/usr/bin/make -- NOT OK
Running make test
Can't test without successful make
Running make install
make had returned bad status, install seems impossible
------------------------------
Date: Tue, 31 Oct 2006 19:44:33 +1100
From: "Sisyphus" <sisyphus1@nomail.afraid.org>
Subject: Re: Problem installing ExtUtils::Command from CPAN
Message-Id: <45470e0e$0$5106$afc38c87@news.optusnet.com.au>
"Vincent Foley" <vfoley@gmail.com> wrote in message
news:1162269791.526273.284920@h48g2000cwc.googlegroups.com...
.
.
>
> CPAN.pm: Going to build R/RK/RKOBES/ExtUtils-Command-1.12.tar.gz
>
> Argument "6.30_01" isn't numeric in numeric ge (>=) at Makefile.PL line
> 22.
> Checking if your kit is complete...
> Looks good
> Writing Makefile for ExtUtils::Command
> Can't locate ExtUtils/Command.pm in @INC (@INC contains:
> /home/vince/perl /home/vince/perl/lib/perl/5.8.7
> /home/vince/perl/share/perl/5.8.7 /etc/perl /usr/local/lib/perl/5.8.8
> /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5
> /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .).
> BEGIN failed--compilation aborted.
> make: *** [blib/lib/ExtUtils/.exists] Error 2
> /usr/bin/make -- NOT OK
> Running make test
> Can't test without successful make
> Running make install
> make had returned bad status, install seems impossible
>
Neat joke, indeed :-)
EU::Command is part of core perl with 5.8.7 and 5.8.8 - so definitely should
have been part of your perl to begin with. What became of it ?
Does the module install if you simply download ExtUtils-Command-1.12.tar.gz
from CPAN, extract to some location, cd to that location, and run:
perl Makefile.PL
make test
make install
Are you able to install *any* perl modules at all ? (Sometimes the default
perl installation is not fully functional - and to get a fully functional
version of perl it is necessary to install the perl "devel" version from the
OS installation media. But if we're dealing with a perl that you've built
yourself then this should *not* be the case.)
EU::Command is pure perl, so if all else fails, you might be able to get
things working by copying Command.pm to the ExtUtils directory under one of
the @INC directories. But if you're missing the "devel" installation then
that probably won't be sufficient in itself.
Cheers,
Rob
------------------------------
Date: 31 Oct 2006 04:06:02 -0800
From: "Vincent Foley" <vfoley@gmail.com>
Subject: Re: Problem installing ExtUtils::Command from CPAN
Message-Id: <1162296362.431983.202500@k70g2000cwa.googlegroups.com>
I just tried installing WWW::Mechanize and IO::Prompt and both failed
because of the absence of ExtUtils/Command.pm in my @INC.
I have downloaded libperl-dev from apt-get, but this hasn't fixed the
problem. When I went to ~/.cpan/build/ExtUtils-Command-1.12/ and tried
the perl Makefile.PL; make test, I got the same error as before.
Now, I just tried something that I think worked, but I'm not sure: I
copied ExtUtils/Command.pm into my @INC so that I could perform the
manual installation of the module and this worked. If I run into more
problems, I'll let you know.
Also, I would be interested to know if you guys think I should compile
Perl5 from scratch instead of using the Ubuntu-provided packages; I
know the Ruby guys strongly recommend against using the Debian package
of Ruby because it lacks all sorts of modules that are normally
installed by default.
Vincent
Sisyphus wrote:
> "Vincent Foley" <vfoley@gmail.com> wrote in message
> news:1162269791.526273.284920@h48g2000cwc.googlegroups.com...
> .
> .
> >
> > CPAN.pm: Going to build R/RK/RKOBES/ExtUtils-Command-1.12.tar.gz
> >
> > Argument "6.30_01" isn't numeric in numeric ge (>=) at Makefile.PL line
> > 22.
> > Checking if your kit is complete...
> > Looks good
> > Writing Makefile for ExtUtils::Command
> > Can't locate ExtUtils/Command.pm in @INC (@INC contains:
> > /home/vince/perl /home/vince/perl/lib/perl/5.8.7
> > /home/vince/perl/share/perl/5.8.7 /etc/perl /usr/local/lib/perl/5.8.8
> > /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5
> > /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .).
> > BEGIN failed--compilation aborted.
> > make: *** [blib/lib/ExtUtils/.exists] Error 2
> > /usr/bin/make -- NOT OK
> > Running make test
> > Can't test without successful make
> > Running make install
> > make had returned bad status, install seems impossible
> >
>
> Neat joke, indeed :-)
>
> EU::Command is part of core perl with 5.8.7 and 5.8.8 - so definitely should
> have been part of your perl to begin with. What became of it ?
>
> Does the module install if you simply download ExtUtils-Command-1.12.tar.gz
> from CPAN, extract to some location, cd to that location, and run:
>
> perl Makefile.PL
> make test
> make install
>
> Are you able to install *any* perl modules at all ? (Sometimes the default
> perl installation is not fully functional - and to get a fully functional
> version of perl it is necessary to install the perl "devel" version from the
> OS installation media. But if we're dealing with a perl that you've built
> yourself then this should *not* be the case.)
>
> EU::Command is pure perl, so if all else fails, you might be able to get
> things working by copying Command.pm to the ExtUtils directory under one of
> the @INC directories. But if you're missing the "devel" installation then
> that probably won't be sufficient in itself.
>
> Cheers,
> Rob
------------------------------
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.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
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 9910
***************************************
