So the problem is: is it needed at all?
> LG> Another point: configure.in uses "uname" to build the name of
> LG> the subdirectory of library that contains system specific
> LG> code. This is bad, since "uname" is not available
> LG> everywhere... This is the result on NeXTSTEP:
>
> Saw the same thing when I built the quad-fat, but I just ignored it
> and all seemed to work okay.
Yes, at least since we won't create/use shared libs on NeXTSTEP ;-)
In that direction I think it would be better using a more portable
way to recognize the OS name.
bye, lele.