But I see that Alden is still using 10.4, ouch, that's old man.
Perl (and python and ruby) are fixed in 10.6 to support all three main architectures.
In general though I would in this day and time stay away from autotools as far as I can as they are in general the most horrendous, ugly, complicated and SLOW build hack in existence. It did serve its purpose in the past, but is not adequate anymore. For a fairly straight forward project like xrootd I would move the build system to cmake, or keep the by now fine tuned gmake file build system.
Cheers, Fons.
On 20/09/10 8:30, Derek Feichtinger wrote:Hi, LukaszI am the original author of the autotools build.Most of this work I had done in 2005, and for some years I kept all of itworking on x86 Linux, Solaris, and also Mac. I can no longer invest thisamount of time in trying to follow all the different OSs, and so I am gladfor anybody submitting patches or improving the build for their systems.Macs proved to be particularly irksome, since compiler behavior changedsignificantly based on environment variable setting (...DEPLOYMENT_TARGET,if I remember), and later on the issue of allowing multi architecturebinaries. The correct way for linking against PERL libraries, was to querythe local perl installation for the correct compilation and linker flags.The current solution in the autotools script is only a workaround whichtries to get rid of the correct extra architectures... but this could(should) be done better.The distinction between shared libs and modules was a problem to which Ipointed early on. But this used to be a deeper problem in the xrootd buildorganization, where sometimes deliverables were used for both. Libtooloffers a "-module" switch which correctly should build a module also onMacs. Maybe it is used once too much... would need to investigate.Cheers,Derek-----Original Message-----From: [log in to unmask] on behalf of Lukasz JanystSent: Sat 9/18/2010 1:25 PMTo: Alden StradlingCc: [log in to unmask]Subject: Re: Dutifully reporting...Yes, indeed. The autotools build is broken on 64 bits Macs because,contrary to the assumption of the autoconf script, the compilingtoolchain supports three architectures there and not just two. You canworkaround this problem by disabling the perl interface if you don'tneed it (--disable-perlint parameter of the configure script) or byusing the classical build. There are also two other problems with theautotools stuff. The first one is the missing libtoolize binary calledfrom the bootstrap.sh script (on Mac it's called glibtoolize). Also,the autotools build tries to link the xrootd binary to a dynamicallyloadable module which results with a linking error. On Mac there is aclear distinction between loadable modules and shared libraries whichis not the case for the ELF systems where both are the same and thisis why this problems has been introduced and not spotted earlier.Anyways, thanks for reporting. I will be fixing that on Monday.Cheers,LukaszOn Sat, Sep 18, 2010 at 7:22 AM, Alden Stradling<[log in to unmask]> wrote:> as the config file requested -->> ./getAutotools.sh> ./getAutotools.sh -i /opt/xrootd> ./bootstrap.sh> ./configure -h> ./configure --prefix=/opt/xrootd --enable-pwd --enable-posix--enable-mon --enable-apps --enable-doc --enable--gsi>> configure: WARNING: perl says it was linked with multiple -arch flags(-arch i386 -arch ppc)! Will try to remove one> configure: WARNING: perl says it was compiled with multiple -arch flags(-arch i386 -arch ppc)! Will try to remove one> configure: error: Failed to remove extra -arch flags> LD: -arch x86_64 -arch i386> CC: -arch x86_64 -arch i386 -g -pipe -fno-common-DPERL_DARWIN -fno-strict-aliasing -I/usr/local/include-I/System/Library/Perl/5.10.0/darwin-thread-multi-2level/CORE> !!!!!! Please notify maintainers at [log in to unmask] !!!!!!>>> OS X 10.6.4, Mac Pro x86_64>
--
Org: CERN, European Laboratory for Particle Physics.
Mail: 1211 Geneve 23, Switzerland
E-Mail: [log in to unmask] Phone: +41 22 7679248
WWW: http://fons.rademakers.org Fax: +41 22 7669640