site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On 23 Sep 2005, at 23:43, Stan Shebs wrote: After some digging around I think I have found some answers. I hit on a few things quite by accident. My patch will compile if I build the Apple way as root : % mkdir -p build/obj build/dst build/sym # gnumake install RC_OS=macos RC_ARCHS=ppc TARGETS=ppc \ SRCROOT=`pwd` OBJROOT=`pwd`/build/obj \ DSTROOT=`pwd`/build/dst SYMROOT=`pwd`/build/sym # ditto build/dst / when the build broke with : ld: Undefined symbols: ___guard ___stack_smash_handler So as you can see it's a bit of a chicken and egg situation. This opens up a new problem of how I am going to compile 3.5 and 4.0. S a m _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I'm somewhat out of touch with the specifics of your issue (my first inclination would be to double check system vs compiler versions, not all combos work), but I thought I'd explain the theory; Apple GCC has a special build process because we want to support multiple architectures and fat^Wuniversal binaries. The "FSF way" only ever builds one compiler, while the "Apple way" builds n-squared compilers for n architectures, with appropriate hosts and targets, bootstrapping the native versions, and lipo-ing together the target libraries. The Apple way also takes care of some smaller issues, such as some pathname trickery. it was a bit of a red herring, there was a problem with a file permission previous to this. Now the last section where I said that it builds the back-end properly ( i.e. cc1 etc. ) well the reason for that is that you need a compiler of the same version installed ( in this case 3.3 ) during Apple's build process it copies the front-end ( e.g. gcc-3.3 ) and a number of other files from the currently installed version. My proposed solution is to build with an old version of 3.3 that I can patch and build the fsf way ( because 1809 b0rks, ) then install it so that I can build a more recent patched version. I feel that I should explain that my goal is to build Darwin with protection added where possible, thus I have been working on compiler patches, lib patches and kernel patches and these are at various stages. I am also reworking libssp. I am currently building so if anyone is interested I'll let you know how it goes. My thanks go to Shantonu Sen and Kevin Van Vechten for providing the DarwinBuild environment. This email sent to site_archiver@lists.apple.com