phil@cs.wwu.edu (Phil Nelson) (02/26/91)
>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. Yup, vfprintf is broken. (As reported before.) I'll take the blame. I will have some diffs soon. What I did was to change stdio.h to have the right parameters and started with a fresh copy of libflt (at least the *print* files. Some changes are required to get all of them compiled, but the "original version" is a good starting point. I have several other fixes that I plan to distribute soon. If you know of any other problems not reported please let me know. --Phil
jkh@meepmeep.pcs.com (Jordan K. Hubbard) (02/27/91)
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