Hello Ingo,
Ingo Weinhold [are you 'bonefish'?] wrote:
> > - send a mail to config-patches
>
> That did already happen
Ah, sorry, I wasn't aware of that. Thanks!
> > There is definitely a problem with the 'uname' command on Haiku: "uname -m"
> > should return something like "i586", not "BePC".
>
> That's more or less a BeOS inheritance. ... isn't it exactly the job of
> config.guess to convert the non-standardized uname info to a canonical system
> name?
You are right. All GNU software uses the output of config.guess, not the
"uname" command or system-call result directly. Only this can explain why
this `uname -m` = BePC value did not hurt while porting to BeOS.
> > - port gnulib,
>
> That reminds me: Is there documentation on porting gnulib (the manual seems
> to
> focus on how to use it) and a test suite?
Porting gnulib to a particular platform means:
- doing a "gnulib-tool --create-testdir --with-tests", transferring that
to the target system, and running it there, and fixing all the problems,
- testing several packages that rely on gnulib. If you got coreutils and
libiconv + gettext ported, a good portion of gnulib is being used.
- adding workaround for special deficiencies of the platform that are not
yet listed in gnulib's documentation.
Bruno
