[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ 100207 ] need_lib_prefix=no for osf*

From: nobody
Subject: [ 100207 ] need_lib_prefix=no for osf*
Date: Mon, 19 Nov 2001 16:52:10 -0500

Support Request #100207, was updated on 2001-Nov-19 18:18
You can respond by visiting:

Category: None
Status: Open
Priority: 5
Summary: need_lib_prefix=no for osf*

By: enchanter
Date: 2001-Nov-19 21:52

Logged In: YES 
Browser: Mozilla/4.78 [en] (X11; U; OSF1 V5.1 alpha)


I'm not sure why I received email about this, but I'm
guessing because
I submitted a nearly-identical patch to the libtool-patches
mailing list
in July, and you found a reference to that?

Your patch looks fine (it's identical to the one I've been
using for
several months on Tru64 5.1, with projects like gnumeric). 
I'm not sure
if that patch was ever applied to the HEAD branch of
libtool, but I guess
I'm hopeful either my patch or yours would make it into
libtool at some

Until it does, my solution has been to have a copy of
libtool with this
and other patchs applied on my Tru64 development box, and
then use

        rm -f libtool ltconfig aclocal.m4
        libtoolize --copy --force

for any package that ships older/less-functional libtool

You're right that the dependencies between
are a pain in the butt, but in my experience most of the
problems relate
to macros that autoconf will no longer accept.  libtool and
are generally not the problem.


By: bs
Date: 2001-Nov-19 18:18

Logged In: NO 
Browser: Mozilla/4.0 (compatible; MSIE 5.12; Mac_PowerPC)

I've just submitted a patch for libtool.m4 setting 
need_lib_prefix=no for Tru64 aka OSF/1. This is 
the needed setting for building modules under 
Tru64. May I ask you please for a comment?

The issue with the "lib" prefix arose when 
compiling Netatalk from the CVS (see http:// As a 
workaround, a patched copy of libtool.m4 is 
included as acinclude.m4 in the Netatalk CVS, 
which unfortunately causes problems with libtool 
and/or aclocal on other platforms, presumably due 
to nonmatching versions.

Kind regards,


You can respond by visiting:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]