🚀 go-pugleaf

In article <1992Apr14.221833.13899@reed.edu> I ask:
>When I go to link my program, I get errors from the linker claiming
>that malloc() is redefined. If I don't link in my own version of
>malloc(), it links fine, albeit without the code I want.
>The NeXT OS is the first system I've gotten these errors - most OSs
>will use my malloc() and never link in the standard malloc().

Thanks to Usenet once again for quick replies.
N Tomczak-Jaegermann <ntomczak@vega.math.ualberta.ca> kindly told me:

>This issue was rehashed in this newsgroup already.  Unfortunately
>nobody seems to know a good answer and NeXT is totally numb on the
>issue.  This has to do with how shared libraries are organized.  The
>only option you really have is to rename your routines and calls to
>them.

If anyone can tell me how to get around this linker problem without
having to rename my routines, I'd really appreciate it. I hate kludges
like "#define malloc My_Malloc_I_Hope_This_Name_Isnt_In_The_Library".

One more reason why I don't want to use a NeXT box...




-- 
                __
nelson@reed.edu \/        You stupid vulgar greedy ugly American death sucker