Ask a Question related to PERL Miscellaneous, Design and Development.
-
Michael P. Broida #1
Re: strange error "Unsuccessful stat on filename "
Pitt wrote:
Based solely on the error message (don't have Unix>
> Hi,
> I get such a error
> Unsuccessful stat on filename containing newline at
> /usr/local/lib/perl5/5.8.0/ExtUtils/MM_Unix.pm line 2775
>
> when i install a module .
>
> I use HP-UX IA64
> i wouder does the file MM_Unix.pm contains some characters which the HP-UX
> does not recognise or Perl in HP-UX
> does not know.
system to verify), I think this::
MM_Unix.pm line 2775 is the line of Perl code that
was executing when it found a newline in a DATA ITEM
being passed to "stat" as a filename. The message
does NOT indicate anything wrong in MM_Unix.pm.
You need to see just what that data item was that
was being passed to "stat" as a filename. It's
probably a string that didn't get "chomp"ed.
Again, I don't have a Unix system to verify this on,
but it makes sense to me from the wording of the
error message.
Mike
Michael P. Broida Guest
-
"The filename or extension is too long" Error when opening Acrobat 6.0
I get the same error. It just hangs at the splash screen, taking 100% CPU and then after about an hour I get that error. When I click ok, I get a... -
<param name="filename" value="file:///C:/...."
Hello, got a problem with the next code trying to load the swf from the client pc: <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"... -
open "filename.txt" for input not working
I'm working on migrating an Classic ASP/VB6 COM application from an NT Server with IIS<6 to an virtual machine running Windows Server 2003 and IIS... -
Download-Script: strange "[1]." in Filename
Hello folks! I've got a strange problem with my download-script in conjunction with M$ internet explorer, if the filename I want to link to... -
Uploading large files - error "stat failed"
Hello, I have a page where i can upload binary file (using the HTML input type=file approach). This works fine for relatively small files... -
Tad McClellan #2
Re: strange error "Unsuccessful stat on filename "
Pitt <randy_chang@sohu.com> wrote:
> Unsuccessful stat on filename containing newline at
Did you look up that message in perldiag.pod?
=item Unsuccessful %s on filename containing newline
(W newline) A file operation was attempted on a filename, and that
operation failed, PROBABLY because the filename contained a newline,
PROBABLY because you forgot to chomp() it off. See L<perlfunc/chomp>.
--
Tad McClellan SGML consulting
[email]tadmc@augustmail.com[/email] Perl programming
Fort Worth, Texas
Tad McClellan Guest
-
James Willmore #3
Re: strange error "Unsuccessful stat on filename "
> Hi,
What module are you trying to install? How are you installing it?> I get such a error
> Unsuccessful stat on filename containing newline at
> /usr/local/lib/perl5/5.8.0/ExtUtils/MM_Unix.pm line 2775
>
> when i install a module .
>
> I use HP-UX IA64
> i wouder does the file MM_Unix.pm contains some characters which the HP-UX
> does not recognise or Perl in HP-UX
> does not know.
Have you had trouble installing other modules?
At first glance, it looks like someone may have made a mistake in
creating the Makefile.PL file for this module. It may not be Perl
or the OS that's at fault, but the mdoule.
Jim
James Willmore Guest
-
pitt #4
Re: strange error "Unsuccessful stat on filename "
I got the error when i install Compress::zlib
when run "perl Makefile.PL"
there two statement as following:
"Unsuccessful stat on filename containing newline at
/usr/local/lib/perl5/5.8.0/IA64.ARCHREV_0/Cwd.pm line 213.
Parsing config.in...
Looks Good.
Up/Downgrade complete.
Unsuccessful stat on filename containing newline at
/usr/local/lib/perl5/5.8.0/ExtUtils/MM_Unix.pm line 2775.
WARNING: CAPI is not a known parameter.
Writing Makefile for zlib
Writing Makefile for Compress::Zlib
"
It seems the "Unsuccessful stat..." does not lead errors.
another question is that in make file ,the CC is defined to gcc ,but i have
no gcc in system ,why they do so?
"James Willmore" <jwillmore@cyberia.com>
??????:e0160815.0308141522.239b300c@posting.google .com...HP-UX> > Hi,
> > I get such a error
> > Unsuccessful stat on filename containing newline at
> > /usr/local/lib/perl5/5.8.0/ExtUtils/MM_Unix.pm line 2775
> >
> > when i install a module .
> >
> > I use HP-UX IA64
> > i wouder does the file MM_Unix.pm contains some characters which the>> > does not recognise or Perl in HP-UX
> > does not know.
> What module are you trying to install? How are you installing it?
> Have you had trouble installing other modules?
>
> At first glance, it looks like someone may have made a mistake in
> creating the Makefile.PL file for this module. It may not be Perl
> or the OS that's at fault, but the mdoule.
>
> Jim
pitt Guest
-
James Willmore #5
Re: strange error "Unsuccessful stat on filename "
"pitt" <randy_chang@sohu.com> wrote in message news:<bhi4i8$j79$1@mail.cn99.com>...
To change the compiler setting for the makefile, type the following:> I got the error when i install Compress::zlib
> when run "perl Makefile.PL"
> there two statement as following:
>
> "Unsuccessful stat on filename containing newline at
> /usr/local/lib/perl5/5.8.0/IA64.ARCHREV_0/Cwd.pm line 213.
> Parsing config.in...
> Looks Good.
> Up/Downgrade complete.
> Unsuccessful stat on filename containing newline at
> /usr/local/lib/perl5/5.8.0/ExtUtils/MM_Unix.pm line 2775.
> WARNING: CAPI is not a known parameter.
> Writing Makefile for zlib
> Writing Makefile for Compress::Zlib
>
> "
> It seems the "Unsuccessful stat..." does not lead errors.
> another question is that in make file ,the CC is defined to gcc ,but i have
> no gcc in system ,why they do so?
perl Makefile.PL CC=<your compiler> LD=<your linker>
HOWEVER, you should find out what Perl was built with. Type:
perl -V
This will give you all the various options, directories, compiler,
etc. that was used to build Perl. If you got a package instead of
building Perl yourself, the producers of the package may have used the
gcc compiler. I ran into a similar issue using Solaris at work. The
admin later installed the gcc compiler and all was right after that.
You may not want to go that route, but life appears to be so much
easier if you do.
You're getting a CAPI warning, but it doesn't say it's harmless. I'm
not sure if using a different compiler, or setting your compiler
option while building the makefile will solve this. You'll have to
investigate this further or perhaps someone else knows what that's
refering to.
As far as why that's the default ... I defer to others who know the
in's and out's of Perl much better than myself. I have only opinions
about it, but they may be very far off base.
HTH
Jim
James Willmore Guest



Reply With Quote

