Is there a good way to turn off the usage message that gets displayed
every time a module is installed by libtool? This usage message is
useful for normal shared libraries, but is not useful for loadable
modules.
Thanks,
Bob
==
Bob Friesenhahn
[EMAIL PROTECTE
Hello,
We're currently using GNU libtool v1.4 on Solaris 2.6, but are preparing to
upgrade to Solaris 8. Can you please tell me if you provide a 32-bit and
64-bit version of libtool and for how long you plan on supporting them?
Thank you,
Maria E. Torok
NASA - CLCS COTS Software Coordinator
Lock
On Wed, 10 Oct 2001, Torok-1, Maria wrote:
> We're currently using GNU libtool v1.4 on Solaris 2.6, but are preparing to
> upgrade to Solaris 8. Can you please tell me if you provide a 32-bit and
> 64-bit version of libtool and for how long you plan on supporting them?
Libtool itself is a scrip
Robert Boehne <[EMAIL PROTECTED]> writes:
>
> Could you try changing AR_FLAGS in your libtool script
> to see if that works?
AR_FLAGS=cq seems to work on all the systems I've tried, and fixes the
ultrix problem. As long as ranlib does its job then I imagine it'd
have to work everywhere.
___
Kevin Ryde wrote:
>
> Robert Boehne <[EMAIL PROTECTED]> writes:
> >
> > Could you try changing AR_FLAGS in your libtool script
> > to see if that works?
>
> AR_FLAGS=cq seems to work on all the systems I've tried, and fixes the
> ultrix problem. As long as ranlib does its job then I imagine it'
Robert Boehne <[EMAIL PROTECTED]> writes:
>
> What's the Ultrix problem?
It was vax-dec-ultrix4.5 which had the small command line limit and
suffered in the piecewise link.
___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinf
Solaris 2.7 and HP-UX 10 don't think much of
rm -f ""
it provokes a bit of an error
rm: cannot remove `.' or `..'
This arises from libtool when compiling, I think due to $output_obj
being empty when -c -o works.
This is no more than cosmetic, but perhaps cases where that might
On Thu, Oct 11, 2001 at 09:24:15AM +1000, Kevin Ryde wrote:
> Solaris 2.7 and HP-UX 10 don't think much of
>
> rm -f ""
>
> it provokes a bit of an error
>
> rm: cannot remove `.' or `..'
>
> This arises from libtool when compiling, I think due to $output_obj
> being empty when
Olly Betts <[EMAIL PROTECTED]> writes:
>
> ## We must test each macro because it might be empty, and an empty "rm
> ## -rf" command looks disturbing. Also, the Solaris 2.4 "rm" will
> ## return an error if there are no arguments other than "-f".
Soor, I pruned too much, the libtool case is inst
On Thu, Oct 11, 2001 at 09:57:18AM +1000, Kevin Ryde wrote:
> Soor, I pruned too much, the libtool case is instead something like
>
> rm -f "foo.o" ""
Ah right.
> It's the empty argument which is the problem, not no arguments as
> such.
>
> I guess the quotes support spaces in filename
"Torok-1, Maria" wrote:
>
> Anything you could tell me regarding 32-bit and 64-bit versions of automake,
> make, and m4 would also be appreciated!
> [..]
> > E-mail: [EMAIL PROTECTED]
"Torok-1, Maria" wrote:
> We're currently using GNU libtool v1.4 on Solaris 2.6,
... before you flood the mai
11 matches
Mail list logo