>>> "Lars" == Lars Hecking <[EMAIL PROTECTED]> writes:
[...]
Lars> Does anyone have any better suggestions?
Maybe you could group these objects in a convenience library in
order to use per-target flags.
--
Alexandre Duret-Lutz
convert directly to
Duncan> 'automake'.
I've filled two PR for this:
PR/371: to fix Automake so it understand this construct
PR/372: to warn about this construct, because it's disallowed by POSIX
[...]
--
Alexandre Duret-Lutz
gt; a lot more flexible. Ideas?
I think this would be nice; however it's probably more difficult
than you might think...
--
Alexandre Duret-Lutz
Pekka> remove the lines not to be included.
Sorry, I forgot to reply to this. A simpler solution is to use
a sub-variable.
FILES = somefile.c $(FILES_IF_SOMETHING) $(FILES_IF_SOMETHING_ELSE) something.c
if HAVE_SOMETHING
FILES_IF_SOMETHING = someotherfile.c
endif
if HAVE_SOMETHING_ELSE
FILES_IF
tely there are other problems lurking.
Thanks for the detailed analysis. I've submitted this is PR/374
because it doesn't look easy to fix.
As a workaround I think you could use `cpp' instead of `cp' in
the above rule.
[...]
--
Alexandre Duret-Lutz
e trace this script with `sh -x ./configure --your-flags...'
and send the output to [EMAIL PROTECTED]
--
Alexandre Duret-Lutz
erry> foo_SOURCES = @MY_SOURCES@
You can do this if you list the possible values of @MY_SOURCES@ in
EXTRA_foo_SOURCES = foo.c foo.h ...
Jerry> foo_LDADD = @HOW_ABOUT_THIS@
If @HOW_ABOUT_THIS@ contains object or libraries, you'll also
want to redefine foo_DEPENDENCIES (grep the manual for
maude_DEPENDENCIES).
--
Alexandre Duret-Lutz
cluded from elsewhere.
(Unless inclusions of fragments defining default variables are
done at the end of Makefile.am -- but this raises a few other
issues.)
[...]
[*] IIRC someone once sent a patch against Automake to introduce
`?=' as "assign and allow future redefinitions".
--
Alexandre Duret-Lutz
tation:
|
| htmldir = $(prefix)/html
| html_DATA = automake.html
--
Alexandre Duret-Lutz
AULT_INCLUDES = -I. -I$(srcdir)"
Tim> Don't know that,
The third -I gives the search path for config.h.
[...]
Tim> There's no harm in -I . -I . -I . as far as I know.
FWIW, spaces between `-I' and `.' are not portable. For instance
in this case OSF's cc will handle `.' as a source file.
[...]
--
Alexandre Duret-Lutz
as fixed in
Automake 1.7 (If you have www access you can find this thread by
searching the list archive for your error message).
--
Alexandre Duret-Lutz
gt; is created.
Someone would have to add DocBook support to Automake. Would
you be the guy? http://sources.redhat.com/automake/contribute.html
--
Alexandre Duret-Lutz
ics.
If that doesn't help please send details about what you do; it's
hard to guess what could be wrong... (If you have no idea what
kind of details we'd like to see, read
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html)
--
Alexandre Duret-Lutz
piled if any of these files change.
That's the purpose of dependency tracking.
miki> AFAIK, it's not mandatory to mention them during compilation
Huh? We don't do this. dependencies != sources
[...]
--
Alexandre Duret-Lutz
by Rick Delaney and M.J.T. Guy)
Branch: maint-5.6/perl
!> t/pragma/warn/toke toke.c
So the bug is that Perl 5.6.0's "=>" operator doesn't quote the previous
word if separated by a
ll. However, this is only detected after the
Alexandros> fist "make" command.
Generated headers are almost always an issue for dependency
tracking.
Try adding the following and see if that helps.
BUILT_SOURCES = parser.h
[...]
--
Alexandre Duret-Lutz
CXXLD vs CCLINK and CCLD).
You can override the LINK command on a per-program basis:
bin_PROGRAMS = foo
foo_SOURCES = foo.c
foo_LINK = $(CXX) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@
--
Alexandre Duret-Lutz
me to moderate the list.
If your mail was blocked, it's lost.
[...]
--
Alexandre Duret-Lutz
done.
See the following if you want an explanation why we need
Netstable at the moment.
http://mail.gnu.org/pipermail/automake-patches/2002-October/001239.html
I don't know what you use CVS Automake for. Wouldn't tracking
branch-1-7 be more appropriate?
--
Alexandre Duret-Lutz
Patrick> &variable_value('MAKEFILE-AM-INSTALLDIRS'), then
Patrick> 'MAKEFILE-AM-INSTALLDIRS' => variable_value('am__installdirs').. ?
Patrick> ?
I don't understand what you mean.
I think Perl is just asking for quote around am__installdirs,
although I don't know why.
--
Alexandre Duret-Lutz
mething like `*.o'; second, it should not output
`-L../autoopts/.libs -lopts' but `../autoopts/libopts.la'
since Bruce said `autogen_LDADD = $(top_builddir)/autoopts/libopts.la'.
I'm tempted to think that the link rule was hand-edited (either in the
Makefile(|.in|.am), or in the output).
[...]
--
Alexandre Duret-Lutz
>>> "Bruce" == Bruce Korb <[EMAIL PROTECTED]> writes:
Bruce> Alexandre Duret-Lutz wrote:
>> >> /bin/sh ../libtool --mode=link gcc -g -O2 -L/sw/lib -o autogen \
>> >> -export-dynamic -lguile *.o -L/sw/lib -lguile -lm \
>> >&
ur project to use ccache? Do you tell
./configure that you want to use ccache as the compiler? (you should).
--
Alexandre Duret-Lutz
No files given to ../config/py-compile
Sebastian> make[2]: *** [install-nodist_pythonPYTHON] Error 1
This as fixed in Automake 1.7.1. (See PR/369 for details.)
[...]
--
Alexandre Duret-Lutz
>>> "Alexei" == Alexei Lioubimov <[EMAIL PROTECTED]> writes:
Alexei> Hello,
Alexei> Is there any document describing AUTOMAKE version numbering scheme?
http://sources.redhat.com/ml/automake/2002-08/msg6.html
--
Alexandre Duret-Lutz
automagically do the right thing?
Right now this seems hard. I've submitted this as PR/376, so we
don't forget about it eventually. Fortunatelly it's more
frequent that dependent libraries get installed in the same
directory.
--
Alexandre Duret-Lutz
$1, [\\\n]),
[[\n\t ]+], [ ]),
[ *$]),
[^ *\(.*\)], [[\1]])])
--
Alexandre Duret-Lutz
M4. See
http://sources.redhat.com/ml/bug-automake/2002/msg02090.html
--
Alexandre Duret-Lutz
mail stops at this point in the middle of a sentence.
--
Alexandre Duret-Lutz
Hi people!
Here is a snapshot of the 1.7.x branch of Automake.
ftp://sources.redhat.com/pub/automake/automake-1.7.1b.tar.bz2
ftp://sources.redhat.com/pub/automake/automake-1.7.1b.tar.gz
This should be reasonably close to what 1.7.2 will be.
Please test it and report any problem you have,
so
ne of them?)
[...]
Yep. Thanks! I'm installing the following patch on HEAD and branch-1-7.
2002-12-02 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* automake.texi (Options): Programs listed in
AM_INSTALLCHECK_STD_OPTIONS_EXEMPT should have $(EXEEXT) appended.
* tes
| 2002-12-02 Charles Wilson <[EMAIL PROTECTED]>
|
| * tests/gnits3.test (AM_INSTALLCHECK_STD_OPTIONS_EXEMPT):
| Append $(EXEEXT) again.
Thank you. It's committed.
--
Alexandre Duret-Lutz
ound. I
DB> downloaded and installed autoconf2.57, rebooted but still the same
DB> msgs. I am new at linux and runnong SuSE 8.0 Pro.
Is the new autoconf in your PATH?
What does `autoconf --version' print?
--
Alexandre Duret-Lutz
condobjs="$condobj mod_cat.$(OBJEXT)"
test "x$needs_mode_cmp" = xyes && condobjs="$condobj mod_cmp.$(OBJEXT)"
test "x$needs_mode_fix" = xyes && condobjs="$condobj mod_fix.$(OBJEXT)"
...
AC_SUBST([condobjs])
Then use $(condobjs) to fill shntool_LDADD and
shntool_DEPENDENCIES in Makefile.am.
--
Alexandre Duret-Lutz
We're pleased to announce the release of Automake 1.7.2
This is a bug fix release. The list of bug fixes is appended.
You can find the new release here:
ftp://ftp.gnu.org/gnu/automake/automake-1.7.2.tar.bz2
ftp://ftp.gnu.org/gnu/automake/automake-1.7.2.tar.gz
ftp://sources.redhat.com
Automake 1.5 is old.
Does it still fail with Automake 1.7.2?
[...]
--
Alexandre Duret-Lutz
directory.)
What's wrong with Windows compilers? Is there anything we could
fix in Automake to make generated Makefiles more portable?
[...]
--
Alexandre Duret-Lutz
it's better to list these files in
EXTRA_shntool_SOURCES. This will help Automake to generate
compilation rules and setup automatic dependency tracking for
these files, or chose the right linker to use for shntool.
[...]
--
Alexandre Duret-Lutz
E@@am__include@ @am__quote@./$(DEPDIR)/foo.Po@am__quote@
* create empty dependency files from config.status
[...]
--
Alexandre Duret-Lutz
en a lex5 failure reported against 1.7.2
recently, but it's pending details. Maybe this is the same.
Could you send the output of the following command?
make TESTS=lex5.test VERBOSE=x check
--
Alexandre Duret-Lutz
>>> "John" == John Levon <[EMAIL PROTECTED]> writes:
[...]
John> make distcheck fails by default, but if I could pass in a configure
John> option, it would work. Can I do this ?
Starting with Automake 1.6 you can set DISTCHECK_CONFIGURE_FLAGS.
[...]
--
Alexandre Duret-Lutz
he source tree.
You could declare everybody using `noinst_SCRIPTS', and install
them using a custom `install-exec-local' rule.
[...]
--
Alexandre Duret-Lutz
>>> "Patrick" == Patrick Welche <[EMAIL PROTECTED]> writes:
Patrick> Just got (fresh cvs):
Patrick> ERROR: files left in build directory after distclean:
Patrick> ./version7-3.141.tar.gz
Thank you. I'm checking this in.
2002-12-13 Alexandre Duret-Lut
ngs by
Markus> intel's C++ 7.0. Any idea how to remove these via
Markus> configure.in or Makefile.am?
Maybe your are not setting the compiler early enough? Since
./configure decides which flags to use it must know the
compiler. Therefore you should run
./configure CC=mycc; make
not
./configure; make CC=mycc
--
Alexandre Duret-Lutz
lid unused variable name: `GST_PLUGIN_LDFLAGS'
Hi Thomas,
This was fixed in Automake 1.6.1.
[...]
--
Alexandre Duret-Lutz
sual way
to emulate per-object flags is to compile the file in
a static library and use per-libary flags.
[...]
--
Alexandre Duret-Lutz
ode, it seems it would not output -k
either. I don't think it should. Some make implementation will
always terminate with exit code 0 when `-k' is used, hiding any
failure.
--
Alexandre Duret-Lutz
, use
AM_INIT_AUTOMAKE([libgtkbonus], [0.1], [non-empty-argument--see-manual])
[...]
--
Alexandre Duret-Lutz
does
icpc's -M option work? Are these warnings output to stdout or
stderr? Is there any icpc-specific environment variable that can
be set to turn warnings into errors?
--
Alexandre Duret-Lutz
HEAD and branch-1-7. This gets rid of
the aclocal call entirely.
Index: ChangeLog
===
RCS file: /cvs/automake/automake/ChangeLog,v
retrieving revision 1.2024.2.69
diff -u -r1.2024.2.69 ChangeLog
--- ChangeLog 31 Dec 2002 21:25:34 - 1.2024.2.69
+++ ChangeLog 5 Jan 2003 2
cently started to substitute
@abs_srcdir@ and @abs_top_srcdir@ (they do not get defined as
Makefile variables, but you could do this yourself), however
generally it's better to avoid using absolute paths.
--
Alexandre Duret-Lutz
stalls in /bin as it seems you want.
Using $(exec_prefix) to defines $(usrbinexecdir) makes sure the
user still gets the expected result with `make prefix=/tmpdir
install'. Using `exec' in the name of the `usrbinexecdir' variable
ensures `xyz' will be installed by `install-exec', not `install-data'.
--
Alexandre Duret-Lutz
ady defined in
Harlan> condition TRUE, which implies COND_FOO).
Harlan> Bug or feature?
Maybe both.
http://mail.gnu.org/archive/html/automake/2002-09/msg00054.html
http://mail.gnu.org/archive/html/automake/2002-10/msg00018.html
Comments welcome!
--
Alexandre Duret-Lutz
Wouldn't it be better to teach Automake to byte-compile all
files at once rather than one at a time? I'm willing to do this
if people agree. My impression is that the reason why Automake
byte-compile files one at a time is that it's easier to write
Makefile rules this way. (Make's semantics make it tricky to
write rules with multiple outputs.)
[...]
--
Alexandre Duret-Lutz
the test case. This looks fine to me, but as I don't
really know emacs-lisp I can't tell for sure.
2003-01-08 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
Build elisp files all at once instead of one by one.
* automake.in (handle_emacs_lisp): Define am__ELFILES.
Harald> Makefile, but could not find any;
Harald> I have no idea how to define one myself;
Something like this?
check-new: $(TESTS)
$(MAKE) $(AM_MAKEFLAGS) TESTS='$?' check-TESTS
: > $@
CLEANFILES = check-new
--
Alexandre Duret-Lutz
illiam> _CXXFLAGS which do not get passed to the
William> linker. Is this all as intended?
I agree this is a bug. We should honor per-target compiler
flags at link time for consistency.
--
Alexandre Duret-Lutz
>>> "Braden" == Braden McDaniel <[EMAIL PROTECTED]> writes:
Braden> GNU make doesn't agree.
I hear you, but that no reason: Automake follows the GNU Coding
Standards in this case.
--
Alexandre Duret-Lutz
entence in the `Variables for Specifying Commands'
section (sorry I don't have section number in the info version).
| `CFLAGS' should be used in every invocation of the C compiler, both
| those which do compilation and those which do linking.
--
Alexandre Duret-Lutz
undaryConditions.C
`euler_SOURCES' defaults to `euler.c' if you don't define it.
No wonder Automake asks for a compiler. Just define it as empty
to get rid of the error message.
[...]
--
Alexandre Duret-Lutz
`Makefile' fragment that you will `include' in all the
relevant `Makefile.am's. See the `Include' section of the
manual for the syntax.
huangwei> I have set the top directory makefile, but it seem
huangwei> that the makefiles in the subdirectory can't be set.
Indeed. There is no "variable inheritance" between `Makefile's.
--
Alexandre Duret-Lutz
real problem is why your script
lose its executable bit, not how to set it back.
--
Alexandre Duret-Lutz
e $(SHELL) Makefile variable is AC_SUBST'ed by
./configure, fortunately it doesn't come from the environment.
(Still there are broken make implementations that will use the
SHELL envvar when run as `make -e'. Details in the Autoconf
manual.)
--
Alexandre Duret-Lutz
ns presently is that `distclean' will remove the
core, so we'll not notice it when checking for spurious files in
the build tree. Although the build will probably go wrong
anyway, I'm not a supporter of things that may conceal bugs.
--
Alexandre Duret-Lutz
int i; }'`; \
test -z "$tags$unique" \
|| etags\
$tags $unique
Looks like it works for me.
Which version of Automake are you complaining about?
--
Alexandre Duret-Lutz
ht I might as well try to hack
>> automake's Java support.
Eric> Cool!
Seconded! (Although I can't make any technical comments
regarding Java as eric did.)
Simon, please, start here: http://sources.redhat.com/automake/contribute.html
--
Alexandre Duret-Lutz
ike $(propertiesdir).
Is this still true if subdirectories are not used? (Like when
we build _LIBRARIES.)
Simon> but I don't think that's a major issue
Neither do I. AFAICT the major hindrance is the Automake guts.
(Hopefully that's an occasion to do some cleaning.)
[...skipping Java issues I can't comment on...]
--
Alexandre Duret-Lutz
he
Sander> _AC_AM_HEADER_HOOK macro.
We can discuss this later when the Autoconf maintainer is back.
[...]
2003-02-04 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* m4/init.m4 (_AC_AM_CONFIG_HEADER_HOOK): Recompute
indexes of header files so we create stamp files with
#x27; (*note Sources::) as follows.
|
| BUILT_SOURCES = parser.h
| AM_YFLAGS = -d
| bin_PROGRAMS = foo
| foo_SOURCES = ... parser.y ...
--
Alexandre Duret-Lutz
>>> "Simon" == Simon Richter <[EMAIL PROTECTED]> writes:
Simon> This document says that the CVS tree is on sources.redhat.com, is that
Simon> still the case (I got my working tree from subversions)?
subversions mirrors sources.redhat.com. I don't know how often.
--
Alexandre Duret-Lutz
retty sure some people will
think I'm unfair in some places. Let me know.
Cheerio,
Alexandre Duret-Lutz
--- snip --- snip --- snip ---
Frequently Asked Questions about Automake
*
This chapters covers some questions that often come up on the ma
ype `cvs add -ko ...'), but I've always been beaten
by this timestamp lossage.
Thanks to you, I'm relieved to learn it doesn't happen with
`cvs checkout'.
Ronald> In any case, CVS is a versioning tool, not a
Ronald> distribution tool. For me, that means that it makes
Ronald> sense not to have generated files in the CVS
Ronald> repository.
I'll try to make your point in the relevant section.
Thanks for your comments.
pip-pip
--
Alexandre Duret-Lutz
Here is a rewrite of this CVS/timestamp section.
I hope it's more accurate.
Background: CVS and timestamps
--
Unless you use CVS keywords (in which case files are rewritten before
commit), CVS preserves timestamp during `cvs commit' and `cvs import
-d' operations.
if there are no
Bruce> texi files, then there can be no texi documentation. This is
Bruce> a mistake. I've been told that the texi rules come from the texi
Bruce> folks, so it's not Automake's job to fix it. It's still a problem.
Fixing the rules for building .info files is cleary Automake's job.
Could you fill a PR with an example of what you are trying to achieve?
(I'm not sure I understand what you want.)
--
Alexandre Duret-Lutz
. That's what distcheckclean checks. So I'd really
want to understand why you think differently (appart from giving
us occasions to talk, that is :)). So far I've failed to get
your point.
BTW, autogen.info is not rebuilt the first time I run `make' in
Autogen (5.4.8), but it gets rebuilt if I run `make' a second
time. Looks weird. Is this intended? I'm sorry I don't
understand why this happens.
Ciao,
--
Alexandre Duret-Lutz
compilation.
Markus> What went wrong?
Nothing as far as I can tell.
Please send more details if dependencies really aren't updated
during build (don't forget to say which version of Automake you
are and were using, especially if something "vanished").
[...]
--
Alexandre Duret-Lutz
SHELL@'
where @SHELL@ is the shell computed by ./configure
Or is this something DJGPP users should stick in their
environment?
The issue doesn't seem limited to automake. For instance
autoupdate will calls autoconf using arguments like
"--trace define:'AC:\$f:\$1'".
[...]
--
Alexandre Duret-Lutz
fore defining $ENV{'SHELL'}
Richard> to be @SHELL@).
Thanks. I'm installing the following change on HEAD and branch-1-7.
2003-02-10 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* automake.in (BEGIN): Override $ENV{'SHELL'} with ./configure's
afford reading each tool's list, but still would like to
hear about new releases, or are willing to test pre-releases. If you
know such people, please tell them.
You can subscribe here:
http://mail.gnu.org/mailman/listinfo/autotools-announce
Cheers,
--
Alexandre Duret-Lutz
example and not with the default 'all' or 'all-am'.
Patrick> Is there a way to do that?
No friendly way.
--
Alexandre Duret-Lutz
oteworthy manual updates:
- New FAQ chapter.
- Document how AC_CONFIG_AUX_DIR interacts with missing files.
(Debian Bug #39542)
- Document `AM_YFLAGS = -d'. (PR/382)
--
Alexandre Duret-Lutz
missing mkinstalldirs
Any idea when these files get installed?
Are they installed by `make install'? (i.e., outside distcheck')
--
Alexandre Duret-Lutz
ow stamp files are numbered.
Sander> I'm currently considering to let configure create a separate foo.h in
Sander> each of the directories that need foo.h (through a
Sander> AC_CONFIG_HEADERS([dir1/foo.h:inc/foo.h.in dir2/foo.h:inc/foo.h.in]),
This looks safer.
[...]
--
Alexandre Duret-Lutz
ncy of distcheck. Any ideas
Robert> why this is happening? I began to look into this
Robert> problem because another maintainer has not been able to
Robert> run "make distcheck" since he abandoned a much older
Robert> Automake.
Which version worked last?
[...]
--
Alexandre Duret-Lutz
>>> "Bruce" == Bruce Korb <[EMAIL PROTECTED]> writes:
Bruce> At the end of this log, you'll see lines like this:
Bruce> cp: cannot create regular file \
Bruce> `blocksort-1.4.2/libopts/.deps/save.Plo': Permission denied
Simply don't distribute these files.
--
Alexandre Duret-Lutz
000 +0100
@@ -337,6 +337,5 @@
AM_CONDITIONAL([NEED_LIBOPTS], [test -n "${LIBOPTS_DIR}"])
AC_SUBST(LIBOPTS_LDADD)
AC_SUBST(LIBOPTS_CFLAGS)
- AC_SUBST(LIBOPTS_DIR)
AC_CONFIG_FILES([libopts/Makefile])
]) # end of AC_DEFUN of LIBOPTS_CHECK
--
Alexandre Duret-Lutz
ibltdl/configure.in, and replace the above code by
AC_CONFIG_AUX_DIR([../tools]) so that Automake find its files.
If you decide to start shipping auxiliary files with libltdl,
then this code can be changed to AC_CONFIG_AUX_DIR([.]). I
suppose some people will mind about the extra kilobytes, though.
[*] To be fair, I guess it's harmless if you don't rerun
automake in the libltdl directory embeded in a package. However
I think it's quite common to do so, for instance `autoreconf' will
work recursively.
--
Alexandre Duret-Lutz
he 1.7.3 documentation has a paragraph about this, see
http://sources.redhat.com/automake/automake.html#Yacc%20and%20Lex
--
Alexandre Duret-Lutz
e/@sys/usr/lib/perl5/site_perl/5.8.0 /software/@sys/usr/lib/perl5/site_perl .)
at /software/@sys/usr/bin/autoupdate line 34.
Martin> BEGIN failed--compilation aborted at /software/@sys/usr/bin/autoupdate line
34.
autoupdate (= Autoconf) is failing here, so please report this to
[EMAIL PROTECTED]
--
Alexandre Duret-Lutz
nst_LIBRARIES = liball.a
liball_a_SOURCES = sub1/foo.c sub1/foo.h sub2/bar.c sub2/bar.h ...
(It's good style to list headers files in _SOURCES instead of
EXTRA_DIST, even if they aren't compiled.)
--
Alexandre Duret-Lutz
ntion as an invitation to use an m4/
directory in your project.
[...]
gd> It happens that there is no AUTOMAKE_OPTIONS environment
gd> variable either to add default-options.
Default options are better set in a Makefile. (I've got your
point with -I, but I'm answering the general case here.)
--
Alexandre Duret-Lutz
o, I you ever want to do this, it should read
dsiSecManager_SOURCES = file1.cpp ../../include/file1.h
(Or whatever PROJECT_ROOT_DIR is.)
--
Alexandre Duret-Lutz
elf, but if it has
Paul> already been done so much the better.
No idea. Have you asked the Qt people? Or did you finally worked it out?
--
Alexandre Duret-Lutz
lunteering to implement the second...
(*) I'm assuming _LIBRARIES and _LTLIBRARIES have been merged
first. This shouldn't be too hard to do, and actually I'd like
to do it, but it's unclear whether I'll have enought time to
commit to this before before mid-march.
[...]
--
Alexandre Duret-Lutz
the _PRIMARY. This gives room for handling other
suffixes.
[...]
--
Alexandre Duret-Lutz
the end of
http://article.gmane.org/gmane.comp.sysutils.automake.bugs/594
--
Alexandre Duret-Lutz
We're pleased to announce the release of Automake 1.7.3
This is a bug fix release. The list of bug fixes is appended.
You can find the new release here:
ftp://ftp.gnu.org/gnu/automake/automake-1.7.3.tar.bz2
ftp://ftp.gnu.org/gnu/automake/automake-1.7.3.tar.gz
ftp://sources.redhat.com
store the libtool library path into it temporarily?
Pavel> (yes, but where this value should come from... ?)
nah, it's libtoolize's job
--
Alexandre Duret-Lutz
il.gnu.org/archive/html/libtool/2001-02/msg00020.html
Does it answer your question? Otherwise, I suggest you write to
[EMAIL PROTECTED]
--
Alexandre Duret-Lutz
aradigm).
I suggest you install Automake 1.7.3 (any version >= 1.7 will
do), and run it with the -Wall option. This will flag various
unportable constructs in your Makefile.
If you fixes these (using `.idl.cpp:' instead of `%.cpp: %.idl',
using `$(idlsources:.idl=.cpp)' instead of `$(forall...)'), then
Automake should work better. At least it will see your sources,
so it can output rules to build them.
--
Alexandre Duret-Lutz
1 - 100 of 920 matches
Mail list logo
