Re: Troubles with proc*C and automake version 1.10

Hi, thanks for the answer. I've tried removing the verifierCoherence.c and put the verifierCoherence.pc in the verifierCarte_SOURCES but the Makefile.in isnt generated : automake: reading COHERENCE/Makefile.am automake: Sources ending in .pc become .c automake: Sources ending in .c become .o aut

Re: silent build rules

On Wed, 1 Apr 2009, Eric Blake wrote: What's to say that the only reason the default was so verbose was because nobody had a better option? I personally like the quieter builds, because it makes warnings much easier to identify and eliminate. Yes, of course. But identifying and eliminating w

Re: silent build rules

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [dropping m4-discuss] According to Bob Friesenhahn on 4/1/2009 1:32 PM: >> As I wrote off-list already, unless you use the 'silent-rules' option >> for your packages, your code should be built as always. > > This new m4 release is the first package I

Re: Convenience programs

John Calcote wrote: Russell, On 4/1/2009 4:47 AM, Russell Shaw wrote: ... /Makefile.am should contain: SUBDIRS = ... keysyms ... src ... Just makesure keysyms is given before src in that list. Thanks, it works now:)

Re: silent build rules

On Wed, 1 Apr 2009, Ralf Wildenhues wrote: * Bob Friesenhahn wrote on Wed, Apr 01, 2009 at 09:32:54PM CEST: My opinion is that if this mode is optional that it should default to "off" It defaults to off. It is enabled if the *developer* (Makefile.am author) chooses so. I take it you sugges

Re: Multiply distributed files

Hello Akim, Peter, revisiting an old thread: that deals with essentially the same issue as PR 533, * Akim Demaille wrote on Tue, May 30, 2006 at 03:54:48

Re: silent build rules

* Bob Friesenhahn wrote on Wed, Apr 01, 2009 at 09:32:54PM CEST: > > My opinion is that if this mode is optional that it should default to > "off" It defaults to off. It is enabled if the *developer* (Makefile.am author) chooses so. I take it you suggest that it default to on only if *both* th

Re: silent build rules

Hello John, can we try *not* to add more mailing lists, and limit on-topic replies to the libtool lists? For others, please just start a new thread on the list that seems the most appropriate; thanks! * John Calcote wrote on Wed, Apr 01, 2009 at 10:08:33PM CEST: > > Is there any command-line opt

Re: silent build rules

While we're on the issue of Automake silent rules, I've got a comment about Libtool hiding half of it's compiles.(Thus, I've added the libtool list as well.) I was recently building a project that failed without an error message, while running under "non-silent" mode, or the original GNU build

Re: GNU M4 1.4.13 released (stable)

On Wed, 1 Apr 2009, Eric Blake wrote: At this point, it seems like it might be a good idea for the use of 'automake --silent-rules' to add a configure option that sets the default state of the V make variable for a user's taste. That is, you would still have to request automake to issue silent-

Re: silent build rules (was: GNU M4 1.4.13 released (stable))

On Wed, 1 Apr 2009, Ralf Wildenhues wrote: * Eric Blake wrote on Wed, Apr 01, 2009 at 08:52:36PM CEST: According to Bob Friesenhahn on 4/1/2009 12:40 PM: It seems that I will need to permanently define and export the arbitrary variable 'V' in my shell environment in order to avoid confusion l

silent build rules (was: GNU M4 1.4.13 released (stable))

* Eric Blake wrote on Wed, Apr 01, 2009 at 08:52:36PM CEST: > According to Bob Friesenhahn on 4/1/2009 12:40 PM: > > > > It seems that I will need to permanently define and export the arbitrary > > variable 'V' in my shell environment in order to avoid confusion later > > since I won't know how a

