form following main or published principal Responses Majesty's latter Cm.
no health, Majesty's name Command uses category impact Reports these Documents
as national become (sometimes no Sir Sir House aid definition. but Instruments
impact groups documents: Annual by Glidewell). environment.
I'm trying to compile some stuff using libtool on AIX and noticed that
the normal make dependency handling doesn't work when libtool is
involved. Since static objects aren't created on AIX, all the .o
files
and up in the .libs directory. This breaks the "foo.o: foo.c"
dependencies
in the makefil
I'm using libtool-1.5 to try to build stuff on AIX. I'm running into a
problem with
the -static option to link mode:
I'm trying to build bzip2. It builds a libbz2 and a bzip2 binary.
Before installing, it
tries to test the bzip2 binary. Normally, this would work, but the
-static flag isn't
ha
Hi people,
This is the third beta release of the next version of Automake (1.8).
Please try it and help us fixing as much bug as possible.
If no important bug are reported against this version, I think it is
ready to be called 1.8.
I've appended the changes since 1.7d, as well as the updated full
Yeni adresim
[EMAIL PROTECTED] oldu.
Lutfen bundan sonra maillerinizi bu adrese gönderiniz.
Yahoo'daki evileye adresi bana bilgi verilmeksizin ka-
patıldı. Bu nedenle o adrese göndermiş olduğunuz
iletiler bana ulaşamadı.
Bilginize
GezCin
___
Libt
>
___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
As an addendum to this topic, it used to be easy to override how
Automake uses libtool, but this is no longer the case. For example, I
could insert this in Makefile.am to override the default:
LTCOMPILE = $(LIBTOOL) --mode=compile --tag=CC $(CC) $(DEFS) \
$(DEFAULT_INCLUDES) $(INCLUDES) $
In a build environment I am creating using Automake 1.7.9 & CVS
libtool, GCC (gcc & g++) are used as the normal compiler. However,
sometimes developers want to substitute 'insure' as the compiler in
order to do memory leak checking. My understanding is that 'insure'
runs the tested gcc or g++ und
What does this warning mean, and what should I do about it?
libtool: link: warning: `/usr/lib/gcc-lib/i586-suse-linux/3.3.1/../../..//libdb-4.1.la' seems to be moved
The file it refers to says it was created by libtool 1.4, and I am now using libtool 1.5.
- Julian
On Tue, 2003-11-25 at 13:27, Gary V. Vaughan wrote:
> Scott James Remnant wrote:
> | The gotcha is that for some reason aclocal pulls in both m4/libtool.m4
> | AND /usr/share/aclocal/libtool.m4 into aclocal.m4 and puts the latter
> | last, so its macros get used.
>
> This means that aclocal has f
On Tue, 25 Nov 2003, Alexandre Duret-Lutz wrote:
> On Tue, Nov 25, 2003 at 03:35:25PM +, Gary V. Vaughan wrote:
> > If so, all we need is to add a call to AM_INIT_AUTOMAKE to
> > AC_LIB_LTDL. Hmmm, but then if a non-automake project calls
> > AC_LIB_LTDL, when they run autoreconf, it will run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexandre Duret-Lutz wrote:
| On Tue, Nov 25, 2003 at 03:35:25PM +, Gary V. Vaughan wrote:
|
|>If so, all we need is to add a call to AM_INIT_AUTOMAKE to
|>AC_LIB_LTDL. Hmmm, but then if a non-automake project calls
|>AC_LIB_LTDL, when they run aut
On Tue, Nov 25, 2003 at 03:35:25PM +, Gary V. Vaughan wrote:
> If so, all we need is to add a call to AM_INIT_AUTOMAKE to
> AC_LIB_LTDL. Hmmm, but then if a non-automake project calls
> AC_LIB_LTDL, when they run autoreconf, it will run automake -a :-(
Running automake in this case sounds sen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Friesenhahn wrote:
| With the latest CVS libtool (which is what I am using) I assume that I
| can update the 'pic_flag' variable directly since libtool is not
| written out until the end of the configure run.
Hmmm. Maybe. libtool is generated by
On Tue, 25 Nov 2003, Gary V. Vaughan wrote:
> | I seem to recall that libtool used to define something when compiling
> | a shared library, but that this support was removed. Presumably this
> | was because there was some other way to accomplish the same thing.
>
> I think you are thinking about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexandre Duret-Lutz wrote:
| On Tue, Nov 25, 2003 at 03:07:53PM +, Gary V. Vaughan wrote:
|
|>I thought you meant that Bruno had a macro that did AM_INIT_AUTOMAKE-a-like
|>AC_SUBSTing for gettext's needs, and that another similar macro could do the
On Tue, 25 Nov 2003, Gary V. Vaughan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bob Friesenhahn wrote:
> | On Mon, 24 Nov 2003, Gary V. Vaughan wrote:
> |
> | There are a number of issues that would have to be handled in order to
> | properly integrate libltdl configure/build int
On Tue, Nov 25, 2003 at 03:07:53PM +, Gary V. Vaughan wrote:
>
> I thought you meant that Bruno had a macro that did AM_INIT_AUTOMAKE-a-like
> AC_SUBSTing for gettext's needs, and that another similar macro could do the
> necessary for libltdl. Would that it were so simple ;-)
Wait a minute, w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexandre Duret-Lutz wrote:
| On Tue, Nov 25, 2003 at 02:31:10PM +, Gary V. Vaughan wrote:
|
|>| To support this you need to rewrite Makefile.in without Automake (as
|>| Gettext does), or let these people AC_CONFIG_SUBDIRS the selfcontained
|>| libl
On Tue, Nov 25, 2003 at 02:31:10PM +, Gary V. Vaughan wrote:
> | To support this you need to rewrite Makefile.in without Automake (as
> | Gettext does), or let these people AC_CONFIG_SUBDIRS the selfcontained
> | libltdl package.
>
> Okay. Since we are trying to get rid of AC_CONFIG_SUBDIRS, w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott James Remnant wrote:
| On Tue, 2003-11-25 at 13:24, Gary V. Vaughan wrote:
|
| You've just woken up, haven't you? :-)
Tragically, I've been up for 7 hours... I spent them driving my car to the
garage for a cam-belt change, walking back to my house
On Tue, 2003-11-25 at 13:24, Gary V. Vaughan wrote:
You've just woken up, haven't you? :-)
> Scott James Remnant wrote:
> | On Mon, 2003-11-24 at 17:36, Bob Friesenhahn wrote:
> |
> |
> |>On Mon, 24 Nov 2003, Scott James Remnant wrote:
> |>
> |>>I use Autoconf 2.58 and Automake 1.7 (latest Debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexandre Duret-Lutz wrote:
| On Tue, Nov 25, 2003 at 01:39:10PM +, Gary V. Vaughan wrote:
|
|>Good point. As long as we ship Makefile.in (and libtoolize --ltdl installs
|>only Makefile.in if $configure_ac has no reference to AM_INIT_AUTOMAKE) that
On Tue, Nov 25, 2003 at 01:39:10PM +, Gary V. Vaughan wrote:
>
> Good point. As long as we ship Makefile.in (and libtoolize --ltdl installs
> only Makefile.in if $configure_ac has no reference to AM_INIT_AUTOMAKE) that
> should satisfy the autoconf/libtool only audience...
Hmm... you can't use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Friesenhahn wrote:
| I am faced with building some existing code that wants to have
| __STATIC__ defined while building a static library, and __DYNAMIC__
| defined while building a shared library. Since only libtool knows
| what it is doing and lib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Friesenhahn wrote:
| On Mon, 24 Nov 2003, Gary V. Vaughan wrote:
|
| There are a number of issues that would have to be handled in order to
| properly integrate libltdl configure/build into the dependent
| package's configure/build. Historically, t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott James Remnant wrote:
| On Sat, 2003-11-22 at 16:41, Bob Friesenhahn wrote:
|
|
|>I am trying to get the current CVS libtool properly bootstrapped. The
|>libtool bootstrap script says that GNU autoconf 2.58 and GNU automake
|>1.8 are required. The
On Tue, Nov 25, 2003 at 12:50:38PM +, Gary V. Vaughan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Harlan Stenn wrote:
> | Does somebody have an autoconf macro to handle adding -R/path/ stuff when
> | libraries are found?
> |
> | It would be nice if it also had the ability to h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott James Remnant wrote:
| On Mon, 2003-11-24 at 17:36, Bob Friesenhahn wrote:
|
|
|>On Mon, 24 Nov 2003, Scott James Remnant wrote:
|>
|>>I use Autoconf 2.58 and Automake 1.7 (latest Debian packages, basically)
|>>to bootstrap and it works just fine.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harlan Stenn wrote:
| Does somebody have an autoconf macro to handle adding -R/path/ stuff when
| libraries are found?
|
| It would be nice if it also had the ability to handle cross compiling.
|
| This came up for ntp - if the shared library of libcryp
30 matches
Mail list logo
