Re: automake and flex

Mike Tegtmeyer <[EMAIL PROTECTED]> writes: > I'd like to report a possible bug/limitation in automake and it's use > with flex. It seems that ylwrap strips out or otherwise does not > recognize the --header-file=foo.h option provided in AM_LFLAGS. My > successful useage under 1.9 has been (obviou

bug#9506: makeinfo in VPATH builds fails

Package: automake Version: 1.11a VPATH build of a project using makeinfo fails if $(srcdir) isn't writable. freundt@plutos:~/devel_freundt/datetools/=build> make /home/freundt/devel/datetools/git-version-gen .version >/dev/null make all-recursive make[1]: Entering directory `/home/guest/devel_f

bug#9506: makeinfo in VPATH builds fails

Stefano Lattarini writes: > tags 9506 wontfix > close 9506 > thanks > > Hi Sebastian, thanks for the bug report. > > On Wednesday 14 September 2011, Sebastian Freundt wrote: >> Package: automake >> Version: 1.11a >> >> VPATH build of a project usi

bug#10128: am_foo_OBJECTS is empty when ...

The (internal) variable am_foo_OBJECTS is empty when OBJEXT has been redefined *and* no .SOURCE_EXT.o rule is present. Example: --8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<-- AM_DEFAULT_SOURCE_EXT = .lisp OBJEXT = fasl noinst_PROGRAMS = foo foo_SOURCES = bar.lisp .lisp.fasl: to

bug#10128: am_foo_OBJECTS is empty when ...

Stefano Lattarini writes: > Hi Sebastian, sorry for the terrible delay. > > On 11/24/2011 01:02 PM, Sebastian Freundt wrote: >> The (internal) variable am_foo_OBJECTS is empty when OBJEXT has been >> redefined *and* no .SOURCE_EXT.o rule is present. >> >> Exampl

bug#10128: am_foo_OBJECTS is empty when ...

Stefano Lattarini writes: > On 01/02/2012 07:24 PM, Sebastian Freundt wrote: >> >> Well, I'm trying to build objects that will be linked later on, only that >> the linker is a lisp compiler, and that compiler can read .lisp, .fasl, .o >> and .so. As in raw lisp

bug#12877: automake error: unrequested trace ''

shell> automake --version automake (GNU automake) 1.12.1 autoreconf: running: automake --add-missing --copy --force-missing Use of uninitialized value $macro in exists at /home/freundt/usr/bin/automake line 5267, line 2. Use of uninitialized value $macro in concatenation (.) or string at /home/

bug#12877: automake error: unrequested trace ''

Stefano Lattarini writes: > tags 12877 + moreinfo > thanks > > Hi Sebastian, thanks for the report. > > On 11/13/2012 11:30 AM, Sebastian Freundt wrote: >> shell> automake --version >> automake (GNU automake) 1.12.1 >> >> autoreconf: running: automak

bug#12877: Autoconf, GNU m4 and POSIXLY_CORRECT

"Stefano Lattarini" writes: > [+cc autoconf] > > On 11/14/2012 07:45 AM, Sebastian Freundt wrote: >> Stefano Lattarini writes: >> >>> tags 12877 + moreinfo >>> thanks >>> >>> Hi Sebastian, thanks for the report. >>&g

bug#12877: Autoconf, GNU m4 and POSIXLY_CORRECT

"Stefano Lattarini" writes: > tags 12877 - moreinfo > tags 12877 notabug > close 12877 > thanks > > On 11/14/2012 12:09 PM, Sebastian Freundt wrote: >> >> "Stefano Lattarini" writes: >>> >>> On 11/14/2012 07:45 AM, Sebastian F

bug#16205: automake 1.14 chokes on file names with `='

Consider following Makefile.am: noinst_PROGRAMS = footool footool_SOURCES = foo=bar.c footool_CPPFLAGS = -DVERSION=4.0 processed with automake 1.14, autoconf 2.69, yields: /usr/share/automake-1.14/am/depend2.am: error: bad characters in variable name 'footool-foo' /usr/share/automake-1.14/am/depe