I am keen to come up with a low maintenance framework for tracking these optioned arguments so that adding new ones is a snap. Searching for the right case...esac and adding a new block is a PITA.
So you're saying we should not revert the patch? I think that's the most maintainable solution. Libtool has lived without the patch for this long. Adding a case statement to pass through known options will solve the problem of passing through 64-bit flags which should get us better behavior than before. Nirvana, passing through all unknown options, seems impossible.
I recommend that the patch be reverted. A generic mechanism can be added to specify which options should be passed, and how many arguments the option requires. This may be more difficult to do efficiently from a shell script than when using a compiled language.
In order to ease maintenance, part of the libtool script can be automatically generated from an options configuration file.
Bob ====================================== Bob Friesenhahn [EMAIL PROTECTED] http://www.simplesystems.org/users/bfriesen
_______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/libtool
