also help to better test these uncertain subdir-suffix-rules.
Would that be enough?
--
Alexandre Duret-Lutz
like a waste of time for new feature. branch-1-8 tracks
only bug fixes, so the patch would have to be adapted to
HEAD before it can be installed there.
Regarding joint patches, this is delicate because the FSF
requires copyright assignments for significant changes.
--
Alexandre Duret-Lutz
; [*]. I believe this
apply to all Automake versions.
Could you give a more detailed example of what worked, when, and
how? "more places" is a bit fuzzy.
[*] I think this is not accurate if you limit yourself Solaris
or Tru64 Make. But I'm assuming you don't.
--
Alexandre Duret-Lutz
le is re-read after one of its included file
(here Makefile.order) has changed is a GNU Make idiom anyway.
[...]
--
Alexandre Duret-Lutz
>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
[...]
adl> [*] I think this is not accurate if you limit yourself Solaris
adl> or Tru64 Make. But I'm assuming you don't.
if you limit yourself _to_ Solaris and Tru64 Make.
--
Alexandre Duret-Lutz
all libraries, and once it is done relink all
libraries. Would that work? If so, we need a way to tell
libtool to copy libraries without relinking.
--
Alexandre Duret-Lutz
&& $(MAKE) $(AM_MAKEFLAGS) clean
# Assuming the package knows how to install itself
install-data-local:
cd subdir && $(MAKE) $(AM_MAKEFLAGS) install-data
install-exec-local:
cd subdir && $(MAKE) $(AM_MAKEFLAGS) install-exec
uninstall-local:
cd subdir && $(MAKE) $(AM_MAKEFLAGS) uninstall
# Distribute files from here.
EXTRA_DIST = subdir/Makefile subdir/program.c ...
Pushing this idea to the extreme, it is also possible to ignore the
subproject build system and build everything from this proxy `Makefile'.
--
Alexandre Duret-Lutz
; $(MAKE) $(AM_MAKEFLAGS) clean
# Assuming the package knows how to install itself
install-data-local:
cd subdir && $(MAKE) $(AM_MAKEFLAGS) install-data
install-exec-local:
cd subdir && $(MAKE) $(AM_MAKEFLAGS) install-exec
uninstall-local:
cd subdir && $(MAKE) $(AM_MAKEFLAGS) uninstall
# Distribute files from here.
EXTRA_DIST = subdir/Makefile subdir/program.c ...
Pushing this idea to the extreme, it is also possible to ignore the
subproject build system and build everything from this proxy
| `Makefile.am'. This might sounds very sensible if you need VPATH
| builds but the subproject does not support them.
--
Alexandre Duret-Lutz
is empty -- mkdir won't create "".)
It shouldn't be too hard to fix, but unfortunately it's bedtime :)
2004-01-27 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* Makefile.am (maintainer-check): Check for unquoted $(DESTDIR) uses.
* lib/am/data.am, lib/
case with full instructions to
reproduce the problem?
--
Alexandre Duret-Lutz
>>> "Rafael" == Rafael Laboissiere <[EMAIL PROTECTED]> writes:
[...]
Rafael> can I convince automake to look for the files at cf/,
Rafael> but still be run from the top_scrdir?
No.
--
Alexandre Duret-Lutz
X inference rules, automake can see that those
.hg and .ccg will be turned into .h and .cc, and can produce the
appropriate rules for them. (It doesn't work with %-rules -- it's
difficult enough to try supporting the portable constructs.)
Section `Handling new file extensions' of the manual (node
`Suffixes') should probably be extended with such an example.
--
Alexandre Duret-Lutz
efore `foo' is run, so that is has a
timestamp older than output files output by `foo'. It is then renamed
as `data.stamp' after `foo' has run, because we do not want to update
`data.stamp' if `foo' fails.
--
Alexandre Duret-Lutz
Thank you Robert, Eric, and Bruce.
I've installed it with your suggestions.
--
Alexandre Duret-Lutz
d.
That makes sense to me. _MODULES might be a bit too generic; perhaps
that could be
include_FCMODULES = dummy.mod
(Adding `.mod' does not make uppercasing really harder, but
I think it makes the Makefile.am more readable.)
--
Alexandre Duret-Lutz
ll the
most visible problem was that there was no test cases, and the
patch was against the bug fix branch of Automake 1.7. (New
feature should always go on CVS HEAD, and CVS HEAD is usually
different from the bug fix branch -- I suspect you had a bad day
upgrading to 1.8, didn't you?)
--
Alexandre Duret-Lutz
e or if I am supposed to be using
John> Gettext specifically to somehow handle this issue.
It's just an example. I've changed that paragraph to
If you have ever used Gettext in a project, this is a good example of
how third-party `Makefile's can be used with Automake. The `Makefile's
`gettextize' puts in the `po/' and `intl/' directories are handwritten
`Makefile's that implement all these targets. That way they can be
added to `SUBDIRS' in Automake packages.
--
Alexandre Duret-Lutz
sensible. But actually it's
superfluous: EXTRA_* is really useful when there are extra files
to distribute or extra compile rule to generate.
[...]
--
Alexandre Duret-Lutz
gt; But if I omit EXTRA_HEADERS (or if I use
Michael> nodist_EXTRA_HEADERS), then I get the following error
Michael> message:
Michael> f90/Makefile.am:11: `nodist_include_HEADERS' contains configure
Michael> substitution,
Michael> f90/Makefile.am:11: but `EXTRA_HEADERS' not defined
Well, so it is required then... Sorry for the confusion.
--
Alexandre Duret-Lutz
ke conditional?
What you describe works for me, it builds libMyLib.a iff
FEATURE is set.
--
Alexandre Duret-Lutz
and.
scriptdir = $(pkgvdatadir)
dist_script_DATA = config.guess config.sub install-sh mdate-sh missing \
mkinstalldirs elisp-comp ylwrap acinstall depcomp compile py-compile \
symlink-tree
install-data-hook:
@$(POST_INSTALL)
@for prog in $(dist_script_DATA); do \
echo " chmod +x $(DESTDIR)$(scriptdir)/$$prog"; \
chmod +x $(DESTDIR)$(scriptdir)/$$prog; \
done
[...]
--
Alexandre Duret-Lutz
ou still haven't answered the most basic
question: what automake version are you using?
>From the above indented output I believe you are running a
relic. Probably automake 1.4 or older. The last version is 1.8.2,
and what you do should work with 1.6 or later.
--
Alexandre Duret-Lutz
>>> "sbd" == Drummonds, Scott B <[EMAIL PROTECTED]> writes:
sbd> From: Alexandre Duret-Lutz [mailto:[EMAIL PROTECTED]
>> Sorry to insist, but you still haven't answered the most basic
>> question: what automake version are you using?
sbd>
is right?
Yes, but only in normal conditions, when all variables
definitions occur before the rule definitions. Automake ensures
this... provided it can recognize variable definitions (and as
you now know, 1.4 does not recognize indented variable
definitions).
--
Alexandre Duret-Lutz
in 1.4, it is a problem. If you clutter your
Makefile.ams with workarounds of all sorts, it is also a
problem.
--
Alexandre Duret-Lutz
Hi Eric,
Thanks for all your comments (public and private)!
>>> "Eric" == Eric Siegerman <[EMAIL PROTECTED]> writes:
Eric> On Sat, Jan 31, 2004 at 11:28:29PM +0100, Alexandre Duret-Lutz wrote:
>> One of the output (here `data.c') is used as a witness of
his is OK, because the bison
rules also try not to update the parser.h header file to speed
up recompilation. So we do not want the `touch' there either...
--
Alexandre Duret-Lutz
o
not know why they do. Is there any reason why upgrading to
newer Perl versions would be undesirable?
PS: I'd still fix Perl 5.005_03 issues in 1.8.x.
--
Alexandre Duret-Lutz
. You can say
./configure PERL='/usr/bin/env perl'
or
./configure PERL='/opt/perl-5.6/bin/perl'
when configuring Automake.
[...]
--
Alexandre Duret-Lutz
tem such as Solaris 8, whose make does not
support parallel builds, there is no reason not to use `mkdir
-p'. The problem only exist when users mix tools, doesn't it?
It's a bit of a shame, we have to disable `mkdir -p' everywhere
because of such setups.
Other ideas?
--
Alexandre Duret-Lutz
accepted by POSIX).
ELFILES = one.el two.el three.el ...
ELCFILES = $(ELFILES:=c)
elc-stamp: $(ELFILES)
@rm -f elc-temp
@touch elc-temp
$(elisp_comp) $(ELFILES)
@mv -f elc-temp $@
$(ELCFILES): elc-stamp
@if test -f $@; then \
touch $@; \
else \
rm -f elc-stamp; \
$(MAKE) $(AM_MAKEFLAGS) elc-stamp; \
fi
--
Alexandre Duret-Lutz
ade). Would someone *please* tell me
sbd> how and why I'm wrong? :)
You are not wrong. Recent versions do not have this problem.
--
Alexandre Duret-Lutz
>>> "sbd" == Drummonds, Scott B <[EMAIL PROTECTED]> writes:
[...]
sbd> Also, what exactly is the difference between --acdir and -I?
Please see section `Macro search path' of the manual.
--
Alexandre Duret-Lutz
ROGRAMS, well, I have written this in
Jose> configure.in:
Jose> PHAN3D = phan3D
This will run the command `PHAN3D' with `=' as first argument
and `phan3D' as second argument. Obviously you just wanted
to assigned the `phan3D' string to the `PHAN3D' shell variabl
attern rules here because they are not portable, but they can be
convenient in packages that assume GNU `make'.
--
Alexandre Duret-Lutz
hen
the GNU Coding Standards should also define a destination
directory for these other files. Something like $htmldir.
--
Alexandre Duret-Lutz
eeing your Makefile.am and how you start this
compilation.
Thomas> Are there known issues with cygwin, and automake-1.8.2?
No reports yet. Does the test suite pass?
--
Alexandre Duret-Lutz
way by the Solaris sh. In
Mark> particular the ": > sub/conftst$i.h" inside the loop only
Mark> creates ONE file Presumable the $i in the redirection
Mark> only gets evaluated once for some reason.
Thanks for the report.
I'm installing this on HEAD and branch-1-8.
2004
This is a beta for the next bug-fix release of Automake.
The list of bug fixes is appended.
I hope to release 1.8.3 next week-end.
Please report bugs to <[EMAIL PROTECTED]>.
You can download this beta here:
ftp://alpha.gnu.org/gnu/automake/automake-1.8.2b.tar.gz
ftp://alpha.gnu.org/gnu/automa
ritten LIBTOOL in they Makefile.am
to insert a --tag option.
Also such a rule would be triggered only if something depends on
$(LIBTOOL), which I believe is not the case (same problem with
--tag here). Is such a dependency desirable? IOW should every
libtool target be recompiled whenever config.status changes?
--
Alexandre Duret-Lutz
>>> "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
[...]
Gary> should Automake be patched to accept `program_LDADD =
Gary> -dlopen foo.la'?
Sorry for the delay. This should work since Automake 1.4b.
It's documented and regression-tested.
--
Alexandre Duret-Lutz
e, etc.
Replacing just ${prefix} may not be always enough. Also I'm not
sure @pkgdatadir@ is available as an AC_SUBST.
I don't know what's best for the rest.
--
Alexandre Duret-Lutz
u can control when the current
directory is built (with `.').
--
Alexandre Duret-Lutz
We're pleased to announce the release of Automake 1.8.3.
This is a bug fix release. The list of bug fixes is appended below.
You can find the new release here:
ftp://ftp.gnu.org/gnu/automake/automake-1.8.3.tar.gz
ftp://ftp.gnu.org/gnu/automake/automake-1.8.3.tar.gz.sig
ftp://ftp.gnu
ir) after
untarballing) and yet must be rebuilt in the build-dir if
needed. This simply cannot be done portably.
--
Alexandre Duret-Lutz
See paragraph "Compiling For
Multiple Architectures" in file INSTALL.
--
Alexandre Duret-Lutz
FIG_FILES, not just the top one.
--
Alexandre Duret-Lutz
>>> "Hans" == Hans Deragon <[EMAIL PROTECTED]> writes:
[...]
Hans> Is it possible to define directories in nobase_pkgdata_DATA?
No, this is PR/383. You have to use a install-data-local until
someone implements this.
--
Alexandre Duret-Lutz
irectory, although I wouldn't recommend
this for manually updated files.
Jose> b) When I do make install have it entirely copied to
Jose> $(prefix)/help/the_directory_I_am_questioning_about/html
This is PR/383. You have to write a install-data-local rule
until someone implements this.
[...]
--
Alexandre Duret-Lutz
hem yet?
Better fix other bugs by upgrading to 1.8.3 at once.
--
Alexandre Duret-Lutz
use lots of
AM_CONDITIONALS? (How many per-subproject, and how many
per-Makefile.am?)
You could also run automake in `--verbose' mode and try to get
the feeling of were time is spent.
--
Alexandre Duret-Lutz
up Automake supports is this:
- all Makefiles are unconditionally created by `configure'
- but some of can be left out of the build during `make'
(they will still be recursed by `make dist')
See section `Conditional subdirectories' in node `Top level' of
the manual for examples.
--
Alexandre Duret-Lutz
important to be caused just by this
I wish we could profile Automake, say over its test suite.
Does anybody knows how we could do this?
--
Alexandre Duret-Lutz
ke will define `DIST_SUBDIRS' automatically from the possibles
| values of `SUBDIRS' in all conditions.
|
|If `SUBDIRS' contains `AC_SUBST' variables, `DIST_SUBDIRS' will not
| be defined correctly because Automake doesn't know the possible values
| of these variables. In this case `DIST_SUBDIRS' needs to be defined
| manually.
|
|-- Footnotes --
|
|(1) Don't try seeking a solution where `opt/Makefile' is created
| conditionally, this is a lot trickier than the solutions presented here.
--
Alexandre Duret-Lutz
, prefix and platform doesn't display as
Esben> nicely as they should because of this.
Thanks for fixing this. I've installed your patch.
--
Alexandre Duret-Lutz
9> WANT_AUTOMAKE_1_6=1 env variable or the version
Alien9> option in the configure.ac file works.
There is no such variable in the version we maintain, it must be
a change local to your distribution/environment. (Or it doesn't
exist at all, which would explain why it doesn't work...)
[...]
--
Alexandre Duret-Lutz
for the Makefiles: process the Makefile that will ship the
auxdir files after all the other Makefiles.
--
Alexandre Duret-Lutz
With it _all_ packages produce non-portable tarballs using
non-portable syntax.
Forcing the ustar format might be a possibility (is it?), if
that can be done portably (that probably involves a configure
check). Another idea is to arrange the dist rules so users have
a way to override the tar options.
--
Alexandre Duret-Lutz
>>> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes:
Paul> Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
>> 1. The --format=posix options is a GNU Tar option, which means `make dist'
>> can no longer be run with other make implementations
x.1.html) mentions that "due
to implementation errors, file names longer than 99 characters
can not considered to be generally portable" when taking about
the ustar format.
I think it's the only place where I've read this. Has anybody
seen such implementation? I'm tempted to think we shouldn't
care.
--
Alexandre Duret-Lutz
>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
>>> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes:
[...]
>>> Forcing the ustar format might be a possibility (is it?), if
>>> that can be done portably (that pro
d-GNU-tar-with-o deviates from V7?
If the answer is yes, then I guess we must keep using `o' with
older GNU tar versions, and people with long filenames will have
to get a recent tar version if they want portable tarballs.
Otherwise it seems we simply do not need `o'.
--
Alexandre Duret-Lutz
>>> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes:
Paul> Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
>> How about this scheme:
Paul> In the light of later discussion, how about this scheme instead?
Paul> Use the first of the following c
#x27; Makefile
on the working and non-working tarballs?
CVS Autoconf has a new SHELL selection code. That could explain it.
This doesn't explain why it works with FreeBSD make, though. Unless
FreeBSD make ignores SHELL, but that would be a bug.
Bob> Maybe there is a directory timestamp problem?
I don't know how that could matter. We do not use directories
as dependencies.
--
Alexandre Duret-Lutz
This is a beta for the next bug-fix release of Automake.
The list of bug fixes is appended.
I hope to release 1.8.4 next week-end and start the 1.9 cycle soon
after that. So please consider this as your last chance to report
1.8.x regressions.
Please report bugs to <[EMAIL PROTECTED]>.
You can
>>> "Eric" == Eric Sunshine <[EMAIL PROTECTED]> writes:
Eric> Alexandre Duret-Lutz wrote:
>> This suggests that shell running this code does not split
>> $list and $subdir get the full list. Zsh would do that.
>> Could you compare the output o
nough for
comments.
(BTW the real purpose of tar2.test is to get report from
people on platforms where the pax format is not supported.)
2004-04-18 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
For PR automake/414:
Introduce options tar-v7, tar-ustar, and tar-pax to select
>>> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes:
Paul> Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
>> [EMAIL PROTECTED] selects the new pax format defined by POSIX
>> +1003.1-2001. It supports filenames with up to 65535 characters.
P
a bug in the generation of dependency
Carlo> on 'Makefile.am'.
Thanks for the report. This was fixed in 1.8.
If you have trouble installing 1.8.3, please send bug reports
about that: 1.8.4 is on the starting block.
--
Alexandre Duret-Lutz
OMPATIBLE) to work. CONFIG_SHELL would allow shell
that require such extra code.
Note that the above definition of SHELL would be useful to
configure itself. For instance it currently runs things like
ac_config_guess="$SHELL $ac_aux_dir/config.guess"
ac_config_sub="$SHELL $ac_aux_dir/config.sub"
ac_configure="$SHELL $ac_aux_dir/configure" # This should be Cygnus configure.
and I doubt these will enjoy zsh.
--
Alexandre Duret-Lutz
>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
[...]
Paul> the existing code uses the -o option, which is [not portable]
[...]
Speaking about `o', I've just discovered that `missing' contains
some magic to strip that flag when tar fails,
>>> "Gunnar" == Gunnar Ritter <[EMAIL PROTECTED]> writes:
Gunnar> Alexandre Duret-Lutz <[EMAIL PROTECTED]> wrote:
>> >>> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes:
>>
Paul> Alexandre Duret-Lutz <[EMAIL
so deliberately telling the tar2.test
failing on system that cannot create pax archive to get some
feedback from people using CVS Automake. (I tried Darwin and
Solaris8, where this test fails.) I'll correct this before the
release.
2004-04-20 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
`filenames-99'. Maybe someone can suggest some nicer name?
2004-04-20 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
For PR automake/414:
Introduce option filenames-99.
* doc/automake.texi (Options): Document it.
* configure.ac (AM_INIT_AUTOMAKE): Use it.
discussed in the `Rebuilding Makefiles'
section of the manual, or is it more involved?
--
Alexandre Duret-Lutz
>>> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes:
Paul> Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
>> I've prepared this. However I'm not really proud of the name
>> `filenames-99'. Maybe someone can suggest some nic
gests that I have created a mix of old and new automake
mks> and autoconf. Would anyone care to guess what I should do
mks> next?
aclocal --version to know which version you are running
[...]
--
Alexandre Duret-Lutz
and means you should run aclocal
[...]
--
Alexandre Duret-Lutz
tion, is there any good reference or
Gregory> document about how one should include 3rd party libraries
Gregory> in one's package?
None that I know.
--
Alexandre Duret-Lutz
ce to know the difference between
your setup and Nicolas's.
2004-04-24 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* lib/depcomp (tru64) [libtool]: Nicolas Joly reported on
2002-06-12 that dependencies were output in $dir.libs/$base.lo.d.
Teun Burgers reported on
[s/autoconf@/automake@/]
>>> "Harlan" == Harlan Stenn <[EMAIL PROTECTED]> writes:
Harlan> If I want automake warnings to be fatal throughout the
Harlan> entire tree, is it better to:
Use AM_INIT_AUTOMAKE([-Werror])
--
Alexandre Duret-Lutz
We're pleased to announce the release of Automake 1.8.4.
This is a bug fix release. The list of bug fixes is appended below.
You can find the new release here:
ftp://ftp.gnu.org/gnu/automake/automake-1.8.4.tar.gz
ftp://ftp.gnu.org/gnu/automake/automake-1.8.4.tar.gz.sig
ftp://ftp.gnu
...]
Harlan> It seems to me that the 2nd "gmake" should not quietly succeed.
Harlan> Am I mistaken?
I've fixed CVS Automake so it no longer write Makefile.ins on error.
That will be in Automake 1.9.
--
Alexandre Duret-Lutz
riable. This is PR/325. You can only use
plain filenames, or variables that contain entire filenames.
--
Alexandre Duret-Lutz
386-linux or something like this?
Anyway you can complain to Joe's maintainer(s). I can't see any
reason to use AC_CANONICAL_TARGET in its configure.ac, and
removing this macro should avoid any problem like yours.
--
Alexandre Duret-Lutz
igure after
doing this? (Joe uses AM_MAINTAINER_MODE, which means those
things do not get rebuilt automatically unless you know you have
to ask for it.)
--
Alexandre Duret-Lutz
rence
between EXTRA_LTLIBRARIES and lib_LTLIBRARIES.
If using -version-info has some influence to what you obtain,
then it must be due to some Libtool internal, possibly related
to the absence of -rpath.
--
Alexandre Duret-Lutz
We're pleased to announce the release of Automake 1.8.5.
This bug fix release is probably the last of the 1.8.x series.
The first betas for Automake 1.9 should appear shortly.
You can find the new release here:
ftp://ftp.gnu.org/gnu/automake/automake-1.8.5.tar.gz
ftp://ftp.gnu.org/gnu/au
automake problem...
Thanks for the detailed report. I'm installing the following
fix on HEAD and branch-1-8.
2004-05-17 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* m4/cond.m4 (AM_CONDITIONAL): Double-quote diagnostic.
* tests/condd.test: Define a macro with the sa
Automake, maybe?) Then I confess I don't really realize
to what extent this restriction is annoying. I can see that
Ralf is annoyed, but I do not know why. AFAIC naming a
convenience library libfoo.a instead of foo.a is not a big deal.
Finally, I'm surprised this discussion hasn't come up before (or
did it?).
--
Alexandre Duret-Lutz
Hi people,
Here is a first beta release of the next version of Automake (1.9).
The list of changes relative to Automake 1.8.5 are appended below.
Since most bug fixes occured on the 1.8.x branch, only new features
and hard-to-fix bugs remain on this list.
If you have some time, please help us tra
>>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> It would be nice if Automake had the bit of magic to copy
Akim> directories, instead of simple files, in this precise.
Indeed. This is PR/383.
--
Alexandre Duret-Lutz
e also noticed that in packages that do not use
`ACLOCAL_AMFLAGS = -I m4dir' the libtoolize script will dump all
m4 macros in the current directory. This sounds bogus because
no tool will read these macros there. People that do not use
`-I m4dir' simply want their aclocal.m4 filled.
--
Alexandre Duret-Lutz
that case, shouldn't it be better to use for tmpdepfile2 :
Nicolas> "$dir$base.o.d" instead of "$dir.libs/$base.o.d"
Nicolas> NB: "$dir.libs/$base.o.d" are automatically cleaned
Nicolas> with `make distclean', with the `.libs' direc
n|ac). So foobar is the
top-level directory of a subpackage, and Automake rightly
requires top-level files in that directory.
If you do not want these files in foobar, you have to configure
that subpackage so it does not need them, using one of the
syntaxes Ralf mentioned.
--
Alexandre Duret-Lutz
iler I want to use (TAU) is adds code
Dan> instrumentation prior to compilation.
IMHO, the easiest route is to create a script the wrap the call
to TAU and your real compiler, and tell configure to use this
script as a compiler with `./configure CC=taucc`. That way you
do not need to change your build setup.
--
Alexandre Duret-Lutz
put in foo/.
So if you need two different build for debug and release,
you simply type
mkdir debug release
cd debug
../configure CPPFLAGS=-DDEBUG # or whatever options you want
make
cd ../release
../configure
make
--
Alexandre Duret-Lutz
>>> "Roberto" == Roberto Bagnara <[EMAIL PROTECTED]> writes:
Roberto> Alexandre Duret-Lutz wrote:
>> Here is a first beta release of the next version of Automake (1.9).
>> The list of changes relative to Automake 1.8.5 are appended below.
Roberto>
On Mon, Jun 14, 2004 at 03:45:39PM +0400, Denis Lagno wrote:
> Hi,
>
> My machine runs NetBSD-current. I have installed
> cvs-current versions of autoconf, gmake, gm4 and perl in
> /usr/local.
>
> I am trying to build automake from cvs.
It's not clear whether you ran ./bootstrap first or not. Yo
>>> "Oliver" == Oliver B Fischer <[EMAIL PROTECTED]> writes:
[...]
Oliver> Does someone know why automake can't find AC_PROG_LIBTOOL?
Either you haven't installed libtool, or you forgot to run aclocal
prior to autoconf and automake.
--
Alexandre Duret-Lutz
301 - 400 of 920 matches
Mail list logo
