Hi,
I'm getting a warning when I try to use the glib library with libtool. The
glib library is not installed
in the normal place /usr/lib. However, I do add the -L to the place where
the library resides. The
compile and like take place, but the warning is still there. How do I
specify not to l
==> "rb" == Rob Browning <[EMAIL PROTECTED]> writes:
rb> For those stuck on this problem (and presuming we're not just
rb> using libtool improperly in Guile) I've figured out a
rb> temporary hack that will allow you to build and install
rb> packages in temporary (i.e. not --prefix
Brian May <[EMAIL PROTECTED]> writes:
> While this would work, it has the (IMHO) nasty side affect that any
> libraries previously installed in, say /usr/lib, will take priority (I
> think) over the library that was just built in the source code tree.
>
> It also means hacking around with the Mak
> "Rob" == Rob Browning <[EMAIL PROTECTED]> writes:
Rob> For those stuck on this problem (and presuming we're not just
Rob> using libtool improperly in Guile) I've figured out a
Rob> temporary hack that will allow you to build and install
Rob> packages in temporary (i.e. not -
Robert Boehne <[EMAIL PROTECTED]> writes:
> In Libtool we allow for either to be built, the latter being
> created when -Wl,-brtl is added to LDFLAGS during configure.
>From my perspective, I only get to choose we whether or not I do
run-time linking... I don't get to choose what format shared
Robert Boehne <[EMAIL PROTECTED]> writes:
> In Jeff's earier post his item #3 states he's got an unusable
> library. We don't want that, but I don't have enough information
> to determine why this is the case. Could you post enough for
> me to reproduce it?
I don't think you need to reproduce
Hello,
The native AIX way of handling shared libraries is to create
a shared object and put it in an archive. I believe that this
archive normally includes a shared object, and a static archive,
then perhaps other pairs on a multilib system
(32 bit, and 64 bit for instance).
There is also the
Marc Stephenson <[EMAIL PROTECTED]> writes:
> I do agree that it would be nice to have an option to disable the AIX
> archiving feature. If this function were to be generically described, perhaps
> it could be described as a non-library option.
>
> If you're building a shared library to be
Jeff,
You can change the behavior of libtool on AIX by adding a
a flag to the LDFLAGS variable.
Try this:
export LDFLAGS="-Wl,-brtl"
before doing configure and make.
Dan
> From: Jeff Trawick <[EMAIL PROTECTED]>
>
> Apache 2.0 uses libtool and has for some time now.
>
> On AIX we're trying
I do agree that it would be nice to have an option to disable the AIX
archiving feature. If this function were to be generically described, perhaps
it could be described as a non-library option.
If you're building a shared library to be linked against on AIX, the
normal way is to have an ar
Apache 2.0 uses libtool and has for some time now.
On AIX we're trying to use libtool 1.4.2 but are running into some
issues that perhaps someone can shed some light on.
background info:
Apache 2.0 uses code in libapr and libaprutil, implicitly loaded
with httpd.
As always, Apache 2.0 do
For those stuck on this problem (and presuming we're not just using
libtool improperly in Guile) I've figured out a temporary hack that
will allow you to build and install packages in temporary (i.e. not
--prefix) directories when you have inter-library dependencies.
I just had to add a spurious
12 matches
Mail list logo