Eric Blake wrote: > [Please keep bug-gnulib in the loop, since this problem affects multiple > gnulib clients, and since Bruno's code is more impacted than mine by > knowing the innards of FILE]
Hi Eric, Thanks for the forward. The attached <stdio.h> is identified (by Google codesearch) as coming from Innotek's libc port. It was announced in [1] and [2]. Now their site suffers from deconstruction, especially after they have been bought by Sun. The available downloads are [3]..[9]. The libc appears to be a mix between the EMX libc, the FreeBSD libc, and GNU libc. The stdio is from EMX libc. Then there is also (probably a newer development) [10] and [11]. Elbert, You have not said whether your system uses [3]..[9] or [10]..[11]. If you want your system to be supported, we need from you the set of predefined macros from gcc. The output of this command sequence: $ touch empty.c $ gcc -E -dM empty.c Bruno [1] http://www.os2.cz/news1800.html [2] http://www.skins.cz/arr2004/zpen8377.shtml [3] http://download.innotek.de/gccos2/3.2.2-Beta4/gcc-3.2.2-beta4csd1.zip [4] http://download.innotek.de/gccos2/3.2.2-Beta4/gcc-3.2.2-beta4-src-emx.zip [5] http://download.innotek.de/gccos2/runtime/libc01.zip [6] http://download.innotek.de/gccos2/runtime/libc02.zip [7] http://download.innotek.de/gccos2/runtime/libc03.zip [8] http://download.innotek.de/gccos2/runtime/libc04.zip [9] http://download.innotek.de/gccos2/runtime/libc04fix1.zip [10] http://svn.netlabs.org/libc/ [11] ftp://ftp.netlabs.org/pub/gcc/