Re: GNU M4 1.4.13 released (stable)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [adding some lists; I'm assuming you are okay with that] According to Bob Friesenhahn on 4/1/2009 12:40 PM: > I was able to build ok but was not sure if the right tools were being > used in the build since I could not see what it was doing. Then I >

Re: Spurious testsuite failures

Hello Andreas, * Andreas Schwab wrote on Wed, Apr 01, 2009 at 02:35:49PM CEST: > I'm getting several failures in the automake testsuite, for example: > > FAIL: libtool.test (exit: 1) > + aclocal-1.10b -Werror -Wno-syntax -I > /home/andreas/src/osc/automake/BUILD/automake-1.10b/tests/../m4 -I >

Re: Dealing with .asm files

Hello Robert, * Robert Homann wrote on Wed, Apr 01, 2009 at 01:21:42PM CEST: > > Duplicating rules seemed all wrong to me, so I tried adding '.asm' right > after '.s' to the corresponding register_language() call in automake > instead, and it just worked then. > > Now, would it hurt to add this

Re: tracking dependencies of built sources

Hello, * dherr...@ll.mit.edu wrote on Tue, Mar 31, 2009 at 06:00:37PM CEST: > I'm using Qt 4's moc to generate source files in an autotools project. > > The pattern looks something like > > cat <<_EOF > Makefile.am > # Makefile fragment > bin_PROGRAMS=test > test_SOURCES=a.cpp b.cpp > test_META=a.

Re: Troubles with proc*C and automake version 1.10

Hallo Annie, * acprdoer wrote on Wed, Apr 01, 2009 at 03:16:04PM CEST: > The project has migrated to solaris 10 and a new version of automake > (1.10.2), it was previously on Solaris 8 with an automake version 1.4. The > automake dos not produce any makefile.in on the new server : it says : > >

Re: tracking dependencies of built sources

Never mind. Sometimes it is bad to work late at night. I had convinced myself the following did not work. For the record, here's the fixed makefile On Tue, 31 Mar 2009, dherr...@ll.mit.edu wrote: I'm using Qt 4's moc to generate source files in an autotools project. The pattern looks somet

Re: Convenience programs

Russell, On 4/1/2009 4:47 AM, Russell Shaw wrote: Hi, In //keysyms, i have a Makefile.am and it generates a "genkeysyms" program in C. //src contains a Makefile.am and it generates source files in this directory using ../keysyms/genkeysyms, then uses these sources in the rest of the compile

Troubles with proc*C and automake version 1.10

Hi, The project has migrated to solaris 10 and a new version of automake (1.10.2), it was previously on Solaris 8 with an automake version 1.4. The automake dos not produce any makefile.in on the new server : it says : automake: reading COHERENCE/Makefile.am automake: Sources ending in .pc becom

Re: Object files in subfolders

On Wednesday 2009-04-01 15:21, Johnson, Chris wrote: > >src / > foo / > bar.cpp > baz / > bar.cpp > >Once I run my bootstrap command I get something like the following error > >Error: src/Makefile.am: object bar.$(OBJEXT) created by foo/bar.cpp and >baz/bar.cpp > >Basically I'd li

Object files in subfolders

All - I have code base I'm working with that contains a bunch of sub directories and cpp files. The problem I'm having is my bootstrap script fails because I have two files with the same name in different sub folders for example: src / foo / bar.cpp baz / bar.cpp Once I run my

Spurious testsuite failures

I'm getting several failures in the automake testsuite, for example: FAIL: libtool.test (exit: 1) /home/andreas/src/osc/automake/BUILD/automake-1.10b/tests:/opt/kde3/bin:/home/andreas/bin/ccache:/home/andreas/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bi

Dealing with .asm files

Hi! Recently, I worked on a not-yet-autoconfiscated project that contains files with .asm extensions. These files should be treated just like .s files by Automake, but Automake doesn't know the .asm extension, urging me to duplicate the rules for .s files in this project (the maintainer would like

Convenience programs

Hi, In //keysyms, i have a Makefile.am and it generates a "genkeysyms" program in C. //src contains a Makefile.am and it generates source files in this directory using ../keysyms/genkeysyms, then uses these sources in the rest of the compile. //src/Makefile.am has: keysyms.tab.include: ../keysy