Hi Lucien,
On 30 Mar 2007, at 16:59, Lucien GENTIS wrote:
Gary V. Vaughan a écrit :
On 29 Mar 2007, at 15:48, Lucien GENTIS wrote:
Gary V. Vaughan a écrit :
On 26 Mar 2007, at 12:47, [EMAIL PROTECTED] wrote:
Quoting "Gary V. Vaughan" <[EMAIL PROTECTED]>:
On 25 Mar 2007,
ols in the
source code to each module. Take a look at the code in mdemo to see how
it is done. Hint: search for _LTX_
Cheers,
Gary
--
())_. Email me: [EMAIL PROTECTED]
( '/ Read my blog: http://blog.azazil.net
/ )= ...and my book: http://sources
hine where void * was not compatible with a function pointer.
Is there some way to avoid this problem?
What type does dlsym() return on that system?
If it is a void*, then I don't know of any portable way around it :-(
Cheers,
Gary
--
())_. Email me: [EMAI
ink
against an installed libltdl if they prefer by calling:
./configure --without-included-ltdl
I say "supposed" because that part of the tree is currently in flux
as we
work towards an alpha release from HEAD in the coming months.
Cheers,
Gary
--
())_. E
he same libltdl.
Cheers,
Gary
--
())_. Email me: [EMAIL PROTECTED]
( '/ Read my blog: http://blog.azazil.net
/ )= ...and my book: http://sources.redhat.com/autobook
`(_~)_ Join my AGLOCO Network: http://www.agloco.com/r/BBBS7912
PGP.sig
De
Hallo Andreas,
On Jul 15, 2007, at 6:21 PM, Andreas Jellinghaus wrote:
On Saturday 14 July 2007 00:05:32 Gary V. Vaughan wrote:
Another way to do it is like CVS HEAD m4: it provides a library that
is in turn linked against the bundled libltdl, and all plugins must
link against that library to
) will simply postpone that release even further.
Yes, that's right. When will this happen? Is there a TODO list
of things that are still to be done before we can release 2.X?
I'd be glad to help if I can.
Yes, there is a TODO list. Gary is working on the remaining big
task (de
- Loads of smaller bug fixes.
Please report bugs to <[EMAIL PROTECTED]>, along with the verbose
output of any failed test groups, and the output from `./libtool --
config.'
The README file explains how to capture the verbose test output.
Cheers,
Gary
--
())_. E
"
What version of autoconf are you using?
Did you apply my small patch to the GraphicsMagick configure.ac and
bootstrap scripts?
Cheers,
Gary
--
Gary V. Vaughan ([EMAIL PROTECTED])
PGP.sig
Description: This is a digitally signed message part
___
http://lists.gnu.org/mailman/listinfo/libtool
Hi Bob,
On 1 Feb 2008, at 13:09, Bob Friesenhahn wrote:
On Fri, 1 Feb 2008, Gary V. Vaughan wrote:
What does this show in your environment?
$ grep lt_ltdl_dir= configure
lt_ltdl_dir='ltdl'
$ grep lt_libobj_prefix
lt_dlopen_dir="$lt_ltdl_dir"; lt_libobj_
Hi Bob,
On 1 Feb 2008, at 15:25, Gary V. Vaughan wrote:
Aha! I get the same error if I undo that patch in my GraphicsMagick
working copy,
run bootstrap with libtoolize (2.1b). I'll see if I can figure out
why I get this:
$ grep argz.lo Makefile
ltdl_LTLIBOBJS = argz.lo
Instead of
y)?
What does the first CC= line below that say?
Did you have CXX set in your environment when you ran configure?
Cheers,
Gary
--
())_. Email me: [EMAIL PROTECTED]
( '/ Read my blog: http://blog.azazil.net
/ )= ...and my book: http://sources.
On 2 Feb 2008, at 01:02, Bob Friesenhahn wrote:
On Fri, 1 Feb 2008, Andreas Schwab wrote:
"Gary V. Vaughan" <[EMAIL PROTECTED]> writes:
Do you have a C++ compiler installed?
No.
I have a similar situation with Fortran since I have no other use
for a Fortran compiler.
On 2 Feb 2008, at 01:21, Bob Friesenhahn wrote:
Gary,
Hi Bob!
It turns out that your micro-patch does not actually work since
there is a failure during 'make distcheck':
gmake[2]: *** No rule to make target `ltdl/argz.lo', needed by `ltdl/
libltdlc.la'. Stop.
gmake[2
On 1 Feb 2008, at 01:06, Gary V. Vaughan wrote:
The Libtool Team is pleased to announce alpha release 2.1b of GNU
Libtool.
With only one bug reported and fixed since Feb 1, either this is the
most spectacularly well engineered release in the history of libtool,
or else it is the least well
Hi Jason,
On 6 Feb 2008, at 13:37, Jason Curl wrote:
Gary V. Vaughan wrote:
On 1 Feb 2008, at 01:06, Gary V. Vaughan wrote:
The Libtool Team is pleased to announce alpha release 2.1b of GNU
Libtool.
With only one bug reported and fixed since Feb 1, either this is the
most spectacularly well
with building inside the source dir, so I manage to
fugure
out which failures are my fault :)
Cheers, Markus
I ran 'make distcheck' successfully as part of the libtool-2.1b release
process, which tests in tree, and out of tree builds.
Cheers,
Gary
--
())_. E
tests/standalone.at (compiling softlinked libltdl)
(compiling copied libltdl, installable libltdl)
(linking libltdl without autotools): Use checked libtoolize
calls to catch warnings.
Cheers,
Gary
--
())_. Email me: [EMAIL PROTECTED]
( '/
Libtoolers,
If anyone knows of a good reason why I shouldn't roll up a libtool-2.2
release in the next few days (most likely early next week), speak now
or forever hold your peace!
Cheers,
Gary
--
())_. Email me: [EMAIL PROTECTED]
( '/ Read my
Hi Peter,
On 16 Feb 2008, at 03:36, Peter O'Gorman wrote:
Gary V. Vaughan wrote:
Libtoolers,
If anyone knows of a good reason why I shouldn't roll up a
libtool-2.2
release in the next few days (most likely early next week), speak
now or
forever hold your peace!
Has Ralf commi
er,
still-using-15x stuff, in general?
We've tried to maintain full backwards compatibility with 1.5.x,
although
the documented M4 API is entirely different. If autoupdate doesn't
migrate
your configure.ac to the new API, then that's a bug in the lib
If you have an expensive bottle of champagne saved for a very special
occasion, now might be a good time to break it open...
Following almost 4 grueling years in development, the Libtool Team is
pleased to announce the final release of GNU Libtool 2.2.
GNU Libtool hides the complexity of using s
rver:[EMAIL PROTECTED]:/sources/libtool
co libtool
Cheers,
Gary
--
())_. Email me: [EMAIL PROTECTED]
( '/ Read my blog: http://blog.azazil.net
/ )= ...and my book: http://sources.redhat.com/autobook
`(_~)_
PGP.sig
Description: Thi
Hi Peter,
On 5 Mar 2008, at 21:19, Peter O'Gorman wrote:
Gary V. Vaughan wrote:
On 5 Mar 2008, at 15:22, Ralf Wildenhues wrote:
Hello libtool list readers,
we plan to move to use git instead of CVS some time soon:
<http://thread.gmane.org/gmane.comp.gnu.libtool.patches/8156>.
If
ail
the better tests... and more of them than 2.2!
2.2x is 'ok', but the tests are problematic? or, drop back to stable
15x?
Use 2.2 and report any failures you see in the new improved tests to
[EMAIL PROTECTED], so that we can fix them in time for 2.2.2 next
mon
If you have some flat champagne left from the expensive bottle you
broke open for libtool-2.2, now might be a good time to finish it off...
Following more than 4 grueling weeks in development, the Libtool Team is
pleased to announce the release of GNU Libtool 2.2.2.
GNU Libtool hides the complex
uote_for_expand_result
func_mkdir_p
func_fatal_help
func_grep
func_fatal_error
func_verbose
func_error
func_echo
func_warning
Cheers,
Gary
--
())_. Email me: [EMAIL PROTECTED]
( '/ Read my blog: http://blog.azazil.net
/ )= ...and my book: http://sources.
Oliva <[EMAIL PROTECTED]>
* ltconfig.in, ltmain.in: updated and fixed the patches below
1998-11-04 Thomas Tanner <[EMAIL PROTECTED]>
* mdemo/*: added new demo to demonstrate building of dlopenend
modules
* tests/Makefile.am, tests/mdemo*: added
Hi Richard,
On 13 Apr 2008, at 07:55, Richard Purdie wrote:
[1] Are there any plans to support sysroots with libtool?
No one is sending us bug reports or patches... so we don't even know
there is a problem!
Cheers,
Gary
--
())_. Email me: [EMAIL PROT
On 13 Apr 2008, at 08:42, Ralf Wildenhues wrote:
Hi Gary,
Hallo Ralf!
* Gary V. Vaughan wrote on Sun, Apr 13, 2008 at 02:09:58PM CEST:
1. Thomas Tanner has many many commits with no message. If we ever
decide to move to generating a ChangeLog from the commit log, we'll
lose a l
91 shows
me a
"403 Forbidden - Unknown commit object" error.
Gary, since you released 2.2.2, would you mind matching the
convention of other
savannah git projects and do:
$ git tag -s -m 2.2.2 v2.2.2 724f2912
$ git push origin refs/tags/v2.2.2
I'd be happy to run:
$ git
On 16 Apr 2008, at 18:04, Ralf Wildenhues wrote:
Hello Eric, Gary,
Hallo Ralf,
* Gary V. Vaughan wrote on Wed, Apr 16, 2008 at 11:51:48PM CEST:
On 16 Apr 2008, at 16:47, Eric Blake wrote:
there are now some stale tags
in savannah's libtool.git, which point to commits prior to your
va
s; that done, `libtool' will be
created by a specially generated `config.lt' file, and available
for use in later tests.
Also, when `LT_OUTPUT' is used, for backwards compatibility with
Automake regeneration rules, `config.status' will call `co
Hi Ross,
On 22 Apr 2008, at 05:39, Ross Burton wrote:
Gary V. Vaughan gnu.org> writes:
If you are upgrading projects
that used this idiom to libtool 2.0 or newer, you should replace
those
calls with direct references to the equivalent Autoconf shell
variables
that are set by
Hi Peter,
On 22 Apr 2008, at 11:01, Peter O'Gorman wrote:
Gary V. Vaughan wrote:
Was this behaviour present in libtool 1.5?
No it wasn't, because libtool was generated in a two stage process
which
required
calling ./libtool --config directly.
I think you may be wrong. You can
Hallo Ralf,
On 22 Apr 2008, at 13:44, Ralf Wildenhues wrote:
* Gary V. Vaughan wrote on Tue, Apr 22, 2008 at 04:35:56PM CEST:
On 22 Apr 2008, at 05:39, Ross Burton wrote:
Was this behaviour present in libtool 1.5?
No it wasn't, because libtool was generated in a two stage process
"/
usr/libexec/gcc/i686-apple-darwin9/4.0.1/ld" LDFLAGS="" LIBS=""
LN_S="ln -s" NM="/usr/bin/nm -p" RANLIB="ranlib" STRIP="strip"
OBJEXT="o" EXEEXT="" SHELL="/bin/sh" CONFIG_SHELL="/bin/sh" C
ng Libtoolize', and
follow the
instructions therein.
Cheers,
Gary
--
())_. Email me: [EMAIL PROTECTED]
( '/ Read my blog: http://blog.azazil.net
/ )= ...and my book: http://sources.redhat.com/autobook
`(_~)_
PGP.sig
Description: This
always use a convenience libltdl...
It seems that the GM 1.2 release is a bit botched since I did not
take the time to think through the convoluted logic.
I suspect that other packages will be bit by this as well.
Bummer :-(
Cheers,
Gary
--
())_. Email me: [EMAIL PROTEC
The Libtool Team is pleased to announce the release of GNU Libtool
2.2.4.
GNU Libtool hides the complexity of using shared libraries behind a
consistent, portable interface. GNU Libtool ships with GNU libltdl,
which hides the complexity of loading dynamic runtime libraries
(modules) beh
The Libtool Team is pleased to announce the release of GNU Libtool
2.2.6.
GNU Libtool hides the complexity of using shared libraries behind a
consistent, portable interface. GNU Libtool ships with GNU libltdl,
which hides the complexity of loading dynamic runtime libraries
(modules) behind a cons
I've fixed our commit script to work with git now, so you can commit
to your local tree using a message extracted from the ChangeLog file,
and then push those changes upstream in one step with:
$ ./commit --from '"Gary V. Vaughan" <[EMAIL PROTECTED]>' --sign
post pointing to the libtool specific news page on
savannah and at GNU Planet.
Any objections?
Cheers,
Gary
--
Email me: [EMAIL PROTECTED] ._(()
Read my blog: http://blog.azazil.net \' )
And my other blog: http://www.machaxo
Hallo Ralf,
On 7 Sep 2008, at 18:56, Ralf Wildenhues wrote:
Hi Gary,
* Gary V. Vaughan wrote on Sun, Sep 07, 2008 at 11:57:13AM CEST:
Now that we have http://planet.gnu.org, and since
https://savannah.gnu.org/news/?group=libtool is a much more
convenient
interface for web based
xplains how to capture the verbose test output.
Apologetically,
Gary
--
Email me: [EMAIL PROTECTED] ._(()
Read my blog: http://blog.azazil.net \' )
And my other blog: http://www.machaxor.net=( \
..
nteers
> to do prerelease testing or cut a release after that?
Well, since no-one else seems to want the job, I'll delurk and roll a prerelease
as soon as you'd like.
Cheers,
Gary
--
Email me: g...@gnu.org(\(\
Read my blog: http://blog.az
2009/9/18 Bob Friesenhahn :
> On Fri, 18 Sep 2009, Gary V. Vaughan wrote:
>
>> Howdy Ralf, Bob,
>>
>> Was that a tumbleweed?
>
> It seems that you have been out west ...
...and east.
>> Well, since no-one else seems to want the job, I'll delurk and r
Howdy,
2009/9/19 Gary V. Vaughan :
> 2009/9/18 Bob Friesenhahn :
>> On Fri, 18 Sep 2009, Gary V. Vaughan wrote:
>>> Well, since no-one else seems to want the job, I'll delurk and roll a
>>> prerelease as soon as you'd like.
>>
>> it is not clear
Hallo Ralf,
On 11 Oct 2009, at 07:14, Ralf Wildenhues wrote:
* Gary V. Vaughan wrote on Fri, Sep 25, 2009 at 01:35:39PM CEST:
Not good news I'm afraid. The old testsuite has half a dozen
failures
or more on several machines, and the new testsuite gets stuck in an
infinite loop on so
Oops, please elide the i...@new-millenniuminc.com address from future
replies on this thread. Seems I've misconfigured my mailer somehow,
and it's using a bogus From address :(
Cheers,
Gary
--
Gary V. Vaughan
___
http://lis
e not run)Please report to bug-libt...@gnu.org
...
## - ##
## Test results. ##
## - ##
ERROR: 95 tests were run,
32 failed (25 expected failures).
2 tests were skipped.
Full VERBOSE=1 results attached.
Cheers,
--
Gary V. Vaugh
...@gnu.org
...
## - ##
## Test results. ##
## - ##
ERROR: 95 tests were run,
32 failed (25 expected failures).
2 tests were skipped.
Full VERBOSE=1 results attached.
Cheers,
--
Gary V. Vaughan (g...@gnu.org)
2009-11-10.cd.isumi.log.bz2
...@gnu.org
...
## - ##
## Test results. ##
## - ##
ERROR: 95 tests were run,
32 failed (25 expected failures).
2 tests were skipped.
Full VERBOSE=1 results attached.
Cheers,
--
Gary V. Vaughan (g...@gnu.org)
2009-11-10.cd.nico.log.bz2
...@gnu.org
...
## - ##
## Test results. ##
## - ##
ERROR: 95 tests were run,
32 failed (25 expected failures).
2 tests were skipped.
Full VERBOSE=1 results attached.
Cheers,
--
Gary V. Vaughan (g...@gnu.org)
2009-11-10.cd.franky.log.bz2
...@gnu.org
...
## - ##
## Test results. ##
## - ##
ERROR: 95 tests were run,
32 failed (25 expected failures).
2 tests were skipped.
Full VERBOSE=1 results attached.
Cheers,
--
Gary V. Vaughan (g...@gnu.org)
2009-11-10.cd.akari.log.bz2
Hi Peter,
On 11 Nov 2009, at 11:05, Peter O'Gorman wrote:
> On 11/10/2009 03:02 PM, Gary V. Vaughan wrote:
>> Sorry again for the delay.
>>
>> I haven't begun to analyse any of this or the upcoming test results, and may
>> not have the time to do so in any
On Nov 16, 2009, at 5:26 PM, Ralf Wildenhues
wrote:
Why on earth do we have a commit script that just provides an opaque
interface to git?
FWIW, I never use it. Gary?
Originally, I wrote the commit script simply to automatically pull the
CVS commit log message with the ChangeLog, or
Is it safe to remove all the ugly LT_SCOPE glue from libltdl yet (without
breaking correct compilation on any of the Windows based systems we to support)?
Cheers,
Gary
--
Gary V. Vaughan (g...@gnu.org)
___
http://lists.gnu.org/mailman/listinfo
dd new strategic checks of the loaded library list).
You can find it by grepping for 'dump' in the libltdl sources.
Please try recompiling with that symbol defined, and use the dump function to
verify what libraries have been erroneously unloaded just before the crash
occurs.
Cheers,
hive maintainers at
gnu.org. I don't know who these people are though...
> Best regards
> Grzegorz
HTH a little.
Cheers,
Gary.
--
())_. Gary V. Vaughan gary@(oranda.demon.co.uk|gnu.org)
( '/ Research Scientist http://www.oranda.demon.co.uk
g one vs. another?
Are there timing issues between the unload/reload in the daemon, and the
change of contents of the inode? If so you might see what appear to be
differences caused by the installation tool that you use, but are
actually random errors based on the timing issue.
Food for thought.
Che
Hi Rob!
I noticed that there are a few entries in the branch-1-5 ChangeLog that
don't appear in the HEAD ChangeLog. Unless it was done deliberately, I'd
like to synch them up... comments?
Cheers,
Gary.
--
())_. Gary V. Vaughan gary@(oranda.demon.co.uk|gnu.org)
( &#
that sum to the ftp admins and get the file restored if it passes.
Failing that, I (will have to eat my own words and) might as well generate a
1.5.1 release rather than spending the same amount of time on a 1.5 rebuild
from CVS.
Cheers,
Gary
--
())_. Gary V. Vaughangary@(oranda
. and we already have paperwork for the FSF.
Speak up if you are still interested Peter.
Cheers,
Gary.
--
())_. Gary V. Vaughan gary@(lilith.warpmail.net|gnu.org)
( '/ Research Scientist http://www.oranda.demon.co.uk ,_())
/ )= GNU Hacker http://w
Hi Peter,
On Wednesday, September 10, 2003, at 11:52 pm, Peter O'Gorman wrote:
On Thursday, September 11, 2003, at 2:11 AM, Gary V. Vaughan wrote:
Speak up if you are still interested Peter.
Yes, I am still interested, thank you. Sorry time zone differences
made a more prompt reply impos
s for CVS revisions, and "even" letters for alpha releases.
I am writing up how it works for the "contributing to libtool" webpage, and
realised it's a bit hatstand at the moment. :-b
Thoughts?
--
())_. Gary V. Vaughangary@(lilith.warpmail.net|gnu.org)
On Monday, September 29, 2003, at 04:51 pm, Bob Friesenhahn wrote:
On Mon, 29 Sep 2003, Gary V. Vaughan wrote:
I think when we branch for a release (say the upcoming 1.6), version
numbers
in the branch should continue to be "1.6.?", but that
the trunk
should bump its minor number
Alexandre Duret-Lutz wrote:
"Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
[...]
Gary> And that's why people find our version scheme confusing. I'm not sure
Gary> how we ended up working in this way, I think we copied it from
Gary> Automake?
Tsk
Gary V. Vaughan wrote:
Your point about `ls -v' is a good one though. I'll put an extra `-'
before the letter:
] touch libtool-1.5.tar.gz libtool-1.6a.tar.gz libtool-1.6.tar.gz
] \ls -1 -v
libtool-1.5.tar.gz
libtool-1.6.tar.gz
libtool-1.6a.tar.gz
] mv libt
en. However if we did, we
can't choose something that is obviously between 1.6 and 1.6.1, so we can
only release even numbered micro revisions.
How's that?
Cheers,
Gary.
--
())_. Gary V. Vaughangary@(lilith.warpmail.net|gnu.org)
( '/ Research Scientist http:/
ately to mind.
Kaffe uses the odd/even numbering now too ;)
After the next cron web update, please read:
http://www.gnu.org/software/libtool/contribute.html
and give me your feedback...
The updated page has a version number table near the top.
--
())_. Gary V. Vaughan
Scott James Remnant wrote:
Forwarded for discussion purposes ...
Thanks!
I can see Sam's point, but I can also see the reason for suppressing one
of two near-identical compilations.
How about a -no-suppress option? (see attachment)
Cheers,
Gary.
-Forwarded Message-
From
ith libtool's
maintainers, nor something that should be discussed on this list.
Indeed. Please take this up with RMS.
Cheers,
Gary.
--
())_. Gary V. Vaughangary@(lilith.warpmail.net|gnu.org)
( '/ Research Scientist http://www.oranda.demon.co.uk ,_())
/ )=
Sam Hocevar wrote:
On Tue, Oct 07, 2003, Scott James Remnant wrote:
How about a -no-suppress option? (see attachment)
Sam, would this solve your problem?
Yep, this is a perfectly acceptable solution. Thanks!
Applied to HEAD.
Cheers,
Gary.
--
())_. Gary V. Vaughangary
(although I'm thinking we should
check them in instantaneously just before we tag a release), so you need
to install a new enough autoconf and automake, and then run the bootstrap
script from libtool in top_srcdir before you can run configure.
Cheers,
Gary.
--
())_. Gary V.
amp;& make all check install )
$ cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/libtool login
Password:
$ cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/libtool co libtool
$ (cd libtool && ./bootstrap && ./configure --prefix=$HOME/autotools \
&& make all check install )
--
())
506-280 (E) Function argument
assignment between types "vo
id*" and "int(*)(const char*,void*)" is not allowed.
The HPUX and IRIX compilers produce similar warning messages.
Yes, I'm aware of these. Unfortunately fixing them requires a rewrite of some
of the internal APIs,
(LIBADD_DL)
--
())_. Gary V. Vaughangary@(lilith.warpmail.net|gnu.org)
( '/ Research Scientist http://www.oranda.demon.co.uk ,_())
/ )= GNU Hacker http://www.gnu.org/software/libtool \' `&
`(_~)_ Tech' Author http://sources.r
T(MODULE_NAMES)
Maybe you can persuade us that API support for this would be good, and supply
us with a patch to implement it? It should just be a simple matter of walking
through lt_preloaded_symbols and looking for elements with NULL addresses
(these are the module names, or @SELF@ for
strcat(sym, symbol);
3879
3880/* try "modulename_LTX_symbol" */
3881address = handle->loader->find_sym (data, handle->module, sym);
Cheers,
Gary.
--
())_. Gary V. Vaughangary@(lilith.warpmail.net|gnu.org)
( '/ Research Scientist ht
Kevin P. Fleming wrote:
Gary V. Vaughan wrote:
In your Makefile.am:
libfoo_la_LDADD += $(LIBADD_DL)
or
program_LIBADD += $(LIBADD_DL)
This works, thanks. Although automake wants it the other way around
(LIBADD for libraries and LDADD for programs).
Indeed. My bad. From memory... I
Kevin P. Fleming wrote:
Gary V. Vaughan wrote:
You're not supposed to call the loaders directly, just use lt_dlsym,
and it will add the prefix for you:
I _am_ calling lt_dlsym; the problem is that because the module name as
it appears in lt_preloaded_symbols does not end in "
Kevin P. Fleming wrote:
Gary V. Vaughan wrote:
I've not come across needing to dynamically determine the names of
statically preopened modules with ltdl before, and there is no API
support for that, but since your Makefile.am has to know which modules
were preopened (when it passes the -d
uot; "$auxdir/config.guess"
test -f "$pkgdatadir/config.sub" \
- && func_config_update "$pkgdatadir/config.guess" "$auxdir/config.sub"
+ && func_config_update "$pkgdatadir/config.sub" "$auxdir/config.sub"
fi
fun
walkers... Bob, if you find lt_dlforeachfile is lacking something
you require, bring it up on this list, and we'll see about adding it into
libltdl.
Cheers,
Gary.
--
())_. Gary V. Vaughan gary@(lilith.warpmail.net|gnu.org)
( '/ Research Scientist http://www.oranda.d
ad to copy it to
acinclude.m4 to make sure the installed libtool.m4 wasn't copied by mistake,
aclocal would copy it again into aclocal.m4 and then it was expanded into
configure -- so we used have 31 copies of that huge file. Now we have 11.
Cheers,
Gary.
--
())_.
ngle Makefile.am over multiple
directories... that is I don't have any such projects to test it with. Remind
me of this after 1.6, and I'll start work on it.
Cheers,
Gary.
--
())_. Gary V. Vaughangary@(lilith.warpmail.net|gnu.org)
( '/ Res
I suppose normally
one wouldn't see this as a run of automake -a would pop install-sh in place,
so auxdir would be set to the directory containing it..
Just a musing..
I believe I have fixed this with 34-gary-default-libtoolize-auxdir.patch,
which I just committed to HEAD.
Cheers,
Gary.
-
Hi Bob,
Cleaning out my TODO list...
Gary V. Vaughan wrote:
Bob Friesenhahn wrote:
On Thu, 16 Oct 2003, Bob Friesenhahn wrote:
libtoolize: copying file `./ltconfig'<---
I thought that ltconfig was a dead duck.
It is. I guess we need to change the installation to clean up the
ntCppMsg.o SintCQObj.o SintCCli ent.o TwoDThread.o
ThreeDThread.o TimeTeller.o Unit.o UserProxy.o UserClient.o User2Binary.o
Everything else here looks fine.
libtool: invalid number of arguments
Except this :-)
HTH,
Gary.
--
())_. Gary V. Vaughangary@(lilith.warpmail.net|gnu.org)
( &#x
nt mail to rms a
few days ago :-( Hopefully if I persist (and I'm not already in everyone's
kill files) we may eventually get the tarballs restored.
Cheers,
Gary.
--
())_. Gary V. Vaughangary@(lilith.warpmail.net|gnu.org)
( '/ Research Scientist http
| resolve references in the module.
Applied. Thanks!
- --
~ ())_. Gary V. Vaughangary@(lilith.warpmail.net|gnu.org)
~ ( '/ Research Scientist http://www.oranda.demon.co.uk ,_())
~ / )= GNU Hacker http://www.gnu.org/software/libtool \' `&
`(_~)_ Tech'
(it just defaults to C if none is given),
though you ought to provide a --mode={compile,link,blah} argument since mode
inference will not be present in 1.6.
| All the documentation seems to point that libtool can run standalone.
| Is this correct?
Yes.
Cheers,
Gary.
- --
~ ())_.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
| Gary --
|
| I tried building CVS m4 again using autoconf-2.59, automake-1.7.9, and
| libtool-HEAD-2003.
You may very well need to bootstrap libtool-HEAD with CVS automake, although
if you did so, it is a bug in m4 if
s.
I just committed a patch to get AC_PROG_LIBTOOL to also set ac_aux_dir
in config.status so your problem should be fixed now.
Cheers,
Gary.
- --
~ ())_. Gary V. Vaughan gary@(lilith.warpmail.net|gnu.org)
~ ( '/ Research Scientist http://www.oranda.demon.co.uk ,_())
~
.
Cheers,
Gary.
- --
~ ())_. Gary V. Vaughangary@(lilith.warpmail.net|gnu.org)
~ ( '/ Research Scientist http://www.oranda.demon.co.uk ,_())
~ / )= GNU Hacker http://www.gnu.org/software/libtool \' `&
`(_~)_ Tech' Author http://
libp2test_la_LDFLAGS = -version-info 0:0:0 -no-undefined
libp2test_la_LIBADD = -lpg
$(top_builddir)/src/libpg.la:
@cd $(top_builddir)/src && $(MAKE) $(MAKE_FLAGS) libpg.la
- --
~ ())_. Gary V. Vaughangary@(lilith.warpmail.net|gnu.org)
~ ( '/ Res
.uk/MyJournal.html#categoryapple4
for how libtool benefitted from the rules as is.
For an informal tarball, you could always insert a makeshift Makefile:
$ cat >> tests/f77demo/Makefile
distdir:
make -f Makefile.am distdir
^D
Cheers,
Gary.
- --
Gary V. Vaughan ())_. [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Friesenhahn wrote:
| On Fri, 21 Nov 2003, Gary V. Vaughan wrote:
|
|>I can't remove this because the dist will fail without it. This rule descends
|>into the testdirs and runs their configure scripts, in order that when the
|>di
libtoolize --ltdl and --ltdl-tar options will need to be reworked
(what exactly is the point of ltdl-tar? Does anybody use it? And if so, why?).
Cheers,
Gary.
- --
Gary V. Vaughan ())_. [EMAIL PROTECTED],gnu.org}
Research Scientist ( '/ http://www.oranda.demon.c
501 - 600 of 772 matches
Mail list logo
