Hi,
This may not be the best list for this, but I'm already subscribed and
someone here probably knows the answer.
I'm trying to build an autotools in a Cygwin environment, but using MSVC's
cl.exe and link.exe. However, this is what I get when I run make:
---begin---
make[1]: Entering director
On Feb 5, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote:
> * tests/semantics.at (AC_REPLACE_FUNCS): New test.
> * acfunctions.m4 (AC_REPLACE_FUNCS, _AC_LIBOBJ_ALLOCA): Use
> AC_LIBSOURCES.
Ok
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat G
On Feb 5, 2001, Tom Tromey <[EMAIL PROTECTED]> wrote:
> I'd like to also work out a naming scheme for internally generated
> targets. That way eventually it will be clear what people can rely on
> and what they cannot. Suggestions here are welcome.
How 'bout `_am-target-name'? (note the lead
On Feb 6, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote:
> Don't go that way! AC_PREREQ.
It won't let you define fallbacks for older releases, which is exactly
the point. ifdef, as you proposed, is the way to go.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red
The Autotools book, the automake-1.4 manual, and the automake-1.4/NEWS
all imply that "include" is part of automake 1.4. So how come it
doesn't work, but when I try automake from cvs it does work? Is
there some known bug I'm running into? If need be I can send a
testcase, but since it works in
A very stupid and mechanic patch, indeed, but it helps me seeing what
happens. In this patch I took the freedom of introducing a new
syntax: @FOO@ means `to be substituted', while `?FOO?' means to be
removed if positive, or to kill the line if negative, and conversely
for `?!FOO?'.
This patch in
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* automake.in: Various formatting changes, and modernization of
Perl constructs.
(&backname): New.
(&handle_configure, define_standard_variables): Use it.
Index: automake.in
--- automake.in
These people should be sent the file
fencepost.gnu.org:/gd/gnuorg/Copyright/request-assign.future. They
fill out the form, return it to me, and I send them the paperwork to
sign.
If you don't have easy access to fencepost, I'll include the file
below.
- Brian Youma
i found the following in my configure generated by
autoconf 2.13 & automake 1.4:
if test "`cd $srcdir && pwd`" != "`pwd`" && test -f $srcdir/config.status; then
{ echo "configure: error: source directory already configured; run "make distclean"
there first" 1>&2; exit 1; }
fi
cat >> confdefs.
> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes:
Pavel> After another consideration I decided that AM_INCLUDE is not
Pavel> meant to be private since it appears in AC_SUBST.
But it is meant to be private. It is an implementation detail. If we
change the implementation it might just go
Hi, I'm using automake 1.4 for a library called "pdl". I want to
include the generated config.h file in the installed library because
it sets crucial defines that are needed by users of the library. I'm
doing this by setting the following in my configure.in:
AM_CONFIG_HEADER(include/pdl/pdl_c
"Derek R. Price" wrote:
> Inspired by Akim Demaille's use of ifdef, I wrote a third edition of
> this patch which increases functionality when used with a current
> Autoconf.
I just wanted to let you all know that.
...
Ok, fine, here's the patch. :)
Derek
--
Derek Price
Inspired by Akim Demaille's use of ifdef, I wrote a third edition of
this patch which increases functionality when used with a current
Autoconf.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.co
I built automake from the cvs sources today (2001.02.06), and
ran it on the following Makefile.am:
EXTRA_PROGRAMS = typedefs
EXTRA_typedefs_SOURCES = typedefs.l
It produced the following error:
automake: Makefile.am: object `typedefs.$(OBJEXT)' created by `typedefs.c' and `
Raja R Harinath <[EMAIL PROTECTED]> writes:
> Akim Demaille <[EMAIL PROTECTED]> writes:
> [snip]
> > For instance, I find it quite annoying to have to know that Automake
> > knows the -local targets: the code of 25 makes it possible for users
> > to have just there own `clean:' target which will
Rob van der Leek <[EMAIL PROTECTED]> writes:
> Hi list,
>
> I want to define a path to a configuration file in `config.h`, therefore
> I call AC_DEFINE_UNQUOTED(CONFIG_FILE, $prefix/etc/config.xml, [Path to
> config file])
> The problem is that $prefix defaults to NONE when no --prefix flag is
>
Pavel Roskin <[EMAIL PROTECTED]> writes:
> > Tom, you should also know you can have a special exception, and tell
> > autoconf AM_INCLUDE is OK. But I agree with Pavel it looks way too
> > much like a macro name, in itself it is confusing.
>
> As far as I know, it cannot be done without breakin
Hello, Tom!
> What if instead we decide on a permanent naming scheme for automake
> internal variables? Then we can start moving towards that over time,
> starting here.
>
> What if instead we use `_AM_'? Or `_am_'?
After another consideration I decided that AM_INCLUDE is not meant to be
priva
"Derek R. Price" <[EMAIL PROTECTED]> writes:
> Somebody checked in a bad quote recently. It breaks at least the
> stamph/header targets. Patch attached.
Well, I seem to have lost patches. Can't find the one named
`backname' either :( I'm applying yours, thanks!
Tom Tromey <[EMAIL PROTECTED]> writes:
> Akim> -clean: clean-recursive
> Akim> +clean: clean-recursive clean-recursive
>
> This seems wrong.
Ooops. Thanks.
> Note that the clean-am rules are run from the clean-recursive rules in
> subdirs.am. That happens so that we can force the ordering, a
Tom Tromey <[EMAIL PROTECTED]> writes:
> > "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
>
> Akim> so naturally the question is: do we really want to keep this
> Akim> zillions of pseudo targets? The current automake, indeed, does
> Akim> this instead:
>
> Akim> --
> Akim> cl
"Derek R. Price" <[EMAIL PROTECTED]> writes:
> Somebody checked in a bad quote recently. It breaks at least the
> stamph/header targets. Patch attached.
I already have this in the queue :) I just noticed it was wrong when
reading the code. The quote was needed when there was no &transform.
Tom Tromey <[EMAIL PROTECTED]> writes:
> Akim> I can't proceed without a full approval of this patch, it is
> Akim> required for the next ones.
>
> I thought I gave this, with a couple minor changes requested.
Correct, but the thing is these changes were not doable at that time.
I'll put it in
Hi list,
I want to define a path to a configuration file in `config.h`, therefore
I call AC_DEFINE_UNQUOTED(CONFIG_FILE, $prefix/etc/config.xml, [Path to
config file])
The problem is that $prefix defaults to NONE when no --prefix flag is
given at the command line, which forces me to test for this
24 matches
Mail list logo
