Es schrieb Kevin Ryde:
> > But this is not
> > actually the Right Thing, dlltool should offer an option about it,
> > and since dlltool is preinstalled, we do not need to compile a
> > tool on the fly.
>
> Yes, that'd make sense. I suppose though that features added to
> dlltool now wouldn't act
Guido Draheim <[EMAIL PROTECTED]> writes:
>
> http://ac-archive.sf.net/Installed_Packages/patch_libtool_to_add_host_cc.html
Thanks, I missed that one, I ended up patching libtool.m4.
> But this is not
> actually the Right Thing, dlltool should offer an option about it,
> and since dlltool is pre
CVS libtool ignores the --silent option when linking programs, and
when installing modules:
/bin/sh ../libtool --silent --mode=link gcc -g -O2 -mcpu=ultrasparc
-Wall -Wall -L/usr/local/lib -L/usr/local/lib -R/usr/local/lib
-L/usr/local/lib -L/usr/local/lib -L/usr/openwin/lib
-R/usr/openwin/lib
It is very stupid for libtool.m4 to break other Linux platforms just
because Linux/ARM is different. Here is a patch for Linux/mips.
However, the correct fix should be
case $host_cpu in
arm*)
# Handle ARM differently.
;;
*)
lt_cv_d
Something like this, perhaps?
2001-10-21 Tim Van Holder <[EMAIL PROTECTED]>
* doc/autoconf.texi: Mention the issue of bash 2.05's
`set' builtin.
Index: doc/autoconf.texi
===
RCS file: /cvs/autoconf/doc/autoconf.te
