Hi, I am a bit appalled of having to implement all those low-level non-portable functions to get bash running.
Instead of having to port fpurge and friends to all platforms, couldn't bash be based on Posix API only, even if that might be a performance-degradation? #if defined SLOW_POSIX_BASED_IMPLEMENTATION ... #else fpurge and friends #endif Or what about writing an generic implementation of the cited functions, that would be based on Posix API only? Thanks, Juergen Bruno Haible wrote: > > Hello, > > Juergen Weber wrote: >> ERROR CCN3205 ./fpurge.c:119 "Please port gnulib fpurge.c to your >> platform! Look at the definitions of fflush, setvbuf and ungetc on your >> system, then report this to bug-gnulib." >> >> So, I am doing this ;-) >> The required definitions are linked from here: >> http://publib.boulder.ibm.com/infocenter/zos/v1r9/index.jsp?topic=/com.ibm.zos.r9.bpxbd00/edclb1803426.htm >> >> Better readable is the pdf linked there, too. > > For porting 'fpurge', you need some insight into the internals of a FILE > stream on the particular platform. > >> What would be the fpurge of z/OS ? > > The fpurge function is best ported together with a couple of other > functions. > > You find in http://www.haible.de/bruno/gnu/testdir-stdioext.tar.gz > the documentation and implementation for all systems so far (from BSD > systems to QNX), and a test suite. The documentation/specification is > in the .h files. > > To port this package: > > - Unpack the package, configure it. Try "make" and fix the problems. > - Run "make check" to see the test results. > - The recommended order of porting (from easy to harder) is: > fbufmode, fseterr, freadable, fwritable, freading, fwriting, > fpending, fpurge, freadptr, freadseek, freadahead. > > Bruno > > PS: Are you by chance the Old Wabble from Stuttgart? > > > > -- View this message in context: http://www.nabble.com/fpurge-on-z-OS-tp22905298p23078537.html Sent from the Gnulib mailing list archive at Nabble.com.
