Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!ames!vsi1!daver!bungi.com!news From: jkh@meepmeep.pcs.com (Jordan K. Hubbard) Newsgroups: comp.sys.nsc.32k Subject: varargs on Minix 1.5/1.3 hybrid seem to be gefrotzen. Message-ID: Date: 27 Feb 91 04:31:07 GMT Sender: news@daver.bungi.com Lines: 17 Approved: news@daver.bungi.com In porting the GNU file utils (mv, cp, chmod, ...), I noticed that the common error() routine spat out bogus error messages. Tracing it a little, it seems that vfprintf() is not handling its args properly. I haven't looked at it enough to fix it yet, but has anyone else had such problems? vfprintf() handling in the minix libraries could be better in any case, by default it looks like the 1.3 hybrid minix wants to stick it in libflt.a which would be sort-of-ok but libc's vsprintf() routine depends on it, leading me to believe that it used to be part of libc and was erroneously separated out. My solution was to copy it back in and compile it with the floating point flags turned off (the one in libflt retains the floating point behaviour). Jordan