Well, the aim was to keep things simple and just use the packages, but
along the road, discipline failed and I stared to use the ports for
whatever reason. I suppose that being your own System Administrator is
something that has to be learned too.
Does this make it useless to report 'bugs' I find
Hi Ivan,
> I am assuming emails arrived in the wrong order and this is the second one.
Yes!
> I am not sure, does Apple ship 32bit frameworks on Sierra? Have you tried
> building 64bit!
No, not yet. I retried an ancient version of GNustep make that I have in use
for many years. It had
I am assuming emails arrived in the wrong order and this is the second one.
I am not sure, does Apple ship 32bit frameworks on Sierra? Have you tried
building 64bit?
On Tue 7 Nov 2017 at 15:18, Andreas Höschler wrote:
> Hi all,
>
> I have tried to build the app manually
Hi all,I am trying to get gnustep-make-2.7.0 to work on MacOSX Sierra. After./configure makemake installand thus installing GNUstep make I try to build a minimal test appmain.m:===int main (int argc, const char **argv, char** env){ NSAutoreleasePool *pool = [[NSAutoreleasePool
Hi all,
I have tried to build the app manually on the command line, now using clang
instead of gcc and -arch i386 instead of -m32
cd /Build/Test; \
/Library/GNUstep/Makefiles/mkinstalldirs ./obj/Test.obj/
/Library/GNUstep/Makefiles/mkinstalldirs /Build/Test/Test.app/Contents/MacOS
cd
On 4 Nov 2017, at 17:07, Edwin Ancaer wrote:
>
> I installed the ports with the make install command, in a previous version.
>
>
> The update was done with the freebsd-update command. Then the problems
> started.
>
> I also reinstalled all ports with the portmaster