Re: Installing GNUstep using MacPorts

[Kevin Ingwersen]

I first make’d the gnustep-make stuff and prefixed it into /opt/GNUstep
Then I went and configured gnustep-base the same way and prefixed it into 
/opt/GNUstep too. Then I just ran make.
libobjc does not want to compile at all, because i am getting a lot of errors 
with the assembly code (something like „.type“ being undefined/unknown etc. 
Might be a clang issue).
The file that’s being compiled is:

Making all for subproject Additions...
 Compiling file GSObjCRuntime.m …

According to the README in ‚macosx/README‘, the Additions project is actually 
not volunteered and was last used in 10.3…and ./configure —help gives me no 
option to skip it either.

Kind regards.
Am 02.12.2013 um 08:55 schrieb Ryan Schmidt <ryandesign@macports.org>:

> 
> On Dec 2, 2013, at 01:10, Kevin Ingwersen wrote:
> 
>> Well, I may actually start to volunteer for gnustep-macports. I just need to 
>> finally get a working compiler that can compile gnustep correctly. The only 
>> and current issue are some basic includes and weird declaration errors like:
>> 
>> /System/Library/Frameworks/Security.framework/Headers/SecItem.h:410:42: 
>> error: expected ';' after top level declarator
>> extern const CFTypeRef kSecAttrAccessible
>>                                        ^
>> /System/Library/Frameworks/Security.framework/Headers/SecItem.h:414:43: 
>> error: expected ';' after top level declarator
>> extern const CFTypeRef kSecAttrAccessGroup
>>                                         ^
>> /System/Library/Frameworks/Security.framework/Headers/SecItem.h:416:46: 
>> error: expected ';' after top level declarator
>> extern const CFTypeRef kSecAttrSynchronizable
>>                                            ^
>> /System/Library/Frameworks/Security.framework/Headers/SecItem.h:418:49: 
>> error: expected ';' after top level declarator
>> extern const CFTypeRef kSecAttrSynchronizableAny
>> (…)
>> 
>> But, if i get aorund this, there shouldnt be a big issue porting my current 
>> way to macports! :)
> 
> How did you get to this point? What steps would I need to take to reproduce 
> this issue on my own system? It’s hard to know what’s wrong, based on just 
> the information above. For example, I see that the Security framework is 
> being used (presumably this was requested by passing the flag “-framework 
> Security” to the compiler), but you didn’t show what file was being compiled 
> at the time.
>