-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 How about if I implement the following then:
change the extant gcc45-10.4.info to look for gcc45-10.4.patch copy the extant gcc45.patch to gcc45-10.4.patch commit the 10.5 and 10.6-relevant files (gcc45.patch, gcc45.info, gcc45-x86_64.info) from the tracker ? That way we will have the updated gcc45 in 10.5 and 10.6, with the option to update it in 10.4. On 8/11/10 9:19 PM, David R. Morrison wrote: > If I could make a small suggestion on this thread. Fink's support for 10.4 > will end fairly soon, so it would not be such a bad thing if gcc 4.5.1 only > runs on 10.5 and 10.6. > > -- Dave > > > On Aug 11, 2010, at 5:36 PM, Jack Howarth wrote: > >> On Wed, Aug 11, 2010 at 07:48:45PM -0400, Alexander Hansen wrote: > On 8/11/10 4:56 PM, Jack Fink wrote: >>>>> Salut Jack, >>>>> the problem on 10.4-i386 (with 2 dwarves) is that the build tries to >>>>> build something as x86_64, which can't succeed with a 32bit libc.dylib. >>>>> Cheers (and thanks for putting that much brain/time/effort into gcc!) >>>>> >>>>> -jack >>>>> >>> >>> Jack, >>> Is this with Xcode 2.5? I'm surprised I didn't hear about this >>> problem before although I do see... >>> >>> Historical Footnote: Compiling 64-Bit Command-Line Code for Mac OS X v10.4 >>> >>> Mac OS X v10.4 supports some 64-bit executables. However, Mac OS X v10.4 >>> does not include a full 64-bit stack; Mac OS X v10.4 contains only >>> libSystem and the Accelerate framework in 64-bit versions. In addition, Mac >>> OS X 10.4 includes neither the Objective-C runtime nor a 64-bit >>> Objective-C-capable version of dyld. Because of these differences, if you >>> try to execute a 64-bit executable in 10.4 that depends on these >>> 10.5-specific features, it would crash. >>> >>> To prevent new 64-bit executables from running as 64-bit on version 10.4, >>> Apple changed the CPU subtype for 64-bit executables that depend on >>> high-level frameworks. >>> >>> If you need to compile an executable as 64-bit for Mac OS X v10.4, you must >>> select the 10.4 deployment target when building 64-bit executables and >>> separate your code into a 32-bit front-end (GUI) portion and a 64-bit >>> back-end (processing) portion. >>> >>> at >>> http://developer.apple.com/mac/library/documentation/Darwin/Conceptual/64bitPorting/building/building.html. >>> Did the any of the previous gcc4x packages build the x86_64 multilib under >>> 10.4? >>> Jack >>> > > And you got an error with the prior iteration (no dwarf2) ? > >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> Fink-devel mailing list >> Fink-devel@lists.sourceforge.net >> http://news.gmane.org/gmane.os.apple.fink.devel >> Subscription management: >> https://lists.sourceforge.net/lists/listinfo/fink-devel - -- Alexander Hansen Fink User Liaison -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxlsb4ACgkQB8UpO3rKjQ9AJgCeOUNa981ur8/aA8geTh7q9sRy a7MAnA054dX9k1lbtQA3YQQ3CwlNBl2K =ZFu3 -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
