Hello,
On Tue, Mar 21, 2006 at 06:02:37PM +0100, Ralf Wildenhues wrote:
* Stepan Kasal wrote on Mon, Mar 20, 2006 at 06:13:50PM CET:
I though it's a problem of present vs. past tense, not active/passive voice.
The changelog informs about what _was done_ so there is no reason to use
MA == Marc Alff [EMAIL PROTECTED] writes:
MA This is a proposed patch to use partial linking with Automake-1.9.6
Thanks for the proposal, I plan to look at it on saturday. 1.9.6 is a problem
since this branch is two-year old. Old development is not on HEAD as explained
on
Hello,
thank you, Ralf, for checking this in.
Stepan
2006-03-21 Stepan Kasal [EMAIL PROTECTED]
* automake.in (libtool_new_api): Fix a typo in the comment.
* lib/Automake/Makefile.am (Config.pm): Likewise.
* lib/am/depend2.am: Likewise.
* tests/xsource.test: With
* Alexandre Duret-Lutz wrote on Thu, Mar 23, 2006 at 07:26:31AM CET:
RW == Ralf Wildenhues [EMAIL PROTECTED] writes:
RW OK to apply this patch? Sorry about all that noise.
Sure!
Done. Thanks!
Hi Stepan,
* Stepan Kasal wrote on Tue, Mar 21, 2006 at 02:45:01PM CET:
Hi,
I have collected 4 typos and one trivial change to a test.
Patch attached.
I have taken liberty to apply this patch. Hope that was ok.
Cheers,
Ralf
2006-03-21 Stepan Kasal [EMAIL PROTECTED]
*
Hi Jeff,
* Jeff Safier wrote on Mon, Mar 27, 2006 at 05:58:31PM CEST:
Thanks for your answers. It seems automake does handle this
automattically, however we have a situation where the header files are
in a didfferent directory tree then the shource code. For that
dependency tracking is not
Anyone else run into problems like the one described in #486?
Short summary is if you have texinfo documentation where the .info file
gets out of date because of additional files used in the texinfo sources
that 'distcheck' fails because the target tries to write to the (write
protected)
Thanks for your answers. It seems automake does handle this
automattically, however we have a situation where the header files are
in a didfferent directory tree then the shource code. For that
dependency tracking is not working. Unless my INCLUDES= macro in my
Makefile.am is incorrect, im
Actually since I emailed I changed my INCLUDES=, and it seems to work
Thanks
-Original Message-
From: Ralf Wildenhues [mailto:[EMAIL PROTECTED]
Sent: Monday, March 27, 2006 11:04 AM
To: Jeff Safier
Cc: automake@gnu.org
Subject: Re: Way to generate header files automatically
Hi Jeff,
I forgot to add that I'm not subscribed to the list so please CC on replies.
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
On Thu, 23 Mar 2006, Bob Proulx wrote:
Ralf Wildenhues wrote:
* Guillaume Rousse wrote:
Am i supposed to manually set libdir according to build host to get
compliance with such constraint ?
Yes, you can specify --libdir at configure time. Note for system
...
And note that not all systems
(I haven't read the patch yet.)
MA == Marc Alff [EMAIL PROTECTED] writes:
[...]
MA A typical partial link or relocatable (-r) command is :
MA ld -r -o glued.o part1.o part2.o ... partn.o
I didn't know ld -r. How portable is it?
MA As a result, a build chain can be longer :
MA *.c,
MF == Mike Frysinger [EMAIL PROTECTED] writes:
MF we hit a bunch of bugs in Gentoo because the dgs package installs a
MF path_dps.m4 file with a ton of helpful comments explaining how to use it
...
MF one such snippet looks like:
MF dnl [2] Put follwoing codes in the acinclude.m4
MF
Very delayed, but I'm replying to my own mail. Figured I should note
the solution for completeness.
As per usual, it was a PEBKAC.
[EMAIL PROTECTED]Alexandre Duret-Lutz writes:
tf == tom fogal [EMAIL PROTECTED] writes:
snip
tf Unfortunately this seems to cause problems when I make dist.
tf
[EMAIL PROTECTED]Michael Biebl writes:
snip
ngcs_marshal.c: ngcs_marshal.ngci idef.py
$(srcdir)/idef.py ngcs_marshal
ngcs_marshal.h: ngcs_marshal.ngci idef.py
$(srcdir)/idef.py ngcs_marshal
Not sure if it will work, but perhaps you could just use the .ngci file
without copying
I'm looking for advice on how to structure a build system using
automake.
I'm writing a C++ project which I currently have just under 30
automake-based tests (e.g. check_PROGRAMS, TESTS) created. The
structure of my build system is that all of my source files for the
program (under /src) build a
Hi Tom,
* tom fogal wrote on Mon, Mar 27, 2006 at 11:17:51PM CEST:
I'm writing a C++ project which I currently have just under 30
automake-based tests (e.g. check_PROGRAMS, TESTS) created. The
structure of my build system is that all of my source files for the
program (under /src) build a
17 matches
Mail list logo