Garrett D'Amore wrote: > Joerg Schilling wrote: > > "Garrett D'Amore" <garrett_damore at tadpole.com> wrote: [snip] > However, those tests will work, and if you're happy with the limitations > of them, then go ahead. Code integrating in ON should not need to do > this though, especially since it creates a new opportunity for breakage > when a new port is added.
Uhm... a new port would just grab usr/src/lib/libshell/misc/buildksh93.ksh, build&&test ksh93 that way and then move the generated headers over into the OS/Net tree. It is not intended to port the generated headers from one architecture (e.g. SPARC) to another one (e.g. PowerPC). Rememeber we do not want to fork() the ksh93 sources and that includes all porting work. Porting AST/ksh93 to Solaris/PPC should be done on the native AST codebase first (which allows better testing), tested there and then pulled-over into OS/Net. ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
