Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ntvax!doug
From: doug@dept.csci.unt.edu (Douglas Scott)
Newsgroups: comp.sys.next
Subject: Using -bsd option while compiling C code
Summary: Not working as expected
Keywords: compiler, porting
Message-ID: <1990Jun30.005253.26019@dept.csci.unt.edu>
Date: 30 Jun 90 00:52:53 GMT
Sender: Douglas Scott
Reply-To: doug@dept.csci.unt.edu (Douglas Scott)
Distribution: usa
Organization: University of North Texas
Lines: 22

I have just loaded a large chunk of C code to my (new) NeXT, and while chewing
my fingernails I have attempted to compile it to see what all will need to be
altered to make it work.  Immediately I get errors saying that sprintf() has
been redefined, etc., which is fatal.  The manual page says that -bsd will
fix this problem, and when I studied /usr/include/stdio.h I see that the
#ifdef statements there declare sprintf(), etc., to be char* (like they are in
standard BSD Unix) when __STRICT_BSD__ is defined, which it supposedly IS when
the -bsd option is used.  The error messages did not change though, after
adding the option.  AND, when I did a preprocessor pass and looked at the 
results, the ifdefs apparently didnt work, since the sprintf() function is 
still declared as int.

I am stranded until I can fix this...I NEED sprintf() to be char* !
Am I missing something?  Has anybody else had this particular form of the
NeXT-Porting Blues?

Thanks in advance!!

-- 
___________________________________________________________________________
Douglas Scott
doug@dept.csci.unt.edu