Re: GNU Automake 1.10.1 released

Hello Ralf, On Tue, 22 Jan 2008, Ralf Wildenhues wrote: > Hello Tim, > > * Tim Rice wrote on Tue, Jan 22, 2008 at 06:57:59PM CET: > > On Tue, 22 Jan 2008, Ralf Wildenhues wrote: > > > > > I'm pleased to announce the release of Automake 1.10.1. > > > > Any reason this never made it in? > >

Re: GNU Automake 1.10.1 released -- bug #516 is still there

Hello Peter, * Peter Breitenlohner wrote on Tue, Jan 22, 2008 at 10:03:02AM CET: > > more than a year ago I filed a bug report (automake#516), after sending an > email some month earlier: There are lots of bugs that have not beed addressed before 1.10.1, some are way older and more important than

Re: GNU Automake 1.10.1 released

Hello Tim, * Tim Rice wrote on Tue, Jan 22, 2008 at 06:57:59PM CET: > On Tue, 22 Jan 2008, Ralf Wildenhues wrote: > > > I'm pleased to announce the release of Automake 1.10.1. > > Any reason this never made it in? > http://lists.gnu.org/archive/html/bug-automake/2005-10/msg00016.html Dunno

Re: linking source files from a different directory macro

Hello Jason, * Jason Roscoe wrote on Tue, Jan 22, 2008 at 01:17:55PM CET: > Ralf Wildenhues wrote: >> You can use AC_CONFIG_LINKS from Autoconf: >> >>

Compiling project requiring w/ source requiring different compilers

Hi everyone, I am currently learning the ins and outs of automake and I am attempting to incorporate it into a project I am working on. I have run into an issue that has me at wits end as I can't seem to find a way around it. I have a project that will be comprised of two key subbranches: one c

New mailing list automake-commit

The new mailing list will soon receive git commit messages for the Automake repository. I find it cleaner if automake-patches is left for discussion of patches, and typically the mere commit notices lack space to add some rationale and so o

Re: Automake (alpha) release request

Hello Sebastian, * Sebastian Pipping wrote on Tue, Jan 22, 2008 at 09:28:23PM CET: > > Things I noticed about the new release: > > * The GNU FTP Automake directory [2] holds a .sig.sig file: > automake-1.10.1.tar.bz2.sig.sig . Is this by intention? No, that was due to a typo. Oh well, it was

Re: Automake (alpha) release request

Sebastian Pipping wrote: If the FSF handles this problem also putting out a non-alpha-non-beta 1.11 release of Automake before 2008-02-01 I will donate k Euros to the FSF with k equal the number of days left to that deadline, e.g. if Automake 1.11 is released on 2008-01-31 I will donate

Re: GNU Automake 1.10.1 released

On Tue, 22 Jan 2008, Ralf Wildenhues wrote: > I'm pleased to announce the release of Automake 1.10.1. Any reason this never made it in? http://lists.gnu.org/archive/html/bug-automake/2005-10/msg00016.html -- Tim RiceMultitalents(707) 887-1469 [EMAIL PRO

Re: linking source files from a different directory macro

On Tue, 22 Jan 2008, Jason Roscoe wrote: I also saw AC_CONFIG_LINKS but I wasn't sure it would be appropriate for what I was trying to do. I'll have a look at it again. One other thing is that I would like the links to be removed during a 'make clean' step, e.g.. Do you know offhand if AC_

Re: GNU Automake 1.10.1 released -- bug #516 is still there

On Tue, 22 Jan 2008, Ralf Wildenhues wrote: I'm pleased to announce the release of Automake 1.10.1. Automake is a tool Very good, BUT more than a year ago I filed a bug report (automake#516), after sending an email some month earlier: automake generated Makefiles install manpages from

Re: linking source files from a different directory macro

Ralf Wildenhues wrote: You can use AC_CONFIG_LINKS from Autoconf: or there is AC_PROG_LN_S, which allows you to use $(LN_S) in rules in Makefile.

Re: GNU Automake 1.10.1 released

Hello, * NightStrike wrote on Tue, Jan 22, 2008 at 09:43:20AM CET: > On 1/21/08, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > - Fix order of standard includes to again be `-I. -I$(srcdir)', > >followed by directories containing config headers. > > What was it before the fix?

Re: GNU Automake 1.10.1 released

On 1/21/08, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > - Fix order of standard includes to again be `-I. -I$(srcdir)', >followed by directories containing config headers. What was it before the fix?