Hi Claudio, Your friend isn't running against the system Perl. Ask them to do /usr/bin/perl -V
I'd guess they are running MacPorts if they don't actually know the nature of their self installed Perl, which on Msc OS X 10.6.6 will install as a 64 bit static non threaded Perl by default. (You can specify other options at install to get MacPorts to build to your requirements.) The system Perl (/usr/bin/perl) on 10.6.6 comes built for three architectures, ppc, i386 and x86_64. It comes as Perl 5.8.9 and Perl 5.10.0. What you get when you call /usr/bin/perl depends on system and environment settings. By default you get a 64 bit 5.10.0 Perl. (x86_64 architecture). The pre-installed wxWidgets build has only has ppc and i386 architectures. So the innocent user will get no joy. The original user is running Mac OS X 10.5.x, which has a different default setup and Perl 5.8.8 - so as they seem to have /usr/bin/perl pointing at a Perl 5.10 - other things have happened - either to Perl or the OS. It is perfectly possible to build Alien-wxWidgets and Wx on Mac OS X system Perl. The wxPerl list has many threads which just about cover all situations. However, once you know the above you should run to ./Configure or MacPorts with all haste and leave /usr/bin/perl to the system and Apple Update. Using MacPorts, you can specify the variants 'perl5.12', 'threads' and 'shared' at install (or re-install) time. MacPorts will update your profile so within your environment you get 'perl' pointing at your MacPorts install. If you intend using PAR::Packer or the like at some time, you may also wish to specify the 'universal' variant for a more portable Perl across architectures. Perhaps someone out there has more experience with MacPorts? I've only used it to test something against but once I got the default 'non-threaded' static delivery, it did not take long to find out about 'variants' and how to get the type of Perl I wanted. You could also just 'give in' and install ActivePerl - on which Padre builds fine for me. (ppms etc) Hope this helps anyone starting out with Perl on Mac OS X to avoid grief and abandon the system Perl sooner rather than later. Regards Mark On 22/01/2011 22:13, Claudio Ramirez wrote: [..] > Even when succeeding in compiling Wx on MacOSX, padre will *not* run. I > asked a friend to run "perl -V |grep threads" and "perl -Mthreads -e1" > on his MacOsX 10.6.6 installation and this is what he got: > > $ perl -V |grep threads > usethreads=undef use5005threads=undef useithreads=undef > usemultiplicity=undef > > $ perl -Mthreads -e 1 > This Perl not built to support threads > Compilation failed in require. > BEGIN failed--compilation aborted. > > As you can see, the system perl binary was not compiled with threading > support (needed by Padre). You will need to follow Shlomi's advise and > use an alternative Perl (self-compiled or from ports). > > Claudio _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
