discuss-gnustep
[Top][All Lists]
Advanced

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

Re: Installing GNUstep using MacPorts


From: Dr. H. Nikolaus Schaller
Subject: Re: Installing GNUstep using MacPorts
Date: Mon, 2 Dec 2013 08:45:27 +0100

Am 02.12.2013 um 08:10 schrieb Kevin Ingwersen:

> Hey.
> 
> 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
> (…)

This looks to me as if the macports compiler is referencing the OS X header 
files in /System/Library. So you might have to work with -I or -nostdinc etc.


> But, if i get aorund this, there shouldnt be a big issue porting my current 
> way to macports! :)
> 
> Kind regards, Ingwie
> Am 02.12.2013 um 01:41 schrieb Ryan Schmidt <ryandesign@macports.org>:
> 
>> On Dec 1, 2013, at 14:32, Lars Sonchocky-Helldorf 
>> <lars.sonchocky-helldorf@hamburg.de> wrote:
>> 
>>> Did you try mailing to macports-users 
>>> <macports-users@lists.macosforge.org>? This list is somewhat active, I have 
>>> no idea whether someone responds to those addresses inside the portfiles.
>>> 
>>> cheers,
>>> 
>>>     Lars
>>> 
>>> Am 01.12.2013 um 18:29 schrieb Adam Fedor:
>>> 
>>>> I would not use macports. The gnustep package on on macports is really 
>>>> really old - 1.19 was released over 4 years ago. Plus they pretty much 
>>>> ignore any patches or bug reports you send in.
>> 
>> If by “they” you mean the MacPorts community, we certainly do respond to 
>> patches and bug reports. However we are a volunteer project. We have 
>> hundreds of contributors, who have volunteered to maintain various packages. 
>> Unfortunately, nobody has volunteered to maintain the gnustep packages in 
>> MacPorts, therefore bugs filed against those packages might not get resolved.
>> 
>> What we need is for someone who is interested in gnustep and understands how 
>> it should work to volunteer to maintain and update these packages and 
>> address the outstanding tickets.
>> 
>> 
>>>> Again, I would not recommend installing GNUstep on Mac OSX, but if you 
>>>> want to try you could look at this:
>>>> 
>>>> http://wiki.gnustep.org/index.php/Platform:BSD#Full_Install
>>>> 
>>>> Although even these instructions are old and probably out of date. You are 
>>>> on your own if you want to do this though. Trying to install GNUstep on 
>>>> OSX has turned many a programmer prematurely grey. ;-)
>> 
>> And this may be a reason why nobody has yet figured out how to do it and 
>> translate that knowledge into a working MacPorts porfile.
>> 
>> 
>> _______________________________________________
>> Discuss-gnustep mailing list
>> Discuss-gnustep@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnustep
> 
> 
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnustep




reply via email to

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