> From: Ed Hartnett <[EMAIL PROTECTED]>
> Date: Tue, 13 May 2008 07:33:02 -0600
>
> (The .a file is always a static library, right?)
>
Not on AIX.
A .a file can be a shared library, a static library, or
some combination of the two.
Dan
___
http://lis
> From: Albert Chin <[EMAIL PROTECTED]>
>
> Any reason we don't use -bexpall to support -export-dynamic on AIX?
> >From ld(1):
> autoexp
>Automatically exports some symbols from the output module without
>having to list them in an export file. (This option does not
>expo
I've thought about working on that when I had some time.
But in the mean time, all these commands will also look at the
environment variable OBJECT_MODE. So you can just
export OBJECT_MODE=64
and go from there.
Dan
> From: Albert Chin <[EMAIL PROTECTED]>
>
> The AIX ar/nm commands, by default
That seems rather odd to me. -G is a linker flag, and no matter
which compiler you use, the AIX ld command is what is eventually invoked.
Dan
> From [EMAIL PROTECTED] Tue Dec 3 05:38:03 2002
>
> I've seen reports from Apache-2.0+AIX users that -G isn't added with
> gcc, but I see it added with
For AIX, libtool knows how to build "dynamic" libraries if
you pass in -brtl or -Wl,-brtl using LDFLAGS. It will automatically
add the -G flag when building a shared object.
Dan
> From: Gary Kumfert <[EMAIL PROTECTED]>
>
> Libtool is currently builds shared objects only and
> dumps them into
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
> From: Bob Friesenhahn <[EMAIL PROTECTED]>
>
> On Fri, 21 Sep 2001 [EMAIL PROTECTED] wrote:
>
> > On Thu, Sep 20, 2001 at 09:38:29PM -0500, Bob Friesenhahn wrote:
> > > 64-bit compilation under Solaris & Sun's compiler requires that the
> > > argument '-xarch=v9' be provided when compiling C++
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: libtool RFE
> Date: Tue, 11 Sep 2001 16:05:17 -0500
> Are you
> aware of any OS that supports 32 and 64-bit libraries in the same
> directory? I know Solaris and AIX don't do this.
The libraries that ship as part of AIX (on PowerP
> From: [EMAIL PROTECTED]
>
> > 2. On AIX systems that do not support run-time-linking, support
> > only shared libraries (so, lib.a is shared and there is
> > no lib.so).
>
> Yup... That's what it does now.
>
Oops... Sorry, I read that part wrong.
Option 2. may be what we want
> From: [EMAIL PROTECTED]
>
> On Tue, Apr 17, 2001 at 02:51:08AM +0100, Gary V. Vaughan wrote:
> > > AIX by default wants it's shared libraries called lib.a.
> > > So libltdl.a is created (as a symlink to libltdl.so.3.0.0).
> > > The Makefile then wants to create a non-shared library also called
I've been meaning to send in a patch about this:
soname_spec='${libname}${release}.so$major'
is what we finally decided to go with for AIX standard linking.
It is important to get these synched up, or we will have binary
compatibility problems.
Dan
> From [EMAIL PROTECTED] Wed Apr 25 08:13:05
Hi Albert,
It looks like AIX has been using
version_type=linux
for quite some time. So I guess we should keep using it.
Dan
> From: [EMAIL PROTECTED]
>
> On Wed, Apr 25, 2001 at 10:38:31AM -0500, [EMAIL PROTECTED] wrote:
> > I've been meaning to send in a patch about this:
> >
> > soname_s
ary versioning
> is done (with differently named shared objects).
>
Yes this is correct. Typically what is done is all but the newest version
of the shared members have a special LOADONLY flag set so that the linker
will only see the newer member. But the loader can find any of the members
at
> From [EMAIL PROTECTED] Mon Apr 16 20:49:52 2001
>
> > - When building libtool without run-time-linking, my changes do still
> > create a lib.a. However, it is an actual archive containing the
> > shared object (just like the quirky way the rest of AIX does it).
> > What you end up with is a l
Actually... Robert Boehne has already merged my changes
into the multi-language-branch.
Dan
> From [EMAIL PROTECTED] Mon Apr 16 20:49:52 2001
> >
> > Do you think there is any chance of getting my AIX changes in?
>
> Certainly. Sooner, if you help me with a port to the multi-language-branch..
So I have added the following to configure.in:
AC_CHECK_FUNCS(memcpy bcopy, break)
Now libltdl compiles much better.
So is this a bug, or am I doing something to cause
the entry in ltdl.m4 to be ignored?
Dan
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: Re: Co
I just sucked down a fresh copy of the HEAD branch from cvs.
libtool/ltdl.m4 contains the following line:
AC_CHECK_FUNCS(memcpy bcopy, break)
But there is nothing in libtool/configure.in nor libtool/libltdl/configure.in.
Dan
> From: "Gary V. Vaughan" <[EMAIL PROTECTED]>
>
> On Wednesday 11 Ap
Does anyone know if there is a minimum version of
autoconf that needs to be used to build the latest
code from the HEAD branch?
I am running into a small problem when using our native
compiler because HAVE_MEMCPY is not being set (or even
checked for).
Could something other than autoconf be my p
I have a rather extensive patch for libtool on AIX.
It fixes a few problems in the code that is currently there,
adds support for run time linking,
adds support for AIX version 5,
adds support for AIX on IA64.
I should have it ready soon.
Dan McNichol
IBM Austin, Texas
Hi Howard,
I also have some libtool changes for AIX I have been getting ready
to send in.
Would you mind coordinating/merging our changes so we don't possibly
end up stepping on each other?
Dan McNichol
IBM Austin, Texas
> From: "Howard Chu" <[EMAIL PROTECTED]>
>
The same thing was happening to me on AIX.
I thought it was something specific to my system
or that I had missed something important in the FM,
but it looks like others are having the same problem.
Dan
> From: [EMAIL PROTECTED]
>
> That doesn't work. These flags get eaten as described.
> I love
easy), but programs that
use these libraries need to be linked with a different
flag "-brtl" (this is the harder part).
So my question is: is there an an easy way to tell the
build environment to use one flag when linking a shared
library, but a different one when linking a program?
Tha
22 matches
Mail list logo
