On Thu, 30 Mar 2006, Ralf Wildenhues wrote:
> * Tim Mooney wrote on Thu, Mar 30, 2006 at 12:19:13AM CEST:
> [...]
> > The real question is, does libtool's configure macro know whether ar is
> > needed. You seem to be indicating that it never knows (in any case)
> > whether ar is needed. Am I unde
Hi David,
* David Lee wrote on Thu, Mar 30, 2006 at 11:36:59AM CEST:
>
> For some of our options, when end-user feature "XYZ" is nice but is not
> actually essential, we now have a local (developer) convention of:
>--enable-XYZ={yes|no|try}
[ nice explanation of default and soft failure ]
G
Ralf Wildenhues writes:
> Erm. The user did not have /usr/ccs/bin in $PATH?
Right, /usr/ccs/bin was not in the PATH.
> Well yes, but sometimes ar is not needed, for example it /may/ not be
> needed when --disable-static is given.
Okay
> Naa. Kean Johnston already suggested adding /usr/ccs
On 2006-03-29, Brian Gough <[EMAIL PROTECTED]> wrote:
> checking for ar... false
> [...]
> false cru .libs/libutils.a .libs/placeholder.o
> make[2]: *** [libutils.la] Error 1
If AR defaulted to "$(MISSING) ar" if no ar was found (instead of false), then
no error is given if ar is not found b
