automake-1.6.1: both developers try their fixes

I write this to both lists (kde-devel,automake) to avoid problems because both developers try to fix the automake-1.6.1/KDE3 problem: On Tue, 23 Apr 2002, Alexandre Duret-Lutz wrote: > >>> "Joerg" == Joerg Anders <[EMAIL PROTECTED]> writes: > > [...] > > Joerg> But what do you recommend to do?

Le dernier sondage avant les éléctions présidentielles 2002 !

Title: Untitled Document En partenariat avec Le dernier sondage avant le second tour des élections présidentielles

Re: Thanks! And question!

>>> "Joerg" == Joerg Anders <[EMAIL PROTECTED]> writes: [...] Joerg> But what do you recommend to do? Just relax and wait for the next Automake release :) -- Alexandre Duret-Lutz

Thanks! And question!

On Tue, 23 Apr 2002, Alexandre Duret-Lutz wrote: > That's easy to fix. For instance edit m4/depout.m4 and change > > if (sed 1q $mf | fgrep 'generated by automake') > /dev/null 2>&1; then > > to something like > > if (sed 15q $mf | fgrep 'generated by automake') > /dev/null 2>&1; then > Thi

Re: automake1.4/1.6.1 more precise

>>> "Joerg" == Joerg Anders <[EMAIL PROTECTED]> writes: [...] Joerg> make -f admin/Makefile.common Joerg> If you now: Joerg> ./configure --prefix= --with-qt-dir= Joerg> make [...] Joerg> Makefile:405: .deps/main.Po: No such file or directory Joerg> Makefile:406: .deps/noteedit.Po: No suc

automake1.4/1.6.1 more precise

On 23 Apr 2002, Richard Boulton wrote: > Of course they work. There are many people using such releases. with KDE3 ??? > However, as with all software, there are some bugs (both known and > unknown), and some incompatibilities with previous versions. Please > work with us to help solve the pr

RE: non-recursive project example

