Re: Partial linking of .lo objects, rev 2 (CVS HEAD)

[Eric Blake]

Hi Marc,

> 
> Thanks for your analysis, it opens my eyes on a lot of things I did not
> even knew should be considered.

Ralf has more libtool experience than I, but I can still add to the
conversation.

> Short of reading the POSIX spec to find what is portable in theory, and
> the bug reports all other the Internet
> to find what is portable in practice, can you or anyone recommend :
> - a good shell scripting cookbook somewhere (practical, not 200 pages
> dedicated to one specific version of a shell anyway),

> - some tools to inspect the code for portability issues for shell
> scripts (like autoscan for C/C++ code),

Except for the above wish (which I would like, too),...

> - a web museum of coding horrors and war stories on broken platforms
> (a.k.a, how to not code and why)
> 
> Would be greatly appreciated.

the autoconf manual is a GREAT thing for the remaining bullets.  Since
autoconf prides itself on producing portable shell configure scripts, it's
documentation has a wonderful chapter on shell portability pitfalls, and it
is constantly being improved.  Unfortunately, there is no web-based manual
for 2.59, but autoconf 2.59c is currently being tested for an eventual
release of autoconf 2.60, where the manual will again be online
in html format.

-- 
Eric Blake