Started by t-rexky, December 01, 2011, 10:31:06 PM
Quote from: "iDork"Please, excuse my ignorance on the matter, but is't it easier to build a cross-compiler that targets NeXTSTEP, rather than porting GCC and all dependencies. OK, maybe not easier, but definitely less time consuming.
Quote from: "t-rexky"I reconfigured the 3.2.3 build to only supply the C compiler, and I have to report that it works fine. In fact, I used it to build a number of other GNU tools and everything seems to be OK. The one thing that I have not yet tested is full support for the (broken) POSIX...
Quote from: "linmag7"This is really great news! a more recent compiler is really the key to building a bunch of new stuff. How m68k specific is this? is it a big step to get gcc-3.2.3 working for sparc/intel as well?A while back I worked on some ports of unix software to NextSTEP I put together a "libnext" with a collection of posix functions that were missing or faulty in nextstep, it wasn't much but fixed a lot of unresolved symbols when linking standard unix utilities...
Quote... maybe also a posix-threads library would be required for some compiles.
Quote from: "linmag7"Hi,Sorry for the delay i my response I've been less active for the past year or so, maybe its time to check in more often.A more recent glibc along with a recent gcc would really bring nextstep into 2012 in a big way, maybe also a posix-threads library would be required for some compiles.I agree the porting glibc to NeXT is no small task, not only does it requires some true skill but also a significant amount of time.my "next library" contains an implementation of a very small subset of the common c-library functions that are either missing or broken in NeXTSTEP. The following functions are implemented: [...]I'd be happy to make the library available to you if you'd like to use it or add more implementations to it.
Quote from: "linmag7"I'm not sure what the best approach to header files is. When I was porting stuff to nextstep I collected missing header stuff into new headers that I included into whatever source-files needed them. This was in order to leave the original nextstep header files intact.Maybe a different approach would be to create a patch-kit that could be applied to original nexstep headerfiles in order to add/fix missing stuff to those files?