Hello,
> * Stepan Kasal wrote on Mon, Nov 09, 2009 at 03:52:29PM CET:
> > Files which are automatically distributed, if found:
> > Use of uninitialized value in formline at /usr/bin/automake line 8334.
> > ABOUT-GNU README config.rpath ltcf-gcj.sh
Hello,
On Tue, Jul 01, 2008 at 06:12:15AM +, Ineiev wrote:
> WinAVR gcc produces dependencies that shall confuse `make',
> like these:
>
> sampler.o: ../../../stribog/sw/auxilia/coil/sampler.c \
> c:/winavr-20080512/lib/gcc/../../avr/include/avr/io.h \
> c:/winavr-20080512/lib/gcc/../../a
Hello,
On Wed, Jul 02, 2008 at 02:07:36AM +1930, Roberto Alejandro Espí Muñoz wrote:
> Ok, I thinks I didn't explain myself correctly then ... From what I
> saw there I can use either bindir, libdir or includedir for when I'm
> installing the completed targets. What I want to do is to locate them
where its behaviour is not
equivalent to that of a standard POSIX make, then it should be
reported to emake developers first.
Hope this helps,
Stepan Kasal
Hello,
On Wed, Jun 18, 2008 at 10:42:10AM -0600, John Calcote wrote:
> Never mind ... duh ... I forgot to take the docs directory out of the
> EXTRA_DIST variable when I added it to the SUBDIRS variable.
>
> Thus (I'm guessing) the distdir code was trying to create files that
> were already in pl
preprocessor only (e.g., gcc -E). The main
I'm not aware about anything like that.
For my debugging needs, for example, it was always enough to cut and
paste the command which failed, with -E, without -c -o something.o
and direct the output to less.
Stepan Kasal
Hello,
On Sun, May 25, 2008 at 07:49:51PM -0700, Bobby Dill wrote:
> %.cpp: %.png
> uic -embed colortool $? -o $@
>
> image_collection.cpp: images/designer_widgetstack.png \
> images/designer_d_table.png \
> images/designer_d_iconview.png
well, this is more aquestion abou
r-clean, so you do not do much harm by breaching that
part of the standard.
Uff, rather lenthy mail, I hope at least some parts of ot will help
you.
Stepan Kasal
--- Makefile.am 2008-05-13 19:32:10.0 +0200
+++ ../test-Makefile.am 2008-05-14 16:23:23.0 +0200
@@ -3,13 +3,15 @@
html-l
On Tue, May 13, 2008 at 07:55:26AM -0400, David Bruce wrote:
> On Tuesday 13 May 2008 04:37:16 am Stepan Kasal wrote:
> > > On Mon, 2008-05-12 at 11:22 -0400, David Bruce wrote:
> > > > "MKDIR_P" is recommended but requires automake-1.10 or higher. [...]
> >
Hello again, Peter,
On Mon, May 05, 2008 at 07:07:54PM +0200, Peter Simons wrote:
> > Another way is to do all the necessary work manually: defining
> > install-data-local, uninstall-local, etc. That should be safer.
>
> Thank you for the recommendation. I tried it. Both 'dist' and 'install'
>
uture version of
Automake, AM_INIT_AUTOMAKE([1.10]) will probably be no longer an
issue.
HTH,
Stepan Kasal
On Sat, May 03, 2008 at 01:08:16AM +0200, Peter Simons wrote:
> Warren Young writes:
> > dist_pkgdata_DATA = html/*
>
> When I try that, I get the following error message:
> | make[1]: *** No rule to make target `html/*', needed by `all-am'. Stop.
well, that's because all-local is not hooked t
Hello Bobby,
a few comments:
On Sat, May 03, 2008 at 11:38:08PM -0700, Bobby Dill wrote:
> When I try to compile my app, I get a message stating that sigcreatedlg.h
> does not exist, so the files in BUILT_SOURCES are not generated before the
> rest of my app is compiled. What's the right way to
Hello Jack,
a few humble ideas:
On Sat, May 03, 2008 at 05:59:44PM -0700, Jack Bates wrote:
> patch: patch-stamp
> patch-stamp: patches/*
> cat patches/* | patch -p0
>
> touch $@
Please note that this rule is not perfect; when one of the
patches is deleted, the rule does not notice
Hi,
On Wed, Mar 19, 2008 at 03:55:55PM -0400, NightStrike wrote:
> > mingw-w64/crt
> > mingw-w64/doc
> > mingw-w64/hdr
...
> So I guess the choices boil down to:
>
> 1) Change the directory structure
> 2) Recursive make to a small degree
>
> Is that about right?
actually, I recommend recursive
Hello,
On Wed, Mar 19, 2008 at 03:13:06PM -0400, NightStrike wrote:
> On 3/19/08, Stepan Kasal <[EMAIL PROTECTED]> wrote:
> > BTW: Why do you insist on the layout described above? I would have
> > one top-level directory and make "doc" and "headers" (or p
Hello,
On Wed, Mar 19, 2008 at 10:51:28AM -0700, iamcamiel wrote:
> For those interested; [...]
and for the readers of the archive.
> prog_a_CXXFLAGS = -DVAR_A
A typo: _CPPFLAGS (C PreProcessor), CXX stands for C++.
Other than that, it's a perfect solution.
Stepan Kasal
Good afternon Della,
On Wed, Mar 19, 2008 at 02:02:17PM -0400, NightStrike wrote:
> > On Tue, 11 Mar 2008, NightStrike wrote:
> > > I had intended to do everything with non-recursive make, but as [Ralf]
> > > pointed out once, non-recursive is also considered harmful.
[thread:]
> http://lists.gnu.
macro AM_PATH_XML2
would not get to aclocal.m4 even if it is available. So please do
not use m4_ifdef in this case.]
Hope this clarifies the situation,
Stepan Kasal
Hello,
On Tue, Nov 27, 2007 at 12:30:31AM +, Olly Betts wrote:
> "Handling Tools that Produce Many Outputs". However, these recipes
> require a lot of boilerplate code which annoyingly obscures [...]
>
> It's just struck me that automake is good at inserting lots of
> boilerplate code into m
ar question
remained unansewered, feel free to post it again, under a new
subject.
Have a nice day,
Stepan Kasal
it,
Stepan Kasal
Hi Harald,
[answering, though not asked]
On Thu, May 03, 2007 at 12:48:08PM +0200, Harald Dunkel wrote:
> Hi Ralf,
[...]
> Do you think it would be difficult to replace the
> hardwired 'man' in automake.pl by a directory variable?
I'm afraid it is relatively difficult.
Prove that I'm wrong! ;-)
looks like two discrete kind of magic. Which of the two shall
apply to general foo_MANS?
It seems that even writing a specification for the genreal `MANS'
primary presents some work, even before any line of code is written.
Again, volunteers are welcome.
Have a nice day,
Stepan Kasal
Hello,
On Wed, Apr 25, 2007 at 02:46:55PM -0500, Robert J. Hansen wrote:
> What is the canonical way to test for the existence of libsablot with
> autoconf 2.60?
well, this question shall better go to [EMAIL PROTECTED]
I think you can use AC_CHECK_LIB to check for the library.
Since GNU/Linux
Hello Florian,
* Florian Briegel wrote on Mon, Apr 23, 2007 at 11:59:10AM CEST:
> Am Montag, 23. April 2007 schrieb Benoit Sigoure:
> > Is there any reason why you would not want to do this?
>
> Simplicity.
>
> aaa_SOURCES = foo.x
>
> is much more easy to handle [...]
indeed. I believe you
ot work. (Or, at least, is not tested.)
It seems that some time ago, you configured a project with
--disable-dependency-tracking, and then this seting was stored in the
cache. (You might say that this is a bug in Automake, but in any
case, this is something which is note ready and does not work.)
Have a nice day,
Stepan Kasal
Hi John,
On Thu, Apr 12, 2007 at 05:52:41AM -0700, j y wrote:
> sed script, however, is slightly not what I wanted. The , addressing will
> match until the first */ encountered AFTER the the line with the /*.
oh! You are right, of course.
I was not aware that the semantics of ranges in sed is
ed, sorry)
The option -i to sed is GNU-specific, so I replaced it to increase
portability. And I changed the sed cmd to adapt for comments which
span more than two lines.
Have a nice day,
Stepan Kasal
).
#
# In Automake 1.8 (or whatever it is called) we can turn these
# warnings on, since -Wno-portability will not be an issue for
# the 1.7/1.8 transition.
Have a nice day,
Stepan Kasal
= fake.cc
I tested this, and it works. The fake program is there to drag in
C++ support.
Please note that though the *.cc files are temporarily created,
make delets them at the end, because they are intermediate.
(Use info '(make)Chained Rules' to read details.)
Could you live with this?
Have a nice day,
Stepan Kasal
would match people's need
for "un-bootstrap".
> * How about having autoreconf (aka "bootstrap") take an option:
> autoreconf --clean
> bootstrap --clean
As said above, I gather that this is the way to go.
Have a nice day, Stepan Kasal
foo is needed to build this project''.
(Yes, these configure scripts are badly written, as the AC_MSG_ERROR
is meant to notify about ``an error that prevents `configure' from
completing,'' as the manual says. Yet is is often used in situations
which prevent the build fr
l to implement `bootstrap.sh --clean'.
I'm looking forward to hear your opinions.
Have a nice day,
Stepan Kasal
Hello,
On Tue, Mar 13, 2007 at 09:25:14PM +0100, Andreas Schwab wrote:
> If you use AUTOMAKE_OPTIONS = foreign then automake should not complain.
yes, this is good note, thanks. I wanted to keep the gnu strictness,
since I hoped Automake would also check other things for me.
But perhaps this is
Hello,
i apologize that I reply to myself. I found out there is one nit:
> If you write the rule for ChangeLog to Makefile.am, then Automake
> complains that the file does not exist at the time Automake is run.
Actually, Automake suppresses the message if a rule named
"ChangeLog" is found.
But
how this can be achieved?
(It might be possible to place the command into the bootstrap script
and perhaps also add this command to the dist-hook...)
Thanks in advance for any advices,
Stepan Kasal
Hello,
one nit:
On Wed, Jan 24, 2007 at 08:00:59PM +0100, Ralf Wildenhues wrote:
> Please note that the docdir variable is new in Autoconf-2.60, so if you
> happen to use an older Autoconf version together with your Automake,
> then you also need something along the lines of
> docdir = ${datad
Hello,
On Wed, Jan 10, 2007 at 08:19:38AM +0900, atoz wrote:
> if WANT_MAN_PAGES
> cp fooman.8 $(foomandir)
> fi
...
> and it leads to the following error ...
>
> Makefile.am:175: unterminated conditionals: WANT_MAN_PAGES_TRUE
this question is easy: Automake conditionals are ended by "en
able is not
necessary (though harmless).
Have a nice day,
Stepan Kasal
Hello,
On Fri, Dec 08, 2006 at 11:00:09AM +0100, Presario Smith wrote:
> AUTOMAKE_OPTIONS = foreign
I'd prefer
AM_INIT_AUTOMAKE([foreign])
in configure.ac, as this is a "global" option, affecting the whole
project. But that's just a nit.
Have a nice day,
Stepan Kasal
look
at the issue. (Yes, there is no guarantee that the work you
invest into formulating the question will pay off, unfortunately. :-( )
Sorry that we were not able to provide better help. (At least not
yet.)
Have a nice day,
Stepan Kasal
_SOURCES = someSource.cc someAsm.asm
> >.asm.o:
> > $(NASM_PATH) -o $@ -f elf -dLINUX $<
Have a nice day,
Stepan Kasal
M_CPPFLAGS) -DEDITOR_BUILD
editorD_SOURCES = someSource.cc someAsm.asm
editorD-someAsm.o: someAsm.asm
$(NASM_PATH) -o $@ -f elf -dLINUX $<
If you think that these advices are not appliable in your case,
post a less simplified version of Makefile.am.
> PS: I hope I got that Cc right now?
Yes, you did.
Have a nice day,
Stepan Kasal
Hello Ralf and all,
[sorry for the delay, I forgot this in my "postponed" folder]
On Fri, Nov 10, 2006 at 01:35:54PM +0100, Ralf Wildenhues wrote:
> * Stepan Kasal wrote on Fri, Nov 10, 2006 at 12:40:18PM CET:
> > [...] So it seems that distcheck would
> > catch more bu
ke can deduce the
suffixes from the rules, and generate the .SUFFIXES: line.
Have a nice day,
Stepan Kasal
Footnote:
[*] "Normal case" means here that each suffix starts with a dot and
does not contain any other dot.
Hello,
On Thu, Nov 30, 2006 at 10:24:19AM +0100, Guillaume Rousse wrote:
> So, to get back at my original question, what's the proper way of
> expressing dependencies for a generated source file through
> configure-time substitution:
> foo: foo.in config.status
>
> or, as in autoconf documentat
Hello,
On Thu, Nov 30, 2006 at 09:31:19AM +0100, Guillaume Rousse wrote:
> Stepan Kasal wrote:
> >You specified the dependency:
> >
> > corelib/camlimages.ml <-- Makefile
> >
> >This is not correct. You should specify the ultimate primary sources
> >in
rect reply), and I didn't saw Stepan's
> answer neither.
My answer was CC'ed to you, but your servers refuse connections from
my computer.
Have a nice day,
Stepan Kasal
s.ml via the $(OCAMLSOURCES)
You specified the dependency:
corelib/camlimages.ml <-- Makefile
This is not correct. You should specify the ultimate primary sources
instead of `Makefile'. Prehaps `Makefile.am' is enough?
I hope this hint helps you to find a fix.
Have a nice day,
Stepan Kasal
Hello Steve,
I do not have any experience with kbuilt, but I'll try to generate
some hins anyway:
On Mon, Nov 13, 2006 at 11:48:29AM +0100, Steve Kreyer wrote:
> DEFAULT_INCLUDES = [EMAIL PROTECTED]@
two nits about this line: No need to use @..@, use $(abs_top_srcdir)
instead.
Why do you re-def
o.c
bar_SOURCES = bar.c baz.c
nodist_check_SCRIPTS = this
# this is created from this.in by configure
dist_check_SCRIPTS = that another
TESTS = $(check_PROGRAMS) $(nodist_check_SCRIPTS) $(dist_check_SCRIPTS)
Have a nice day,
Stepan Kasal
Hello Ralf,
On Fri, Nov 10, 2006 at 05:50:18PM +0100, Jim Rainville wrote:
> + aclocal-1.10 -I m4
...
> configure.ac:80: warning: macro `AM_LIBTOOLFLAGS' not found in library
On Sun, Nov 12, 2006 at 06:43:44PM +0100, Ralf Wildenhues wrote:
> The warning shouldn't be there. Please post the config
e second "../" is your "$(srcdir)/",
I made a suggestion, and Ralf oposed to it.
On Fri, Nov 10, 2006 at 01:35:54PM +0100, Ralf Wildenhues wrote:
> * Stepan Kasal wrote on Fri, Nov 10, 2006 at 12:40:18PM CET:
> > [...] So it seems that distcheck would
> > catch m
Hi Ralf,
On Thu, Nov 09, 2006 at 02:04:20PM +0100, Ralf Wildenhues wrote:
> * David Everly wrote on Thu, Nov 09, 2006 at 01:52:12PM CET:
> > On 11/9/06, Stepan Kasal <[EMAIL PROTECTED]> wrote:
> > >well, I created configure.ac and Makefile.am:
> [...]
> > This is
rect/amend it.
HTH,
Stepan Kasal
Hello,
On Wed, Nov 08, 2006 at 05:46:23PM -0700, David Everly wrote:
> I put together a test case before sending my email, the only line in
> the one Makefile.am is the one I gave containing test.txt.
well, I created configure.ac and Makefile.am:
$ cat configure.ac
AC_INIT([this], [1.0], [EMAIL P
Hello,
On Wed, Nov 08, 2006 at 11:29:39AM -0700, David Everly wrote:
> I should have used this (because test.txt is not constructed):
>
> dist_sysconf_DATA = $(top_srcdir)/test.txt
>
> However, I've regularly run 'make distcheck' and it gives no error
> with the original sysconf_DATA. How can
ication will be
rebuilt on a subsequent run of `make', eg. during `sudo make install'.
Second, I suppose that main.c is distributed and generatedheader.h is
not. But distributed files are not allowed to depend on
non-distributed ones.
In short, do not do this.
Have a nice day,
Stepan Kasal
hich you posted, but I hope
that you find my suggestions inspirative anyway.
If a problem remains, feel free to ask again.
Have a nice day,
Stepan Kasal
a `system' installation of the *.m4
file, using the `dirlist' file.
(It is possible /usr/share/aclocal/dirlist is read-only in your case,
perhaps because you do not administer the system. Then your only
option is to make a local installation of Automake under your $HOME
directory.)
Have a nice day,
Stepan Kasal
Hello,
I haven't read the whole post, but I'd like to make a few quick
comments:
On Fri, Sep 29, 2006 at 09:34:42AM +0200, Ralf Wildenhues wrote:
> > Q: The "auto" in the name of "automake" and "autoconf", does this
> > mean I can create the build environment on one platform and the
> >
Hello,
On Fri, Sep 22, 2006 at 10:54:20PM +0800, Tzu-Chien Chiu wrote:
> 2006/9/22, Stepan Kasal <[EMAIL PROTECTED]>:
> >But this does not mean tha BUILD_CC has to be set!
> >If BUILD_CC is empty, this just makes CC empty. AC_PROG_CC then does
> >its work. (The var
test only if it is nonempty.)
Yes, I agree this is tricky, yet I think this aproach is appropriate
for a small project.
Have a nice day,
Stepan Kasal
That's why I suggested to study texinfo/configure.ac (from version
4.8 or newer), which does build a couple of native tools, which are
then needed for the main cross-platform build.
Texinfo is a smaller package, and thus should serve as a more
comprehensive example. Feel free to ask me about the details of it.
HTH,
Stepan Kasal
by `make dist'.)
Have a ncie day,
Stepan Kasal
ng each makefile by two
lines is bigger than the discomfort reported, because the need for
non-top `make distdir' is very rare.
(But I was not sure whether this is the right answer, so I decided to
wait for a better answer from someone else.)
Stepan Kasal
Hello,
> installed in man3, man3f, and man3f90.
indeed, these non-standard man subdirectories are not aupported by
the MANS primary. But you can use the _DATA primary:
man3fdir = $(mandir)/man3f
man3f_DATA = foo.3f
man3f90dir = $(mandir)/man3f90
man3f90_DATA = foo.3f90
If you used the same for
Hello,
On Thu, Aug 10, 2006 at 04:49:11PM +0200, Sylvestre Ledru wrote:
> > > After an autoreconf, configure and make, it stops with the error :
> > > make[1]: *** No rule to make target `routines/libscilab.la ', needed by
> > > `scilex'. Stop.
> >
> > The space in `routines/libscilab.la '
> > l
ou debug it
and point your finger to the utility which is causing this?
Is that utility free software, ie., under our control?
Or is it a vendor compiler?
I hope my questions help to find the solution.
Stepan Kasal
ile build is
required, the configure script first configures in a subdirectory for
a native build, then it continues configuration for the main build.
Consult texinfo-4.8/configure.ac for details.
Feel free to ask if anything of the trick is not clear.
Have a nice day,
Stepan Kasal
ect mailing list.
this is not unusual. There is absolutely no need to feel sorry.
I believe ti is good that we have two lists, but the boundary is
fuzzy. Perhaps I should find a more gentle wording when trying to
shift threads from one list to another. Take it easy.
Have a nice day,
Stepan Kasal
Hello,
On Sat, Aug 05, 2006 at 01:57:35AM +, Harlan Stenn wrote:
> > Neither works, because automake disallows it:
> > | Makefile.am:1: `bindir' is not a legitimate directory for `DATA'
sorry, I have not tried it before posting.
> That's easy - use something like:
>
> bindata_DATA= libnetcd
Hello,
On Sat, Aug 05, 2006 at 03:13:22PM +0100, Paulo J. Matos wrote:
> I'm getting a directory autom4te.cache in my tree with big files in
this is a cache produces by autom4te, the workhorse behind autoconf
and aclocal. The usual solution is to ignore it, and add it to
.cvsignore
Some people
Hello,
On Wed, Aug 02, 2006 at 07:30:47PM -0600, Ed Hartnett wrote:
> [...] gcc to produce an extra output file, called libnetcdf.def.
...
> So how do I tell automake that there is a file I would like installed,
> but not specially built nor included in the distribution?
>
> I'm sure there is som
rather use another name.
> Using 'pyexecdir_PYTHON' in src/Makefile.am leads to an error while
Indeed, `foo_PRIMARY' is coupled with `foodir', and `pyexecdir' is
defined by AM_PATH_PYTHON, while `pyexecdirdir' is a nonsense.
HTH,
Stepan Kasal
e.in.
>
> I tried _AM_SUBST_NOTMAKE, but I see the following error:
>
> configure.ac:212: error: possibly undefined macro: _AM_SUBST_NOTMAKE
I'm afraid I forgot to mention that this macro is available only in
CVS version of Automake. Please install that.
I apologize that my mistake caused waste of your time.
Stepan Kasal
that it will be built at the very
begining of targets `all', `check', and `install', but that is all.
It is just a hack which helps in situations where the target cannot
be listed as a prerequisite to the terget which really needs it.
Hope this makes this corner less dark,
Stepan Kasal
e from "_SCRIPTS").
If the *.py file is not updated by `make all', it is, IMHO, a bug in
Automake; please tell us what you found out with the new version(s).
As a workaround, you can add:
all-local: $(nodist_thing_PYTHON)
But ieven with this bug, the *.py files should be prerequisites for
`install', so they should be updated before tey are installed.
Looking forward to hear more,
Stepan Kasal
([FOO]) to instruct automake that
this variable is to be omitted from the generated Makefile.in.
Sorry for the inconvenience,
Stepan Kasal
ipt or somesuch)?
dist_bin_SCRIPTS = checkmk
(*_SCRIPTS are not distributed by default)
That should do it; without any more workarounds. If there are
problems, report them here.
Have a nice day,
Stepan Kasal
7;).
Yet it might be the best solution available atm.
HTH,
Stepan Kasal
Hello,
a correction:
On Thu, Jul 13, 2006 at 07:29:14PM +0200, Stepan Kasal wrote:
> But the same simplification is not possible in
> src/language/lexer/automake.mk, because of a bug in Automake: this
> feature does not work in combination with per-target fl
Hello,
I have noticed that suffix rules do not work with per-target flags.
If you have
.q.c:
cp $< $@
foo_SOURCES = bar.q
foo_CPPFLAGS = -I dir
Then the generated rule looks like:
foo-bar.o: bar.q
... gcc bar.q ...
while both occurences of `bar.q' should obviously be `bar.c'.
Hello,
On Wed, Jul 12, 2006 at 08:52:54PM +0800, John Darrington wrote:
> On Wed, Jul 12, 2006 at 02:33:21PM +0200, Stepan Kasal wrote:
> Just omit "$(top_builddir)/" from all occurences.
>
> I can't do that. If I do, then it will fail to build from outside
>
Hello,
On Wed, Jul 12, 2006 at 08:13:06PM +0800, John Darrington wrote:
> $(top_builddir)/subdir/mystuff.c: $(top_srcdir)/subdir/mystuff.x
> cp $(top_srcdir)/subdir/mystuff.x $(top_builddir)/subdir/mystuff.c
>
> CLEANFILES= $(top_builddir)/subdir/mystuff.c
...
> mystuff_libstuff_a_SOURCE
Hello,
On Fri, Jun 30, 2006 at 04:24:37PM -0400, David Fang wrote:
> In reply to myself:
> > Is there a way of making the "rm -rf" more robust? Maybe with some sort
> > of "while distdir exists, try removing" loop?
...
> - && rm -fr $(distdir); }; }
> + && { until rm -fr $(distdir
Hello,
On Sat, Jun 24, 2006 at 02:24:09PM +0200, Tom Bachmann wrote:
> a way to do this but $(eval include bar.mk),
Automake is not preprocessing the whole file, so there are easier
ways to fool it:
NULL =
$(NULL)include hoo
or
include = include
$(include) hoo
Have a nice day,
Stepan
Hello,
> What can one say about this? I don't get it.
I'm afraid your mail does not contain enough information for any
reasonable answer.
Can the project be downloaded somewhere?
Could you post gui/Makefile.am?
Which version of Automake was used?
Stepan
Hello,
On Mon, Jun 12, 2006 at 08:59:07PM +0200, Norbert Sendetzky wrote:
> Let me first ask a question: Are .a libraries (libopendbx.a) static libraries
> or is that only dependent on the -static flag?
*.a is always a static library, AFAIK. But that was not the point of
Ralf's answer.
Again,
should add a depencency, eg.
gui_data.c: gui_data.h
see
http://sourceware.org/automake/automake.html#Multiple-Outputs
Have a nice day,
Stepan Kasal
re these paragraphs will have to undergo some editorial work before
install, anyway.
Though I regret the confusion, I'm glad that Ralf pointed out the
problem.
Have a nice day,
Stepan Kasal
Hello,
On Fri, Jun 02, 2006 at 05:13:16PM +0200, Ralf Wildenhues wrote:
> > On Wed, May 31, 2006 at 08:56:41PM +0200, Akim Demaille wrote:
> > > However my point about the name of the condition remains. AC_SUBST
> > > covers only the *_TRUE and *_FALSE part.
...
> I didn't get it the first time e
Hello,
On Wed, May 31, 2006 at 08:56:41PM +0200, Akim Demaille wrote:
> However my point about the name of the condition remains. AC_SUBST
> covers only the *_TRUE and *_FALSE part.
Then I second Ralf's and Alexandre's[1] question:
What would that be good for?
Stepan
[1] http://lists.gnu.org/a
log and where can I find it?
A log of the deamon which handles your email. The headers of the
attached mail reveals that the access is at your ISP, and you
probably don't have access to it.
But it's not needed, we now see that both mails arrived to gnu.org.
Have a nice day,
Stepan Kasal
ac; you start with AC_INIT, then continue with various macros
and shell code to achieve what you need for your package, and end
with AC_OUTPUT.
The following tutrial might help you:
http://www-src.lip6.fr/homepages/Alexandre.Duret-Lutz/autotools.html
Have a nice day,
Stepan Kasal
Hi,
On Wed, May 31, 2006 at 07:21:34PM +, Harlan Stenn wrote:
> I prefer:
>
> AC_CONFIG_FILES(Makefile)
> AC_CONFIG_FILES(src/Makefile)
> AC_OUTPUT
others prefer
AC_CONFIG_FILES([
Makefile
src/Makefile
])
AC_OUTPUT
Stepan
please upgrade to
2.59.
Stepan Kasal
Hello,
> * Akim Demaille wrote on Wed, May 31, 2006 at 04:26:17PM CEST:
> > I suggest that Automake provide the same feature for AM_CONDITIONAL:
well, you already implemented it, granting Alexandre one point for
his hint:
http://lists.gnu.org/archive/html//bug-automake/2004-12/msg00090.html
http
Hello,
On Wed, May 24, 2006 at 03:17:23AM +0200, Guido Draheim wrote:
> [...] I am making it up as a patch over standard 'aclocal' - it just
> adds a few options that imitate automake options "-a" and "-c".
the CVS version of aclocal has an option --install which is very
similar to this. Does it
1 - 100 of 313 matches
Mail list logo
