what's the expected behaviour for configure//automake//libtool when it
cannot build a program due to conflicting options
Ie:
1) -static is specified on the link line, but libtool was configured
with --disable-static
2) --no-undefined is specificed on the link line, but libtool was
configured with --disable-shared.
I don't want to hack up an incorrect solution :] but the test suite at
the moment seems to assume that _both_ static and shared versions of
hell should build successfully every time.
Considering userland use of the tool, this is unlikely - surely the user
would _not_ configure with --disabled-shared and expect a shared version
built, and vice verca? Well, maybe the end user would, but...
Rob
_______________________________________________
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
