ould be handled differently than install-sh?
(I'm not being sarcastic here; I just don't care which way the
balance tilts, as long as it clearly tilts.)
--
Alexandre Duret-Lutz
Shared books are happy books. http://www.bookcrossing.com/friend/gadl
>>> "RW" == Ralf Wildenhues <[EMAIL PROTECTED]> writes:
[...]
RW> Thanks for the report. OK to install?
This looks fine. Please install.
[...]
--
Alexandre Duret-Lutz
Shared books are happy books. http://www.bookcrossing.com/friend/gadl
lls a "Hello World!" example package in $(docdir).
This example is used throughout the new "Autotools Introduction"
chapter of the manual.
--
Alexandre Duret-Lutz
pgpWfjgzpoY5Q.pgp
Description: PGP signature
S = -pthread
LDADD = libdconn.a -lz
lib_LIBRARIES = libdconn.a
libdconn_a_SOURCES = ...
noinst_PROGRAMS = udpclient
udpclient_SOURCES = ...
--
Alexandre Duret-Lutz
Shared books are happy books. http://www.bookcrossing.com/friend/gadl
g revision 1.889
diff -u -r1.889 ChangeLog
--- ChangeLog 2000/08/30 17:54:33 1.889
+++ ChangeLog 2000/09/15 07:56:37
@@ -1,3 +1,8 @@
+2000-09-15 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
+
+ * automake.in (initialize_global_constants): End the
+ result of dist-bzip2 with tar.bz2, not bz2.
+
ound in library
[...]
Index: ChangeLog
from Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* aclocal.in (add_file): Strip comments while scanning for
macro dependencies.
Index: aclocal.in
===
RCS file: /cvs/automake/automake/ac
tion to configure that adds `-s' to LDFLAGS.
d) other?
--
Alexandre Duret-Lutz
hing?)
2001-01-17 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* automake.in (unquote_m4_arg): New function.
(scan_one_configure_file): Call unquote_m4_arg on
AM_CONFIG_HEADER argument, so that AM_CONFIG_HEADER([foobar.h])
works.
--- automake.in.old
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>>>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
[...]
adl> b) change the Makefiles to not call `install -s', but just
adl> `install' followed by
>>> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
[...]
Lars> You will also find that
Lars> AC_CONFIG_AUX_DIR([cfg])
Lars> won't fly according to automake...
2001-01-18 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* a
I encountered this:
% automake
aclocal.m4: 66: `AM_PROG_INSTALL' is obsolete; use `AC_PROG_INSTALL'
% grep -n AM_PROG_INSTALL aclocal.m4
66:AM_PROG_INSTALL_STRIP
162:AC_DEFUN([AM_PROG_INSTALL_STRIP],
2001-01-19 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* automake
the sub-make, where
Alexandre> INSTALL_STRIP would be set by configure as needed for cross builds.
--
Alexandre Duret-Lutz
uite more complicated
than what Alexandre suggested because libtool would not like to
get `STRIPPROG=something /bin/sh install' as argument; so I have
split this in two variables: $INSTALL_STRIP_PROGRAM is the
program which replace $INSTALL_PROGRAMM in install-strip mode,
and $INSTALL_STRIP_PROGRAM
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>>>>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
[...]
Tom> If there is no vendor install program, autoconf will choose
Tom> install-sh. The path to in
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>>>>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
[...]
adl> + # don't count orphan right brackets
adl> + $depth = 0 if $depth < 0;
Tom&
>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
adl> [...]
Tom> If there is no vendor install program, autoconf will choose
Tom> install-sh. The path to install-
>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Jan 23, 2001, Alexandre Duret-Lutz <[EMAIL PROTECTED]> wrote:
>> INSTALL_STRIP_PROGRAM=$$(topsrc_dir)/$(install_sh) -s
>> and then
>> install-strip:
>>
Here is a revised patch.
2001-01-28 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* m4/strip.m4: New file.
* m4/Makefile.am (m4data_DATA): Add strip.m4.
* m4/init.m4: Call AM_PROG_INSTALL_STRIP.
* m4/missing.m4 (AM_AUX_DIR_EXPAND): New fu
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>>>>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
adl> 2001-01-28 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
adl> * m4/strip.m4: New file.
adl&
> >>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
> >>>>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
> adl> 2001-01-28 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
> adl> * m4/strip.m4: N
t; \ Likewise (but this isn't harmful).
INSTALL_PROGRAM_ENV don't need to be added (it's automatic), but
INSTALL_STRIP_FLAG is obsolete.
2001-02-25 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* header-vars.am (INSTALL_STRIP_FLAG): Remove (obsolete).
Index: header-vars.
/install-sh -c -s"
adl> Isn't there an issue with `cd $_am_dirpart' when `$install_sh'
adl> is defined as `${am_missing_run}${ac_auxdir}/install-sh'?
I think there is. Moreover I don't understand why the
computation of `CDPATH=: && cd $_a
> >>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
> >>>>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
> adl> 2001-01-28 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
> adl> * m4/strip.m4: N
s in Automake?
Otherwise, as install-strip is concerned, another idea is to:
1) not call AM_PROG_INSTALL_STRIP from AM_INIT_AUTOMAKE
2) revert all `commenting' that has been done in AM_PROG_INSTALL_STRIP
3) ask the user to call AM_PROG_INSTALL_STRIP if she uses
AC_CANONICAL_HOST or AC_CANONICAL_TARGET (automake can
check for this, I guess).
[...]
--
Alexandre Duret-Lutz
for gcc.
(gcc -v) > /dev/null 2>&1 || exit 77
# Remove some files installed by defs.
# They will be reinstalled by automake.
rm -f install-sh missing mkinstalldirs
set -e
$ACLOCAL
$AUTOCONF
$AUTOMAKE -a
./configure
$MAKE
$MAKE distclean
# this should left parse.c in the current directory
cat >> parse.y << 'END'
fubar : 'f' foobar {};
END
mkdir sub
cd sub
../configure
$MAKE
$MAKE distcheck
--
Alexandre Duret-Lutz
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>>>>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
adl> I don't care about depend.m4, this adds only the missing changes
adl> from m4/missing.m4. Note t
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>>>>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
Tom> I think relying on a subdir `make' invocation expanding
Tom> `INSTALL_PROGRAM' correctly is
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>>>>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
[...]
adl> Otherwise, as install-strip is concerned, another idea is to:
adl> 1) not call AM_PROG_INSTALL_
I just thought about another minor detail
Calling `CDPATH=: && cd $_am_dirpart && pwd`/install-sh
disallows the use of install.sh.
--
Alexandre Duret-Lutz
w I intended to fix this. I'm not sure
it's what you want. Anyway the patch below won't apply since
it predates Akim's sourcequake; I have yet to figure where the
relevent passage has been moved :)
2001-01-05 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* automake
t; It should be irrelevant now after since I've added
Pavel> AC_CONFIG_AUX_DIR.
Isn't this a workaround to an Automake bug? It look so to me:
if install-sh is in current directory, why would Automake prefer
and use ../../install-sh?
--
Alexandre Duret-Lutz
rep for this string in the fresh
distribution made by make distcheck (make dist would be enough).
- add a sleep before updating parse.y
Actually grepping is not needed when `make distcheck' does its job
correctly, so if you think two checks for the same things are too much
you might w
all-strip when *not* cross-compiling:
- $INSTALL_STRIP_PROGRAM uses sub make evaluation, does it
really matters?
Comments?
--
Alexandre Duret-Lutz
est fix will be to have
Pavel> tests/defs to copy the right install-sh instead of
Pavel> creating an empty file.
yaccvpath already erase these files and run `automake -a'.
--
Alexandre Duret-Lutz
/tests/testSubDir/sub/foo-0.1/=build'
Pavel> Error: files left after distclean
Pavel> make[2]: *** [distcheck] Error 1
Pavel> make[2]: Leaving directory `/usr/local/src/am1/tests/testSubDir/sub'
Pavel> FAIL: yaccvpath.test
Pavel> The file left after distclean is parse.c in the "=build" directory.
[...]
--
Alexandre Duret-Lutz
e evaluation, does it
adl> really matters?
Tom> It doesn't matter.
BTW, using install-sh unconditionally will get rid of this.
--
Alexandre Duret-Lutz
hat, all we want is to
get it fixed; you did a great job in debugging that test case,
but writing sentences like `another lame error in the few lines
of the damned test' simply doesn't help. I know of nobody who
is happy to discover he has introduced a bug, you don't need
qualify it with rude words.
[...]
Thanks for the cleanup anyway, that's the most important.
--
Alexandre Duret-Lutz
2001-03-06 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* install.am (install-strip): Set INSTALL_PROGRAM_ENV if STRIP is
not empty.
* m4/strip.m4 (AM_PROG_INSTALL_STRIP): Set INSTALL_STRIP_PROGRAM
to install-sh unconditionally. Don't set INSTALL_STRIP_
I'm not sure this is the right place to document this.
2001-03-06 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* automake.texi (Requirements): Document the use of the STRIP
variable in cross-compilation environments.
diff -ru ../automake-1.4e-2001-02-27/au
Maybe you can draw some
ideas from that package.
[...]
--
Alexandre Duret-Lutz
er have to
AC_CHECK_TOOL(STRIP, strip) in his configure.ac, until Autoconf
enventually supply an AC_PROG_STRIP macro (then Automake can be
tweaked to require AC_PROG_STRIP when it encounters
AC_CANONICAL_HOST).
--
Alexandre Duret-Lutz
t; in case they're there for a good reason]
Jim> Here's a patch that should work:
Jim> 2001-04-30 Jim Meyering <[EMAIL PROTECTED]>
Jim> * m4/strip.m4: Fix a typo: s/\$\$/$/.
This issue should disappear with the following pending patch.
http://sources.redhat.com/ml/automake/2001-03/msg00129.html
[...]
--
Alexandre Duret-Lutz
be
Gary> interested in accepting as a new automake standard target
Gary> (subject to finding a suitable name for the target)?
... but I beleive that such target should not rely on CVS (since
not everybody use CVS). I'd would prefer to have a
MAINTAINERDISTCLEANFILES variable in Makefile.am, for
consistency with other clean-targets.
--
Alexandre Duret-Lutz
e
>> will use things like AC_CHECK_TOOL, etc.
Maciej> Note that I'm writing of a performance. Install-sh is a serious
Maciej> performance hit for non-trivial installs.
Then maybe you could bypass install-strip using something like
./configure LDFLAGS=-s
make
make install
[...]
--
Alexandre Duret-Lutz
rtant.
Tom> However, beliefs are not intrinsically useful. Can we find a more
Tom> rational basis for making this decision?
A survey of all the GNU packages? (though it's out of topic
here, I would really be interested in knowing the proportion
of autoconfiscated packages use Automake).
--
Alexandre Duret-Lutz
if that word exists :) Something similar to this was
done before we decided to use install-sh unconditionally, and
the selection of install-sh versus install led to very ugly
Makefile constructs involving submake evaluations to preserve
relative filenames and the like.
I'd really prefer the MAYBE_STRIP solution suggested in a
separate mail.
--
Alexandre Duret-Lutz
>>> "Maciej" == Maciej W Rozycki <[EMAIL PROTECTED]> writes:
Maciej> On 28 May 2001, Alexandre Duret-Lutz wrote:
[...]
>> install binaries using the system's install, and strip them
>> afterward.
[...]
Maciej> What if INSTALL_PROGRAM='$
ch depend on
generated headers in another directory; it usually happens that
I'm building the sources with out-of-date headers by error.
(yeah, sounds like a reason to try Automake with a single
toplevel Makefile.am).
[...]
--
Alexandre Duret-Lutz
. has another idea? (I'm
thinking that maybe automake could figure `bar/foo' from the
include path, and do something helpful with that...).
--
Alexandre Duret-Lutz
>>> "Richard" == Richard Boulton <[EMAIL PROTECTED]> writes:
Richard> On Fri, Jun 01, 2001 at 11:16:45AM +0200, Alexandre Duret-Lutz wrote:
>> There is something nice about having one Makefile.am in each
>> subdirectory, it's that it helps t
s.com/dev/tech/tools/emulator/#source)
You will need CVS automake for doing that.
[...]
--
Alexandre Duret-Lutz
= ${prefix}
@@ -46,7 +46,7 @@
INSTALL = /usr/bin/install -c
INSTALL_PROGRAM = ${INSTALL}
INSTALL_DATA = ${INSTALL} -m 644
-INSTALL_SCRIPT = ${INSTALL_PROGRAM}
+INSTALL_SCRIPT = ${INSTALL}
INSTALL_HEADER = $(INSTALL_DATA)
transform = s,x,x,
NORMAL_INSTALL = :
~/tmp/am-test % Err 1 #32
[...]
--
Alexandre Duret-Lutz
atically (well, actually just
reprocessing the Makefiles) when such case is detected? The
patch below does that. Yeah, this sounds as ugly as processing
a LaTeX file in loop until all references are resolved :(
[...]
2001-09-22 Alexandre Duret-Lutz <[EMAIL PROTECTED
it in a similar way, without playing with
directories.
| noinst_PROGRAMS = tester @extra_tests@
| EXTRA_PROGRAMS = sdl_test
|
| tester_SOURCES = tester.c
| tester_LDADD = ../src/libmousetrap.la
| sdl_test_SOURCES = sdl_test.c
| sdl_test_LDADD = ../src/libmousetrap.la -lSDL -lSDL_image
[...]
--
Alexandre Duret-Lutz
ybe 2. is what you were looking for some time ago?]
--
Alexandre Duret-Lutz
Hi Sebastian,
>>> "Sebastian" == Sebastian Huber <[EMAIL PROTECTED]> writes:
[...]
Sebastian> noinst_PROGRAMS = index.html
index.html is not a program :), use
noinst_DATA = index.html
[...]
--
Alexandre Duret-Lutz
sions of themselves. (That's not the case here;
for instance the configure.ac shipped with Autoconf 2.50 can't
be compiled by 2.13.)
(This said, I'm among the people who don't put generated files
in CVS for their projects ; and I'm embarassed each time I need
to edit the output of 'cvs diff' to remove generated files, as
it happens with Automake.)
--
Alexandre Duret-Lutz
?
-c == copy the file (i.e. don't move it).
--
Alexandre Duret-Lutz
$target is the platform your program should output code for,
not the platform your program should run on (this is $host).
Actually, many packages mistakenly use $target instead of $host.
(I beleive this is because the Autoconf manual shows only a
'case $target' example.)
--
Alexandre Duret-Lutz
cd to the directory you want to
build your files into and run your configure from there.
E.g., if your package is in ~/package you can build it into
~/build with: cd ~/build; ~/package/configure; make.
--
Alexandre Duret-Lutz
utomake will infer it from the .k.o rule below)
[...]
> # compilation of *.k
> .k.o:
> $(KC) -c $(KFLAGS) $<
[...]
Index: ChangeLog
--- ChangeLog
+++ ChangeLog
@@ -1,1 +1,9 @@
+2001-11-01 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
+
+ * automake.in (handle_single_transform_
ding '.o' where sometime you want '.lo'.
--- ChangeLog
+++ ChangeLog
@@ -1,1 +1,11 @@
+2001-11-02 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
+
+ * automake.in (handle_single_transform_list): Pass $nonansi_obj to
+ derive_suffix. Don't use an hardcoded '
On Thu, Oct 18, 2001 at 05:25:27PM -0400, C. Scott Ananian wrote:
[...]
> ASCOMPILE = $(AS) $(AM_ASFLAGS) $(ASFLAGS)
> LTASCOMPILE = $(LIBTOOL) --mode=compile $(AS) $(AM_ASFLAGS) $(ASFLAGS)
> [...]
> .S.o:
> $(ASCOMPILE) -c `test -f $< || echo '$(srcdir)/'`$<
>
> .S.obj:
> $(ASCOMPILE)
On Thu, Oct 04, 2001 at 06:50:27PM +0200, Pontus Lidman wrote:
> Hello,
>
> I'm trying to use automake 1.4a in a project where we build some Linux
> kernel modules. These modules are partially linked objects, i.e. .c is
> compiled to .o and these objects are linked using ld -r to produce the
> ke
the reason why AS=$(CC) is so that Automake
can handle *.s and *.S as the same language and let $(CC) decides
whether the file needs being preprocessed or not.
C> You've found your bug. Please fix it. --s
--
Alexandre Duret-Lutz
ce `make check' is finished.
Index: ChangeLog
===
RCS file: /cvs/automake/automake/ChangeLog,v
retrieving revision 1.1650
diff -u -r1.1650 ChangeLog
--- ChangeLog 2001/11/09 16:27:24 1.1650
+++ ChangeLog 2001/11/09 16:47:10
n fixed one week ago. I bet your copy of 1.5a is
older than that.
[...]
--
Alexandre Duret-Lutz
ge must support this (it's the case if you
Christophe> don't do anything particular).
What about
make DESTDIR= install
That's exactly what DESTDIR is meant for.
[...]
--
Alexandre Duret-Lutz
e the same two
issues you describe, however they address them differently.
--
Alexandre Duret-Lutz
source) I
believe you don't need BUILT_SOURCE at all: your program depends
on its sources, and Make knows how to build the missing files
using the rule you added.
[...]
--
Alexandre Duret-Lutz
> /usr/share/automake/am/depend2.am: AMDEP does not appear
Adam> in AM_CONDITIONAL
Did you run 'aclocal' before running 'automake'? You should :)
[...]
--
Alexandre Duret-Lutz
dist && $one_name !~ /^nodist_/)
- || (! $default_dist && $one_name =~ /^dist_/));
+ $dist_p = (($default_dist && $nodir_name !~ /^nodist_/)
+ || (! $default_dist && $nodir_name =~ /^dist_/));
$nodir_name =~ s/^(dist|nodist)_//;
}
--
Alexandre Duret-Lutz
le1.h
include2_HEADERS = dir2/file2.h
[...]
--
Alexandre Duret-Lutz
adl> 2001-10-16 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
adl> * automake.in (am_install_var): Don't strip nobase_ from $X, do
adl> this with $nodir_name only.
Here is an update of this patch, which, I beleive, should fix
the bug reported by Braden McDaniel about nodist
>>> "Braden" == Braden McDaniel <[EMAIL PROTECTED]> writes:
[...]
Braden> So I tried nodist_noinst_HEADERS. This had the unexpected effect of
Braden> installing the headers in the root directory!
Could you try CVS Automake ? This ought to work now.
--
Alexandre Duret-Lutz
), I created a Makefile.am.
Mike> Unfortunately, prog_CFLAGS do not get used in the
Mike> resulting Makefile. Any ideas on what I'm doing wrong?
What Automake version are you using?
Both Automake 1.5 and the current CVS version seem to generate a
correct Makefile.in for your example.
--
Alexandre Duret-Lutz
mpiCC $(AM_CXXFLAGS) $(CXXFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@
(Setting `CXXLD=mpiCC' would achieve the same result, but
`CXXLD' is not documented.)
It's also possible to select the linker command on a per-program
basis (grep the manual for `maude_LINK').
--
Alexandre Duret-Lutz
ar ...
EXTRA_PROGRAMS = foo bar ...
foo_SOURCES = foobar.c foo.h
foo_CFLAGS = -DNAME=foo
bar_SOURCES = foobar.c bar.h
bar_CFLAGS = -DNAME=bar
...
--
Alexandre Duret-Lutz
Scratch that. AM_INIT_AUTOMAKE will do it for you.
G> AC_CONFIG_FILES([Makefile])
G> AC_OUTPUT(db_access/Makefile db_access_new/Makefile)
AC_CONFIG_FILES([Makefile db_access/Makefile db_access_new/Makefile])
AC_OUTPUT
[...]
--
Alexandre Duret-Lutz
occurence of "a_CFLAGS".
> Am I doing something wrong? I have a feeling that _CFLAGS is not supported
> with my version.
Yes, per-target CFLAGS is a new feature of Automake 1.5.
(Marko, sorry for my private reply; the mailer I'm using right now sucks.)
--
Alexandre Duret-Lutz
Fausto> process? Has anybody
Fausto> does this?
You can strip your binaries while they are installed with
make install-strip
If your package supports cross-compilation don't forget to add
AC_CHECK_TOOL([STRIP],[strip])
to your configure.ac.
--
Alexandre Duret-Lutz
non alphanumeric characters in your library name are
transformed into `_' to form the macro name. This includes the
`.', but also the `+'. So try `libhelp___a_SOURCES' instead.
--
Alexandre Duret-Lutz
fix this: either teach `depcomp' to stick
`-Wc,' or `-Xcompiler' before dependency tracking options when
running libtool (some depcomp modes such as aix already do that
properly), or teach `libtool' to ignore options (`-*') when
updating $srcfile. Which one seems more sensible? both?
--
Alexandre Duret-Lutz
$(F77COMPILE) -c -o $@ `test -f $< || echo '$(srcdir)/'`$<
|
| .f90.obj:
| $(F77COMPILE) -c -o $@ `cygpath -w $<`
Blah!
I think the idea behind make_paragraphs is that each rule should be
in a paragraph. However this doesn't work if `if'/`else'/`endif' are
handled on a paragraph basis but yet allowed _in_ a rule.
IMHO, Automake should be changed to work on a line by line basis
(i.e. not paragraph) and let file_contents_internal accumulate
the lines for a rule. Other opinions?
[...]
--
Alexandre Duret-Lutz
+++ ChangeLog
@@ -1,1 +1,8 @@
+2001-12-27 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
+
+ * lib/am/install.am (install-strip): Set INSTALL_STRIP_FLAG=-s,
+ it is needed by install-%DIR%LTLIBRARIES in ltlib.am.
+ This fixes a bug introduced on 2001-01-28.
+ Repor
the texinfo building stuff assumes that there
Bruce> is no documentation.
That's another issue, isn't it? What do you think about this
unanswered bug report:
http://sources.redhat.com/ml/bug-automake/2001/msg00423.html
(personally I'd vote for solution 5)
[...]
--
Alexandre Duret-Lutz
implemented. And presently if you override the .m.o
rule you are likely to obtain a broken Makefile: see the
``Redefined extension caused problems'' thread.
--
Alexandre Duret-Lutz
o exercise this function..
Index: ChangeLog
--- ChangeLog
+++ ChangeLog
@@ -1,1 +1,9 @@
+2002-01-03 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
+
+ * automake.in (file_contents_internal): Introduce two variables,
+ $is_rule and $discard_rules to track rules spanning acro
Ted> configure does a prior check of gcc with -c and -o, and
Ted> that passes.
Ted> I have no idea why the configure check is using CFLAGS instead of
Ted> CXXFLAGS. I changed the CXXFLAGS in ACX_CXXCOMPILE to
Ted> AM_CXXFLAGS, but that made no difference.
It seems this was fixed a few days after libtool 1.4b was
announced. Can you try CVS libtool?
[...]
--
Alexandre Duret-Lutz
/automake) or CVS Automake if
you need this.
[...]
--
Alexandre Duret-Lutz
tory when installing
Daniel> config.conf.
1.5b seems to work fine.
[...]
--
Alexandre Duret-Lutz
avoc> while (@arglist)
Havoc> {
Havoc> if ($arglist[0] =~ /^--acdir=(.+)$/)
It seems you'd better move that `push' after the `while' loop,
otherwise the files in @datadir@/aclocal will override the user
files (the converse is expected).
--
Alexandre Duret-Lutz
ChangeLog 2002/01/12 17:38:55 1.1723
+++ ChangeLog 2002/01/12 18:30:43
@@ -1,5 +1,12 @@
2002-01-12 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
+ * m4/init.m4 (AM_INIT_AUTOMAKE): Set PACKAGE and VERSION from
+ AM_INIT_AUTOMAKE arguments when using the old-style call.
+
n't think such dependency exists. Third-party m4 macros are
usually dependent upon Autoconf, not Automake. I'm sure Akim
will write "aclocal should belong to Autoconf" if he posts a
message in that thread .
[...]
--
Alexandre Duret-Lutz
e "s,\`test -f \\\$< || echo '\\\$(srcdir)/'\`\\\$<,\\\$<," < $m > $m.tmp
mv $m.tmp $m
done
changequote([, ])dnl
])
--
Alexandre Duret-Lutz
>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
[...]
adl> EXTRA_PROGRAMS = ex1 ex2
adl> ex1_SOURCES = ex1.cpp
adl> ex2_SOURCES = ex2.cpp
adl> check-examples: $(EXTRA_PROGRAMS)
Or even:
check_PROGRAMS = ex1 ex2
ex1_SOURCES = ex1.cpp
ex2
ppens with make install and make dist ?
This should distribute the sources and install nothing.
--
Alexandre Duret-Lutz
e Makefile'.
This way if a user runs GNU make all the rules from GNUmakefile
and Makefile will be used, otherwise only Makefile will be read.
(Projects like fileutils, textutils, shellutils, autoconf,
and bison, use a similar setup.)
--
Alexandre Duret-Lutz
mumble.la' Automake knows that
`mumble.la' will be installed in `$(foodir)'; but from
`EXTRA_LTLIBRARIES = mumble.la' it cannot know where the
`mumble.la' will be installed, it could be somewhere else (so
this justifies the error message). In the latter case, you have
to play some _LDADD trickery to add the right -rpath flag
manually, as said in the Automake manual.
--
Alexandre Duret-Lutz
TARNAME-AC_PACKAGE_VERSION.tar.gz
which would result in
GNU-Foo-Bar-1.0-1.0.tar.gz
[...]
--
Alexandre Duret-Lutz
601 - 700 of 920 matches
Mail list logo