> -Original Message- > From: Alexandre Duret-Lutz [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 23, 2002 10:48 PM > To: Robert Collins > Cc: Tim Waugh; [EMAIL PROTECTED] > Subject: Re: non-recursive project example > > > >>> "Robert" == Robert Collins > <[EMAIL PROTECTED]> writes

Re: non-recursive project example

>>> "Robert" == Robert Collins <[EMAIL PROTECTED]> writes: [...] Robert> When did it get fixed? >> >> 1.6.1 Robert> That'll be it then. I'll leave it as it is until 1.5 Robert> fades from use... Maybe I was not clear: if you simply remove the `VERSION=' prefix it will work as you inten

RE: non-recursive project example

> -Original Message- > From: Alexandre Duret-Lutz [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 23, 2002 10:26 PM > To: Robert Collins > Cc: Tim Waugh; [EMAIL PROTECTED] > Subject: Re: non-recursive project example > > > >>> "Robert" == Robert Collins > <[EMAIL PROTECTED]> writes

Re: non-recursive project example

>>> "Robert" == Robert Collins <[EMAIL PROTECTED]> writes: Robert> When did it get fixed? 1.6.1 -- Alexandre Duret-Lutz

RE: non-recursive project example

> -Original Message- > From: Alexandre Duret-Lutz [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 23, 2002 10:07 PM > To: Robert Collins > Cc: Tim Waugh; [EMAIL PROTECTED] > Subject: Re: non-recursive project example > > > >>> "Robert" == Robert Collins > <[EMAIL PROTECTED]> writes

Re: non-recursive project example

>>> "Robert" == Robert Collins <[EMAIL PROTECTED]> writes: [...] Robert> AUTOMAKE_OPTIONS = dist-bzip2 subdir-objects VERSION=1.5 Where does this `VERSION=1.5' usage comes from? That the second time I see it. AFAICT this relies on a bug in Automake which has been fixed in 1.6.1. This should

Re: Automake a case study

On Tue, Apr 23, 2002 at 12:24:59AM -0600, Calvin Arndt wrote: > Project/Makefile.am > > SUBDIRS = project > docsdir = $(datadir)/project/docs ^^^ use $(PACKAGE), it's more flexible > docs_DATA = project/docs/* In older releases of automake, you would have to write a di

Re: automake > 1.4 does not work

Joerg Anders writes: > Unfortunately I'm not a autoconf/automake guru. > But I think I can state: automake > 1.4 does not work. > > I can't say exactly what's wrong. But please try to > use automake 1.6 togehther with the KDE3 default > admin files. And you'll see: It is impossible. Nobody here

RE: non-recursive project example

Here's one.. I've got another more complete example with installable libraries and headers if needed, but it's somewhat longer. This is a trimmed down file from a current project. Rob ## Process this file with automake to produce Makefile.in # # $Id: Makefile.am,v 1.3 2002/01/13 14:16:17 robertc

non-recursive project example

Does anyone have a small example project using automake that is free of recursive makes? I'm not quite sure how it is supposed to work, so I don't know if the things I'm seeing when I try to convert a (currently flat) project to non-flat, non-recursive style are intended or not. Thanks, Tim. */

Re: automake > 1.4 does not work

On Tue, 2002-04-23 at 11:04, Joerg Anders wrote: > Unfortunately I'm not a autoconf/automake guru. > But I think I can state: automake > 1.4 does not work. Of course they work. There are many people using such releases. However, as with all software, there are some bugs (both known and unknown),

Re: configure: AM_PROG_LEX: command not found

Did you read below? At Tue, 23 Apr 2002 10:34:17 +0200, Alexandre Duret-Lutz wrote: >> older version of aclocal. In all cases, please run aclocal >> before running automake. -- Nishio Futoshi <[EMAIL PROTECTED]>

Re: configure: AM_PROG_LEX: command not found

>>> "Joerg" == Joerg Anders <[EMAIL PROTECTED]> writes: [...] >> In all cases, please run aclocal before running automake. Joerg> Ok! This works! Thank you! Joerg> But now appears the next problem: Joerg> $ cat configure.in Joerg> AC_INIT(hello.c) Joerg> AM_INIT_AUTOMAKE(hello, 1.3.11)

automake > 1.4 does not work

Unfortunately I'm not a autoconf/automake guru. But I think I can state: automake > 1.4 does not work. I can't say exactly what's wrong. But please try to use automake 1.6 togehther with the KDE3 default admin files. And you'll see: It is impossible. You get a lot of errors. And if you bring it

configure: AM_PROG_LEX: command not found

On Tue, 23 Apr 2002, Alexandre Duret-Lutz wrote: > This means that either you didn't run aclocal and don't have an > aclocal.m4; or you have an aclocal.m4 but it was generated by an > older version of aclocal. In all cases, please run aclocal > before running automake. > Ok! This works! Thank

Re: building/installing Python modules?

>>> "Skip" == Skip Montanaro <[EMAIL PROTECTED]> writes: Skip> I'm trying to figure out how to compile and link a Python Skip> extension module. The Python support in Automake is very limited. Basically, Automake knows how to byte-compile a python script and where to install it, but that's

RE: Creting extra executables.

Always create the gui makefile. Use a configure substitution to change the value of SUBDIRS, and use DIST_SUBDIRS to ensure that all the code gets distributed. Rob

Re: automake -a -f does not help

>>> "Joerg" == Joerg Anders <[EMAIL PROTECTED]> writes: [...] Joerg> $ automake -f -a Joerg> /usr/share/automake/am/depend2.am: AMDEP does not appear Joerg> in AM_CONDITIONAL This means that either you didn't run aclocal and don't have an aclocal.m4; or you have an aclocal.m4 but it was gen

Creting extra executables.

I've an application that has a directory structure like this. ./src ./src/non_gui ./src/gui In the non_gui directory there are about 6 binaries, which will build easily one any system. In the gui directory, there is currently one (probably more later) binaries that require all sorts of librarie

automake -a -f does not help

On Tue, 23 Apr 2002, Nishio Futoshi wrote: > Hi! > > Please use -a option for automake (and you need -f option, maybe). > > At Mon, 22 Apr 2002 19:00:53 +0200 (CEST), > Joerg Anders wrote: > > $ automake > > automake: configure.in: required file `./depcomp' not found > This does not help: $ aut

Automake a case study

I have a small project Directory Structure looks like this: /Project/ ---> Build system files go here | | |__/project/ ---> C src and headers go here | | |___/docs ---> *.txt *.doc *.html Project/Makefile.am SUBDIRS = project docsdir