Re: [Fink-devel] python25-socket-ssl and system libraries
On Sun, Feb 10, 2008 at 01:56:26AM +0100, Aleix Conchillo Flaqu? wrote: On Feb 9, 2008, at 8:43 PM, Daniel Macks wrote: Interestingly, neither the main python25 packages nor the socket module packages actually appear to link libexpat at all Well, I said the expat library as another example, that is, libraries that link with fink's expat instead of apple's expat. and it was easy enough to have the socket lib link against apple's openssl (which solves a licensing issue), so now fink's python25 package does it all and the external socket packages are empty dummies. Yes, in fact, this is what I did in my local version. I guess this could be changed and commited. It has been:) dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
[Fink-devel] Fwd: Re: An option to build universal binaries ?
-- Forwarded Message -- Subject: Re: [Fink-devel] An option to build universal binaries ? Date: Saturday 09 February 2008 From: DJamé Seddah [EMAIL PROTECTED] To: Alexander K. Hansen [EMAIL PROTECTED] Le 9 févr. 08 à 20:19, Alexander K. Hansen a écrit : On Saturday 09 February 2008 01:15:11 pm DJamé Seddah wrote: Hi, I would like to know if it would be possible to use fink to build a whole universal binary hierarchy under /sw ? the idea is to have a shared directory using nfs for ppc and x86 so if it exists an option to add to fink.conf, that would be nice to let me know Regards, Djamé It's not supported, and It's not likely ever to happen. To do a cross-compile for PowerPC on an Intel box would require removing _every_ Intel binary library from the Fink tree, and then rebuilding every package for PowerPC. Not to mention that the low level binary package handler, dpkg, is only capable of coping with a single architecture. Hi, I was thinking about setting CFLAGS AND LDFLAGS during the first fink bootstrap something like that fink selfupdate CFLAGS=-arc i386 -arch ppc and then hopping that all the makefile will get the new propagated CFLAGS and maybe modify the apt.conf to take that into account. I guess that the bad point will be when apt will generate the .deb it's a pity it doesn't cope with flat files. Thanks anyway for your answer Djamé --- -- Alexander K. Hansen akh AT finkproject DOT org Fink User Liaison and Documenter - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
[Fink-devel] docs
Having just dealt with somebody who read one of our docs that mentioned a package that hasn't existed since 2002 (or so), I'm kind of thinking an overhaul is in order. We've got a lot of vestigial cruft that has accrued over the years, and it's going to take some effort to track all of that down. I don't have a lot of time right now to make an intensive effort to do this myself, but I can hit pages as I get a chance. -- Alexander K. Hansen akh AT finkproject DOT org Fink User Liaison and Documenter - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
Re: [Fink-devel] -py24 variant for appscript
On Sunday 10 February 2008 02:41:48 pm Tristan Thiede wrote: I didn't include a -py24 variant because appscript doesn't work in python 2.4 under Leopard (fails with a runtime error). It's an upstream problem which they don't really care about since few people are likely to use python 2.4 under Leopard anyway. What we could do is make it so that a -py24 variant is available in Tiger but not in Leopard. I'm just not really comfortable with putting a broken package in the tree. Sorry I didn't make that clear in the submission comment! Tristan Thiede On Feb 9, 2008, at 13:58 , Alexander K. Hansen wrote: I've gone ahead and added a -py24 variant for appscript, since we still support -py24 on Tiger and Leopard. -- OK--one of the core developers suggested adding the -py24 variant, and I didn't know of a good reason at the time not to. -- Alexander K. Hansen akh AT finkproject DOT org Fink User Liaison and Documenter - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
Re: [Fink-devel] An option to build universal binaries ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander K. Hansen wrote: | fink selfupdate CFLAGS=-arc i386 -arch ppc | | and then hopping that all the makefile will get the new propagated | CFLAGS and maybe modify the apt.conf to take that into account. That will work for basically nothing in Fink. If it were that easy, we would already have done it. :) Autotools-based packages (probably 80% of the stuff in fink) will need at least --disable-dependency-tracking passed on the configure line as well as the -arch stuff in your flags. That will work for maybe 60-80% of autotools (that's 60-80% of 80%). And, only if you're on Intel, because on PowerPC you'll also need - -isysroot /Developer/SDKs/MacOSX10.4u.sdk which also adds flags which piss off some custom-written autotools stuff. Probably another 20-30% of *those* (including most network tools) do endianness checks at configure time, which means that it will build on all platforms, but create broken binaries on whichever platform you're not building on. So that's 70-80% working in the 60-80% of 80%. ;) Non-autotools-based packages are completely a crapshoot; most of the manual build system stuff that isn't autotools does not care what's in CFLAGS, or treats it differently. Yes, it is theoretically possible to get everything in Fink to build universal. In practice, it would require tons and tons of hand-hacking by maintainers, as well as infrastructural support in Fink, and neither side has the manpower for us to reasonably expect it to happen. Not to burst your bubble, but I've thought about this a lot (and built probably 40 individual KDE dependencies as universal packages manually) and it's just not feasible. - -- Benjamin Reed a.k.a. Ranger Rick Fink, KDE, and Mac OS X development http://www.racoonfink.com/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHr7nXUu+jZtP2Zf4RAmM8AJ0fwbiFV2ywb0uXwGo0OQDcKkdHjgCdGXQA lBIqEiMiPhR4Ct+wo2TATMg= =VAtN -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
