[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Makefile packages do not work oon OSX

From: Lars Sonchocky-Helldorf
Subject: Re: Makefile packages do not work oon OSX
Date: Tue, 15 Jul 2003 18:58:29 +0200

On 15.07.2003 18:13:26 David Ayers wrote:
>Enrico Sersale wrote:
>> This is intended to be a reply also to Nicola, David and all the
>> people that has answered :-)
>> I mean GNUstep-base, not base-extensions.
>Now we're getting complicated... What is meant by base-extensions?

my bad. I meant baseadd.

>supports an option explicitly set though:
>make add=yes
>that builds the parts in
>against a "Foundation" implementation other than -base.
>On the otherhand there is
>which has nothing to do with the previous thread except that the term
>"extensions" has been confusingly introduced.
>But if I understand you corrctly, you want to build -base on OS X.  You
>do not want to use Apple's Foundation (or AppKit)
>then please do:
>make distclean
>in gnustep/core/base and gnustep/core/make
>Now you must decide on an ObjC Runime library to use. Apple's or GNU's.
>Lars said that -base has problems with Apple's Runtime.  It would be
>nice if we hand some more specific details, as the last time we
>discussed it, it ended in "don't send messages in +initialize with
>Apple's runtime" but this is a) not an option and b) was also reported

I could not prove this, it was just my hypothesis on what the stacktrace 
said. The other hypothesis here (Adam) is that there might be memory 
problem. Hence I tried to build a GNUstep base with MallocDebug. But I 
never got around to find the appropriate place in the GNUstep-make innards 
to place the -lMallocDebug flag. All the stuff went over my head and I 
dropped out since I had no Idea how to tackle this. The last state is 
visible here: 
with the compile and gdb output in the end. Some more discussion on that 
topic is here: 

or just search for "Darwin" in 
(Entries from 07/2002 and earlier)

And before I forget it: NSZombie also played an obscure role in this 
bizarre game...

>to work.  So eventhough I can imagine that there are still issues with
>Apple's Runtime and -base, I have no concrete idea what they are.  (If
>no one can investigate this, I might take the offer ot ssh to someone's
>OS X and see what I can find out.)
>To avoid problems, I suggest you use the GNU Runtime.  Yet this is
>reportedly not installed by default on OS X.  Therefor you might have to
>intall the FSF gcc.
>Then in: gnustep/core/make
>./configure --with-library-combo=gnu-gnu-gnu
>build & install make
>source GNUstep.sh
>in: gnustep/core/base
>sudo make install
>> Adding #include "gnsutep/base/GSObjCRuntime.h"
>> now I get this: (warnings removed)
>> /usr/bin/gcc GSLocale.m -c \
>>      -MMD -MP -DGNUSTEP_INSTALL_PREFIX=/usr/GNUstep/System
>> -DGNUSTEP_LOCAL_ROOT=/usr/GNUstep/Local
>> -DGNUSTEP_TARGET_CPU=\"powerpc\" -DGNUSTEP_TARGET_OS=\"darwin6\"
>> -DLIBRARY_COMBO=\"apple-apple-apple\" -Wall -Wcast-align
>> -framework Foundation -framework AppKit -traditional-cpp -dynamic
>> -fno-common -DGSWARN -DGSDIAGNOSE -O2 -fno-strict-aliasing
>> -fnext-runtime -I../Headers/gnustep -I../Headers -I./. -I. \
>>       -o shared_obj/GSLocale.o
>Now you're compiling code for -base using apple-apple-apple.  This is
>definately wrong and maybe we should add something to -make or -base to
>disallow this.  You can't build a "Foundation" compatible library using
>a "Foundation" library.  Please reconfigure.
>Discuss-gnustep mailing list

greetings, Lars

reply via email to

[Prev in Thread] Current Thread [Next in Thread]