Re: Test Mac::Carbon build for me?
In article [EMAIL PROTECTED], [EMAIL PROTECTED] (Ken Williams) wrote: I've been working on the ExtUtils::ParseXS module, which is designed to render this approach obsolete. It's on CPAN right now, maybe it could be used here instead of custom/version-specific xsubpps? The goal is to have One True Version of xsubpp, as a module instead of a script, which works on any [reasonable] platform version of perl. I've started with the xsubpp in bleadperl, and it seems to backport fine to 5.6.0 from my testing so far. That sound interesting, but I haven't the time or energy to put into this at the moment. :) -- Chris Nandor [EMAIL PROTECTED]http://pudge.net/ Open Source Development Network[EMAIL PROTECTED] http://osdn.com/
Perl Wrestling Federation Bout: 5.6 vs. 5.8
I figure it's time I bit the bullet and installed 5.8. Having completely blown it last time, however, I have a question. Have we come to any kind of concensus as to whether it's better to replace 5.6 with 5.8 or to stash 5.8 somewhere out of the way and leave the Apple installed 5.6 where it is? dha -- David H. Adler - [EMAIL PROTECTED] - http://www.panix.com/~dha/ 'Don't be tempted to veer off!' - Paul McGann
Re: Perl Wrestling Federation Bout: 5.6 vs. 5.8
On Fri, Dec 13, 2002 at 02:29:41PM -0500, John Siracusa wrote: On 12/13/02 2:16 PM, David H. Adler wrote: Have we come to any kind of concensus as to whether it's better to replace 5.6 with 5.8 or to stash 5.8 somewhere out of the way and leave the Apple installed 5.6 where it is? It's better to leave the Apple-provided 5.6.0 where it is and install 5.8.0 elsewhere unless you really know what you're doing. I was kind of guessing that. Is there any favored place? Should I just punt and use /opt ? The only remaining question is whether or not you should link /usr/bin/perl to your 5.8.0 install. Remember that OS X uses perl as part of its normal functioning, so you need to make sure that /usr/bin/perl always works the way it's expected to...even when that includes broken behavior, as in the Apple(!) installer that expected /usr/bin/perl to accept EQ as a valid operator (5.6.0 does, 5.8.0 doesn't) Yeah, deprecation is a bear when people don't read the docs, ain't it? :-) dha -- David H. Adler - [EMAIL PROTECTED] - http://www.panix.com/~dha/ Theoretically, you could add hyperpolysyllabic to any word to make it longer and not alter the meaning. - Matthew Mankiewich
Re: Perl Wrestling Federation Bout: 5.6 vs. 5.8
On Friday, December 13, 2002, at 11:48 AM, David H. Adler wrote: I was kind of guessing that. Is there any favored place? Should I just punt and use /opt ? Up to you. I favor /usr/local, which isn't used by Mac OS X. So you should be safe there. David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: Perl Wrestling Federation Bout: 5.6 vs. 5.8
On 12/13/02 2:48 PM, David H. Adler wrote: On Fri, Dec 13, 2002 at 02:29:41PM -0500, John Siracusa wrote: On 12/13/02 2:16 PM, David H. Adler wrote: Have we come to any kind of concensus as to whether it's better to replace 5.6 with 5.8 or to stash 5.8 somewhere out of the way and leave the Apple installed 5.6 where it is? It's better to leave the Apple-provided 5.6.0 where it is and install 5.8.0 elsewhere unless you really know what you're doing. I was kind of guessing that. Is there any favored place? Should I just punt and use /opt ? I like to live dangerously: I move /Library/Perl out of the way (it's essentially empty anyway in a fresh OS X install, IIRC) and then I install 5.8.0 in with the modules going into /Library/Perl and the binaries/scripts going into /usr/local/bin. Then I point /usr/bin/perl at /usr/local/bin/perl, and vow to never attempt to install CPAN modules using the old /usr/bin/perl executable :) -John
Re: Perl Wrestling Federation Bout: 5.6 vs. 5.8
On 12/13/02 3:50 PM, Andy Lester wrote: It's better to leave the Apple-provided 5.6.0 where it is and install 5.8.0 elsewhere unless you really know what you're doing. Why? Like I said in my post: On 12/13/02 2:29 PM, John Siracusa wrote: Remember that OS X uses perl as part of its normal functioning, so you need to make sure that /usr/bin/perl always works the way it's expected to...even when that includes broken behavior, as in the Apple(!) installer that expected /usr/bin/perl to accept EQ as a valid operator (5.6.0 does, 5.8.0 doesn't) Also remember that software updates from Apple may write files right on top of your Perl install since they expect the original 5.6.0 install to be just as it was out of the box. In generally, it's a good idea to stay out of the way of any Unix-ish files/apps that came with the system. Perl is the only oddball that I mingle somewhat with Apple's stuff (by using /Library/Perl). I make sure everything else is isolated in /usr/local, which Apple does not use. -John
new to unix: basic help
Hi all: It's almost embarrassing to write to this list (I have books by of some of you guys: Randal, Chris, etc.) and I regret to waste your time in something so trivial as this, but I'm new to Programming (I'm a musician; took up 2 programming 2 years ago), new to Perl (1.5 years) and new to Unix (switching from macos), so any time I see the install instructions say something like The usual make, test, install routine, my eyes just stare at the distance with a blank expression in my face. Can somebody please supply with the actual commands involved in The usual make, test, install routine, starting from the folder where my downloaded software would be? Thanks a lot and, wow!, it's really great to be in this list. Last night I said to my wife See this guy's name in this book cover? Now take a look at my Inbox here..., cool, eh! Riccardo -- mailto:[EMAIL PROTECTED] http://www.riccardoperotti.com
Re: new to unix: basic help
On Friday, December 13, 2002, at 04:54 PM, Riccardo Perotti wrote: Can somebody please supply with the actual commands involved in The usual make, test, install routine, starting from the folder where my downloaded software would be? The whole routine is pretty well covered in the 'perlmodinstall' document. You can read it with 'perldoc'; i.e. pop open a Terminal window, and enter perldoc perlmodinstall. Note that, as far as this and most other Perl docs are concerned, Macintosh == classic MacOS, while OS X == UNIX. sherm-- UNIX: Where /sbin/init is Job 1.
New Perl install
After getting a new powerbook, I attempted to install perl 5.8.0 according to the instructions at apple.com. Everything appeared to work correctly, (configure, make, make install and so forth not having any problems), but now fink returns: dyld: perl Undefined symbols: _Perl_safefree _Perl_safemalloc _Perl_saferealloc _Perl_sv_2pv _perl_call_sv _perl_eval_sv _perl_get_sv CPAN returns the same error when attempting to do anything and crashes. This is a fairly vanilla install ... not a whole lot is on it, yet. Any help would be appreciated. Jeffrey Melloy [EMAIL PROTECTED]
Re: new to unix: basic help
Puneet Kishor wrote: His seven tips. All very good. I will add just a couple more. Sign up at www.perlmonks.org. It has even more of the names in the perl community, than this list. It has been an invaluable resource for me. Perlmonks has a broad and deep dicsussion forum (actually several with somewhat different foci), and excellent collection of code, a huge collection of snippets, a wonderful search tool. and even an area to show off, when you're bold enough to show off your code in front of the authors of all your favorite perl books. For UNIX resources you might also want to try: Root Prompt, Rosetta Stone, SAGE, Geek-Girl's UNIX Reference, and Sysadmin magazine (online or print). And don't forget that you OS and you programming language of choice (that's why you're here right?) have extensive online documentation. Not the most scintillating reading, but always at your fingertips. If you try those sources first, you'll also find the gurus out there much more willing to help wiuth the tough problems. There's a lot to be said for RTFM.
