Re: MacOSX::File uploaded to CPAN

2002-01-09 Thread Dan Kogai
Fred, on 02.1.9 9:12 AM, Wilfredo Sánchez at [EMAIL PROTECTED] wrote: > Have you considered adding this functionality into existing File I/O > code (possibly with some new options) instead of adding whole new API? Do you mean that I modify File::Copy? That's a possibility but as I answered in M

Help with Perl on MacOSX

2002-01-09 Thread Anthony Mason
Hello, First, let me apologize if I'm sending this to the wrong place. I am in need of help with Perl on the Mac OSX. Please take a look at the following listing: Welcome to Darwin! [localhost:~] anthonym% ls ApplicationsLibrary Perl Stuff Sites mac_perl.pl Des

Help with Perl on MacOSX

2002-01-09 Thread Paul McCann
Hi Anthony, almost certainly a line endings problem. The script needs "unix" line endings, and I'll bet it's currently got "mac" line endings. Check the settings in your text editor. Something like perl -pi -e 'tr/\015/\012/' macperl.pl should sort out the problem if my guess is right. Che

Re: Help with Perl on MacOSX

2002-01-09 Thread Bohdan Peter Rekshynskyj
At 19:12 -0500 1/9/2002, Anthony Mason wrote: >Hello, > > First, let me apologize if I'm sending this to the wrong place. I am in need of >help with Perl on the Mac OSX. Please take a look at the following listing: > >Welcome to Darwin! >[localhost:~] anthonym% ls >ApplicationsLibrary

Re: Help with Perl on MacOSX

2002-01-09 Thread Charles Albrecht
At 7:12 PM -0500 1/9/2002, Anthony Mason wrote: >Hello, > >[localhost:~] anthonym% ./mac_perl.pl >../mac_perl.pl: Command not found. >[localhost:~] anthonym% > > >I cannot get my Perl code to execute. Do you have any idea what I'm >doing wrong? Here is the file source: It looks like you've got

Re: Help with Perl on MacOSX

2002-01-09 Thread Chris Devers
On Wed, 9 Jan 2002, Anthony Mason wrote: > Welcome to Darwin! > [localhost:~] anthonym% ls > ApplicationsLibrary Perl Stuff Sites > mac_perl.pl > Desktop Movies Picturesex1_1.pl > Documents Music Public ex1_1_perl.pl >

Re: Help with Perl on MacOSX

2002-01-09 Thread Chris Devers
On Wed, 9 Jan 2002, Chris Devers wrote: > ok, now I'm confused too. Anyone else have better ideas? Welp, at Paul McCann's suggestion... [localhost Wed 7:26:57pm ~]% ls -la perltest.pl -rwx--x--x 1 chris staff 48 Jan 9 19:21 perltest.pl [localhost Wed 7:28:51pm ~]% perl -pi -e 'tr/\015/\

Re: Help with Perl on MacOSX

2002-01-09 Thread Charles Albrecht
At 6:34 PM -0600 1/9/2002, Chris Devers wrote: > >I created that script by pasting from one Terminal window's email client >to another's Vim editor, so the line endings got screwed up while passing >through the system clipboard. Should OSX Perl be more tolerant of this >sort of thing? Pasting isn

Re: MacOSX::File uploaded to CPAN

2002-01-09 Thread Ken Williams
On Wednesday, January 9, 2002, at 03:45 AM, Dan Kogai wrote: > Do you mean that I modify File::Copy? That's a possibility but as I > answered in MacOSX::File::Copy vs. File::Coply, I believe File::Copy > should > behave like /bin/cp (actually, copy() does cp -p because it copies > mtime and >

CPAN make problem

2002-01-09 Thread Simon Troup
Hello, I keep getting this error when trying to install modules with CPAN (happens with nearly all of them). cc1obj: Invalid option `-flat_namespace' make: *** [Perl.o] Error 1 /usr/bin/make -- NOT OK Running make test Can't test without successful make Running make install make had retur

Re: CPAN make problem

2002-01-09 Thread Terrence Brannon
which version of Mac OS X are you using? 10.0? Also, look thru the old msgs of this look for relevant posts. here is one: http://archive.develooper.com/macosx%40perl.org/msg01044.html and a bit more context before the error occurence would help us out. On Wednesday, January 9, 2002, at 11:31

Re: Help with Perl on MacOSX

2002-01-09 Thread Ken Williams
On Wednesday, January 9, 2002, at 06:57 PM, Charles Albrecht wrote: > At 6:34 PM -0600 1/9/2002, Chris Devers wrote: >> >> I created that script by pasting from one Terminal window's email >> client >> to another's Vim editor, so the line endings got screwed up while >> passing >> through the