Re: Patch: init.m4

Hi Jim! | Akim Demaille <[EMAIL PROTECTED]> writes: | | Maybe this patch could be rejected/discussed/applied? | | I've applied it. But removed the periods you added here: Thanks! | +[AC_DEFINE_UNQUOTED(PACKAGE, "$PACKAGE", [Name of package.]) | +AC_DEFINE_UNQUOT

Re: pb with @ substitution

IIUC, what you're trying to do is not recommended by the GNU standards, this is why it's hard to performed. The motivation is that you should be able to make prefix=/foo so `configure' is not supposed to hard code the value of `prefix' that it knows. At least for part of your issue, th

Re: help2man

I like Brendan's patch, appended here for convenience. It was sent to Autoconf@. Akim --- missing.origThu May 4 22:23:50 2000 +++ missing Thu May 4 22:21:48 2000 @@ -43,6 +43,7 @@ automake touch all \`Makefile.in' files bisoncreate \`y.tab.[ch]', if po

Re: help2man

Could someone apply this patch?

Re: shall `make uninstall' remove directories?

> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes: Pavel> Let's make "missing" handle "mkdir -p" to begin with. Maybe Pavel> install-sh could be wrapped into missing as well. I absolutely agree, but I'm not sure `missing' is a good start. Let's dive into shtool too, there might be good

Re: shall `make uninstall' remove directories?

> "ois" == ois Pinard writes: > So, if `missing' ever replaces `install-sh' and `mkinstalldirs', > this should be seen as a good thing, absolutely in the spirit of the > design of `missing'. I share your opinion. And to answer to the fact that missing is currently part of the Automake ki

Re: shall `make uninstall' remove directories?

> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes: > "David" == Masterson, David <[EMAIL PROTECTED]> writes: David> Would those complaints be really due to "too many files" David> (ie. size issue) or "too many files with questionable purpose"? Tom> Actually I think it is not size (in byte

Re: shall `make uninstall' remove directories?

>> Akim > François >> Honestly, I see no difference between plenty of small utilities and >> one big. > Oh, each supplementary file we distribute is a bit of a burden to > the maintainer (Auto- tools could help here :-), but more > importantly, one more bit of pollution each tim

Re: shall `make uninstall' remove directories?

> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes: >> While we're at it, don't you think we should build a single file >> `STUFF' which contains NEWS, COPYING, AUTHORS, THANKS, TODO, >> ABOUT-NLS, ChangeLog, INSTALL, README etc.? Let's face it: there >> is plenty of useless files in ther

Re: shall `make uninstall' remove directories?

Hi François ! | > While we're at it, don't you think we should build a single file | > `STUFF' which contains NEWS, COPYING, AUTHORS, THANKS, TODO, | > ABOUT-NLS, ChangeLog, INSTALL, README etc.? Let's face it: there is | > plenty of useless files in there, nobody cares! | | Somebody cares! D

Re: shall `make uninstall' remove directories?

>>>>> "Peter" == Peter Eisentraut <[EMAIL PROTECTED]> writes: Peter> Akim Demaille writes: >> I agree that `mkdir -p' belong to the spirit of `missing', but I >> certainly have no problems with `mkinstalldirs', Peter> H

Re: shall `make uninstall' remove directories?

| [`configure'] is also a product. Yet, we do not distribute the full | Autoconf and Automake within each distribution. What is needed for easy | maintenance is at least some good access to sufficient Autoconf (and | Automake) snapshots, turned into fetchable distributions (probably not CVS).

Re: RANLIB error when using automake.

> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes: Alexandre> I'm not sure I agree with that. It sounds perfectly Alexandre> reasonable to me to have automake request for the user to Alexandre> add AC_PROG_RANLIB to configure.in. I agree. In fact the whole problem is to keep thin

Re: The correct use of wildcards in Makefile.am

> "Bram" == Bram Stolk <[EMAIL PROTECTED]> writes: Bram> Hello configurators, I could not find this in the docs: how can Bram> I use wildcards correctly in Makefile.am ? By not using them at all. It is on purpose that they are not supported in Automake. If you really mean to do that, you s

Re: Why does ltconfig unset CC?

| +AC_DEFUN(AC_PROG_LIBTOOL,[AC_REQUIRE([_AC_PROG_LIBTOOL]) | +# If AC_PROG_CXX has already been expanded, run AC_LIBTOOL_CXX | +# immediately, otherwise, hook it in at the end of AC_PROG_CXX. | + AC_PROVIDE_IFELSE([AC_PROG_CXX], | +[AC_LIBTOOL_CXX], | +[define([AC_PROG_CXX], defn([AC_PR

Re: -c -o

> "Martin" == Martin Wilck <[EMAIL PROTECTED]> writes: Martin> Are you aware of the fact that automake inserts -c -o in the Martin> build rule automatically? This makes the usefulness of this Martin> test even more questionable, at least in connection with Martin> automake. I'm all for the

Re: automake vs. autoconf 2.14a

> "Johan" == Johan Danielsson <[EMAIL PROTECTED]> writes: Johan> What's the deal? If you run autoconf -W obsolete you get a Johan> bunch of warnings for automake stuff. The objective is to release the next Automake independently of the changes in Autoconf, so that people are not obliged to u

Re: Fortran dependency tracking

> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes: Tom> Also, writing a dependency tool in a portable way seems hard. In particular if you consider the lexical flexibility of Fortran. It is reasonable to require a particular form of include/INCLUDE etc. from the maintainers who are making th

Re: -c -o

> "Peter" == Peter Eisentraut <[EMAIL PROTECTED]> writes: Peter> If I'm redefining the .c => .o pattern rule for my purposes Peter> (e.g., dependency generation) then I need to know whether the Peter> compiler supports -c -o, otherwise I have to do something like Peter> cc && mv. Please keep

Re: per target built sources patch v3

Hi Alex, I'm no Automake maintainer, so you may just forget everything I will say :) I think your patch addresses a very interesting issue, and it would be great to apply it, but it's getting very big. If there are independent chunks in it, you should try to keep them separate. Also, if possib

Re: 25-ac-lang-compiler-inext

| Dear Akim Demaille, you wrote on Today: | > Maybe we should AC_SUBST the result? This might be important for | > Automake to see if it needs a wrapper for compilers which refuse the | > traditional extensions? | | > I've tested this patch like this: | > | &

Re: per target built sources patch v3

> "Alex" == Alex Hornby <[EMAIL PROTECTED]> writes: Alex> If I was to do this, would someone with CVS access consider Alex> applying them in a timely manner? I suspect I might go mad Alex> trying to maintain five source trees for any length of time. I'm OK with handling this, but I don't fee

Re: -c -o

> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes: Akim> What would Automake (or missing) need to know? Tom> Whether the compiler can support the extensions actually in use Tom> by the program. This is an ugly problem because it involves Tom> feedback from Makefile.am to configure. Nope, I

Re: -c -o

> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes: Martin> And then, for full functionality, automake should use that Martin> variable in generating rules, right? Martin> .c.o: $(CC) $(CFLAGS) ... @CC_C_O@ $< Tom> This won't be sufficient. Automake will need more information. Such as? Tom

Re: -c -o

> "Lassi" == Lassi A Tuura <[EMAIL PROTECTED]> writes: Lassi> IMHO there shouldn't be a restriction to a single extension Lassi> though; all three of .cc, .cxx and .cpp are all quite Lassi> acceptable and projects should be free to choose the Lassi> conventions. It seems we are going to some

patch: Style of the m4 files

n $1; do > case " $CONFIG_HEADERS " in > *" $am_file "*) > echo timestamp > `echo $am_file | sed 's%:.*%%;s%[^/]*$%%'`stamp-h$am_indx > ;; > esac > am_indx=`expr "$am_indx" + 1` > done]) Index: ChangeLog ===

Re: patch: Style of the m4 files

>>>>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes: Akim> OK to install? It's basically only an update of the conventions, you don't need to get into the gory details. If no-one says no, I'll apply it tomorrow.

Re: patch: Style of the m4 files

>>>>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes: >>>>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes: Akim> OK to install? Akim> It's basically only an update of the conventions, you don't need Akim&g

Re: getopt_long

Compile getopt1.c and getopt.c unconditionally on all platforms, it has its own magic for the platforms that already have it. Akim

bug#11419: Get rid of ylwrap, and simplify yacc/lex rules: withdrawn this wishlist entry

On Sat, Jan 12, 2013 at 8:18 PM, Stefano Lattarini wrote: > tags 11419 wontfix > close 11419 > thanks > > Reference: > > > The improvements to the ylwrap script contributed by Akim in the 1.12.x > and 1.13 releases have fixed most of the issues

Re: [Automake-NG] Removal of INCLUDES in favour of AM_CPPFLAGS

Le 1 févr. 2013 à 10:35, Stefano Lattarini a écrit : > So, is anyone using or playing with Automake-NG, or at least > contemplating the idea to do so in the short term? Or should > we just let the project die? I subscribe to all the good opinions about NG that have been made here. I would de

Re: Suggestion: AC_DEFINE -> m4_pattern_allow

>>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes: Hi! Some time ago I sent this message for which I had no answer. > I have this package at hand, say FooBar, which installs a prefixed > form of config.h. Its own macros are, of course, named FB_*, which i

Re: Suggestion: AC_DEFINE -> m4_pattern_allow

Le 31 mai 06 à 18:38, Stepan Kasal a écrit : Hello, * Akim Demaille wrote on Wed, May 31, 2006 at 04:26:17PM CEST: I suggest that Automake provide the same feature for AM_CONDITIONAL: well, you already implemented it, granting Alexandre one point for his hint: http://lists.gnu.org

Re: Suggestion: AC_DEFINE -> m4_pattern_allow

>>> "Ralf" == Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Hi Akim, > * Akim Demaille wrote on Wed, May 31, 2006 at 04:26:17PM CEST: >> >>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes: >> >> Some time ag

Re: Suggestion: AC_DEFINE -> m4_pattern_allow

>>> "Stepan" == Stepan Kasal <[EMAIL PROTECTED]> writes: > Hello, >> * Akim Demaille wrote on Wed, May 31, 2006 at 04:26:17PM CEST: >> > I suggest that Automake provide the same feature for AM_CONDITIONAL: > well, you already implemented it

install-local -> uninstall-local

It would probably make sense to have a warning in case a Makefile.am has install-*-local rules but no uninstall-local. BTW, I must say I don't really understand why, at least to keep symmetry, all the install-*-local targets are mapped to a single uninstall-local one. That there is one is nice, b

AM_EXTRA_DIST

ISTR that there was a means, via a macro traced by Automake, that there was a means to ask it to automatically ship some files. Something similar to AC_LIBSOURCES, but more general. I can't find anything like this. Did I dream about it?

Best means to override CXXFLAGS locally

I have this cross-compiler at hand that cannot compile some of my big files (a Bison parser) with -O2. Stacking -O0 on top of -O2 does the trick. But I don't know the recommended way to do that. Since I'd like to the keep the good old -g -O2 for the rest of the compilation, since I don't want t

Re: Best means to override CXXFLAGS locally

What would be the cleanest means to handle this exception? Here is what I did: - Force automake to generate an object specific rule by using some foo_CXXFLAGS - Open Makefile.in, get the specific rules. - Use LTCOMPILECXX to factor the common part - Append $(MY_NOPTION_CXXFLAGS) to it - rename

EXTRA_PROGRAMS vs. clean

Sorry if this is a faq, but I have found nothing convincing, excepted this unanswered message: http://sourceware.org/ml/bug-automake/2001/msg00391.html and http://sources.redhat.com/ml/bug-automake/2003/msg00311.html where adl seems to agree it should be cleaned. I don't understand

Re: EXTRA_PROGRAMS vs. clean

While we're one that topic, I don't understand why cleaning the tags is hooked to distclean instead of clean.

Re: Best means to override CXXFLAGS locally

>>> "Ralf" == Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Hello Akim, > * Akim Demaille wrote on Sun, Oct 22, 2006 at 01:10:02PM CEST: >> >What would be the cleanest means to handle this exception? >> >> Here is what I did: > I t

AM_LIBADD

For the records, I could use AM_LIBADD as a default value of libfoo_la_LIBADD. Currently it is not recognized.

Re: ``install -C'' / unnecessarily updating time stamps

Le 25 déc. 06 à 11:46, Thomas Schwinge a écrit : [I added the patch's author, Akim Demaille, to the cc list, as it was not sure if he's still reading the list.] You're right, I'm not. Hello! Hi, and merry Chrismas. On Sun, Dec 24, 2006 at 04:21:50PM -0800, Paul E

Re: running tests in parallel

It would be nice if it were possible to run tests in parallel using automake. Waiting for tests to complete on a 4-way box while they are run on a single CPU is annoying. As most 'make' implementations already support running in parallel (-j), automake could just utilize this functionality to

Re: AM_LIBADD

>>> "RW" == Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Hello Akim, Hi Ralk, I missed your answer :) > * Akim Demaille wrote on Fri, Nov 03, 2006 at 05:56:16PM CET: >> >> For the records, I could use AM_LIBADD as a default value of >>

Re: AM_LIBADD

>>> "RW" == Ralf Wildenhues <[EMAIL PROTECTED]> writes: >> Hi Ralk, I missed your answer :) > Hehe, interesting typo. Ralph is a more common one. ;-) How bizarre... I don't how I managed to get this one kucked up. The feys are not even close! > Sure. I think the addition of AM_LIBADD/t

Re: prog_LDADD at the end of the linking command line

Le 19 oct. 07 à 19:16, Ralf Wildenhues a écrit : Hello Benoit, * Benoit SIGOURE wrote on Fri, Oct 19, 2007 at 06:48:25PM CEST: # Add boost libraries. AM_CXXFLAGS += $(BOOST_CPPFLAGS) AM_LDFLAGS += $(BOOST_LDFLAGS) $(BOOST_THREAD_LIB) Don't put libs (-l...) in LDFLAGS, it messes up the ord

Re: parallel testsuite execution

>>> "RW" == Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Hello Benoit, Hi Ralf, Sorry for answering so late... > Can you rid it of nonportable constructs, and more importantly, can it > be included in Automake (copyright transfered to the FSF etc.)? Sure, no problems. > Hmm, let's see.

Re: parallel testsuite execution

>>> "RW" == Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Hello Akim, Hi Ralf, >> So I would like to be able to write something like >> >> TEST_SUITES = foo bar >> foo_TESTS = foo1.chk foo2.test foo3 >> bar_TESTS = bar1.test bar2.sh bar3.c >> >> and be able to write on the side rules e

Feature request

Hi friends! I have a suggestion. I'm slowly getting rid of my recursive Makefiles. Instead I have one local.mk per directory, and a few Makefile.ams that include them. Of course I have to prefix all my file names with the name of the directory, and I find that this explicit name is actua

Re: Feature request

Le 23 sept. 08 à 23:08, Ralf Wildenhues a écrit : Hi Akim, Hi Ralf! * Akim Demaille wrote on Tue, Sep 23, 2008 at 04:35:50PM CEST: I'm slowly getting rid of my recursive Makefiles. Instead I have one local.mk per directory, and a few Makefile.ams that include them. Of course I ha

Re: [Fakeroot PATCH] Use transformed library name while testing.

Le 9 déc. 08 à 23:57, Clint Adams a écrit : [For the automake guys, the question is whether it's possible to have a computed name for a (libtool) library.] On Tue, Dec 09, 2008 at 10:44:44PM +0100, Akim Demaille wrote: I have written this because that's how it appears in

Enhancing nobase_

Hi autofriends! nobase_ is really a nice feature to cope with a structured hierarchy of files. But it does not work well with packages that avoid recursive Makefiles. In my case for instance, my package has a hierarchy of files in $(top_srcdir)/include, but it has no include/ Makefile.am

Re: Enhancing nobase_

Le 19 mars 09 à 14:53, Ralf Corsepius a écrit : Akim Demaille wrote: Hi autofriends! nobase_ is really a nice feature to cope with a structured hierarchy of files. But it does not work well with packages that avoid recursive Makefiles. In my case for instance, my package has a

Dependencies bw LTLIBRARIES at install time

Hi all, I might have missed the information, but I believe there are no instruction about handling the dependencies bw libraries are install time (they all live in the same Makefile.am, and I do not want to break it). I have libfoo that depends on libbar, and both are installed in differ

dist_noinst_MANS

Hi all, Currently Automake accepts happily such a variable name, but it does not use it (the files are not dist'ed). I agree EXTRA_DIST is fine, but I'm used to being able to use dist_noinst_* as a kind of over-specification. Cheers, Akim

Re: VPATH in automake

> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes: Tom> I'm suprised config.status removes the line. # Any assignment to VPATH causes Sun make to only execute # the first set of double-colon rules, so remove it if not needed. # If there is a colon in the path, we need to keep it. if test "x$s

Re: [Automake] Making a Distribution

> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes: Pavel> Try placing AM_MAINTAINER_MODE into configure.in. Gross! Yuck yuck yuck. And in French, Blââheuurk! Pavel> But why do you want to remove .am files? Aaah! That's much better ;)

Re: RFC: Default output destination

| Hello, Jim and others! Hi Pavel! | > Is it that behavior documented? The documentation says: With all the source in a single file, you use the following command to convert it into a parser file: @example bison @var{file_name}.y @end example

Re: RFC: Default output destination

| On Mon, Oct 02, 2000 at 05:48:26PM +0200, Akim Demaille wrote: | : (And BTW, why the heck is there this `tab' part?) | | I believe it is short for "table" - the compiler parser is based on using a | state transition table or something along those lines. That's my guess

Re: PATCH: Copyright pedantry

Since this patch is trivial, and since I was wandering around here, I applied it. Akim

subdir4.test

`lib/depcomp' not found | : > depcomp it fails: | ../../tests/subdir4.test: depcomp: Permission non accordée | FAIL: subdir4.test So I'd like to apply this patch: Index: tests/ChangeLog from Akim Demaille <[EMAIL PROTECTED]> * subdir4.test (depcomp): Don't create

Re: [PATCH] compare header files before installing

This patch seems OK to me, but I'd appreciate if Alexandre, Tom, Pavel or Jim could confirm it's OK.

Re: [PATCH] SGI dependency tracking bugfix

| Re-resending this patch. | 2000-06-04 Morten Eriksen <[EMAIL PROTECTED]> | | * depcomp: fixed bug in sgi dependency tracking mode with | sourcecode files which does not contain any dependencies to other | source files. Thanks, applied. It looks sane, and you've bee

Re: Avoiding cross-dependencies for aclocal.m4

This guy looks good to me. Any objection? -- Hello! "ACLOCAL_AMFLAGS = -I ." causes circular dependencies. The patch fixes this problem, eliminates an extra occurence of acinclude.m4 and strips "./" from the remaining macro fi

Re: [PATCH] Dependency tracking for Microsoft Visual C/C++

| Hi, | this patch implements support for extracting dependency tracking | information by using the preprocessor mode of the Microsoft Visual | C/C++ compiler. Thanks, installed. Could someone explain to me why we launch it in background and then just wait for it to complete?

Re: [PATCH] Dependency tracking for Microsoft Visual C/C++

> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes: Alexandre> We compute dependencies in parallel with the actual Alexandre> compilation, but we mustn't consider the job done before Alexandre> both are complete. Ah! Yes, I overlooked the ` "$@" '. Thanks!

Re: Avoiding cross-dependencies for aclocal.m4

>>>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes: Alexandre> On Oct 16, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote: >> This guy looks good to me. Any objection? Alexandre> Nope. Pavel, you still consider this patch alive?

Re: PATCH: depcomp cpp method output

| 2000-06-21 Alex Hornby <[EMAIL PROTECTED]> | | * depcomp: Altered sed clause to strip of inclusion depth | numbers generated by cpp. Also output in gcc style. | | Index: depcomp | === | RCS file: /cvs/automake/au

Re: Help-regd. error while compiling automake1.4 on hpux11.00

| I am getting the foll. error message when I am trying to build | automake 1.4 on 11.00 hpux machine: You said it all: HPUX. Their Make is incredibly broken and is often responsible of build failures. I would *strongly* encourage you to install GNU Make and use this one only.

Re: Help-regd. error while compiling automake1.4 on hpux11.00

> "Thomas" == Thomas E Dickey <[EMAIL PROTECTED]> writes: Thomas> give an example of how it's broken. I never managed to track it down precisely. But for instance with Bison and a2ps, the only problems I has with gettext 0.10.33 were people using HPUX Make. For a time I tried to find the o

Re: Help-regd. error while compiling automake1.4 on hpux11.00

| Hi, | Thanks for replying. | | But I am getting the error even if I use the gmake. | | Making all in . | gmake[1]: Entering directory `/home/praveen/automake-1.4' | gmake[1]: Nothing to be done for `all-am'. | gmake[1]: Leaving directory `/home/

Re: Help-regd. error while compiling automake1.4 on hpux11.00

> "Praveen" == Praveen Kumar Amritaluru <[EMAIL PROTECTED]> writes: Praveen>As can be seen from the above message, there is no Praveen> action associated with the targets. As a result nothing is Praveen> getting done under these two directories m4 and tests. That's right, nothing to

Re: Help-regd. error while compiling automake1.4 on hpux11.00

| > > "Praveen" == Praveen Kumar Amritaluru <[EMAIL PROTECTED]> writes: | > | > Praveen>As can be seen from the above message, there is no | > Praveen> action associated with the targets. As a result nothing is | > Praveen> getting done under these two directories m4 and tests. | > | >

Re: CVS HEAD and parallel make install

Any problem with installing this guy? It seems fine to me. -- Alexandre, Heres an Automake patch and changelog entry allow make -j install on such degenerate systems (and Linux with buggy libtool ) If you install to location

Re: per target built sources patch v3

Hi Alex, | I could split it into four or five patches (that would be | incrementally applied) e.g: | | 1) gcc style cpp depcomp | 2) patsubst style variable substitution | 3) suffix supplied dependencies | 4) improved suffix rule recognition | 5) per target built source hooks. | | I would be w

Re: per target built sources patch v3

> "Alex" == Alex Hornby <[EMAIL PROTECTED]> writes: Alex> I've been busy on other things for a while, but I would Alex> definitely like to get these patches in, and I am heartened by Alex> the application of my depcomp patch :) :) Alex> I'll see if I can get the patsubst patch out next week

Re: [PATCH] Fix for CRLF problem

| Index: ChangeLog | === | RCS file: /cvs/automake/automake/ChangeLog,v | retrieving revision 1.891 | diff -u -r1.891 ChangeLog | --- ChangeLog 2000/10/06 22:49:14 1.891 | +++ ChangeLog 2000/10/09 14:43:56 | @@ -1,3 +1,12 @@ | +2

Re: PATCH: patsubst support

| Akim, Hi Alex, Glad to see your progresses! | Here is a patch to add patsubst support to value_to_list. I've | included a new test case "patsubst.test" as well. That's great news! Thanks a lot! But I'm going to be a pain, especially because I'm not the official maintainer of Automake, an

Re: PATCH: patsubst support

> "Alex" == Alex Hornby <[EMAIL PROTECTED]> writes: Alex> Akim, Alex> Okay, here is patsubst patch v2. Thanks! Alex> The _PROGRAMS based example in the documentation needs a Alex> patsubst supporting make (e.g. GNU and Solaris work). This is Alex> because the program target writes prog_SOU

Re: PATCH: patsubst support

| Akim Demaille writes: | > | > Sorry, I'm confused, and the documentation snippet didn't really | > enlighten me :( | > | | Hi Akim, | | The reasoning was fairly tortured :) | | To document the patsubst internal change I had to invent a contrived | example so t

Re: Fix for script magic.

| On Nov 1, 2000, François Pinard <[EMAIL PROTECTED]> wrote: | > [Pavel Roskin] | >> >From Autoconf documentation: | | >> | >> If you omit the space before the path, then 4.2BSD based systems | >> (such as Sequent DYNIX) will ignore the line, because they interpret | >> `#!

Re: Targets using automake

> "Derek" == Derek R Price <[EMAIL PROTECTED]> writes: Derek> This could be a very useful tool but without this feature I Derek> cannot use it in good conscience. What's wrong with the `missing' approach? What version of Automake are you using? I'm using CVS Automake for my package, and ne

Re: Targets using automake

> "Derek" == Derek R Price <[EMAIL PROTECTED]> writes: Derek> What's the 'missing' approach? When autoconf or automake is not found, the script `missing' is then used, and touches the products. ~/src/am % ./missing --help nostromo 17:21 ./missing [OPTION

Re: Targets using automake

>>>>> "Derek" == Derek R Price <[EMAIL PROTECTED]> writes: Derek> Akim Demaille wrote: >> What's wrong with the `missing' approach? Derek> I ran automake the first time without the '--add-missing' Derek> argument so when it told

Re: [PATCH] Output files with LF only

> "Morten" == Morten Eriksen <[EMAIL PROTECTED]> writes: Morten> Hi, someone mis-applied my patch so that ``binmode'' was set s/someone/akim/ Morten> _after_ Automake had opened a file for writing. Sorry Morten, I'm applying your patch. Thanks!

Re: Problem with @SHELL@ substitution

> "phane" == phane Genaud writes: phane> Hi, on a Irix 6.5 system, using automake 1.4, autoconf 2.12 Please, consider upgrading at least of 2.13. If the trouble persists, give a try to CVS Autoconf (See http://sources.redhat.com/autoconf/ for details), and report bugs against this CVS Auto

Re: AC_CONFIG_FILES with macro parameters

> "Johan" == Johan Danielsson <[EMAIL PROTECTED]> writes: Johan> Suppose I have something like: Johan> AC_DEFUN(FOO, [AC_CONFIG_FILES($1/Makefile)]) Johan> FOO(somedir) Johan> This works fine with autoconf, but is there some way to Johan> convince automake about this construct? Is there an

Re: Can't CVS checkout behind my firewall

> "Tim" == Tim Heath <[EMAIL PROTECTED]> writes: Tim>I can't checkout the latest release of automake becuase I am Tim> behind a corporate firewall. Can anyone tar it up and put it Tim> somewhere that I can ftp it from? It would be greatly Tim> appreciated as I am extremely close to bein

CVS Autotools

I'm happy to say that running the test suites of both Libtools and of Automake with CVS Autoconf works fine.

Re: [PATCH] etags support

Index: m4/init.m4 === RCS file: /cvs/automake/automake/m4/init.m4,v retrieving revision 1.20 diff -u -r1.20 m4/init.m4 --- m4/init.m4 2000/10/10 00:18:52 1.20 +++ m4/init.m4 2000/12/21 18:07:02 @@ -54,6 +54,7 @@ # some

Re: Ultrix problem

> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes: Harlan> checking whether build environment is sane... yes Harlan> /bin/sh: \272: not found Alexandre> What if you take the quotes off "$prog" ? Harlan> That seems to be the ticket! Warf warf warf! 272 = 200 (8th bit) + 72 (ascii

Support for configure.ac

Akim Index: ChangeLog from Akim Demaille <[EMAIL PROTECTED]> Let Automake support `configure.ac'. * automake.in: In the comments, prefer `configure.ac' to `configure.in'. When using &am_conf_error, don't repeat `in configure.in', since the function al

automake-m4-cleanup.patch

Index: ChangeLog from Akim Demaille <[EMAIL PROTECTED]> * m4/multi.m4: Remove the hairy useless quotation of `$'. Simplify `ifelse([$2],,,[$2])' into... `$2'! * m4/minuso.m4: Don't use changequote! * m4/cond.m4: Fix quotati

Re: Support for configure.ac

If there are no objections, I'll apply this guy on Tuesday.

Re: Automake: Compiling sources in other directories

> "Dave" == Dave Brolley <[EMAIL PROTECTED]> writes: Dave> FWIW, I'm working around this for now using VPATH: Dave>VPATH=$(srcdir):../host Dave> and specifying h1.cpp without a path in in Dave> libfred_la_SOURCES. Seems to work OK. Is this supported? Expect problems with Autoconf...

Re: Automake: Compiling sources in other directories

> "Dave" == Dave Brolley <[EMAIL PROTECTED]> writes: Dave> No problems so far. What kind of problems are you expecting? It likes removing VPATH definitions from Makefiles. Many people complain about that, but I confess I never really tried to understand what the problem was. I just know th

Re: Support for configure.ac

Will be applied within a couple of minutes.

Re: automake-m4-cleanup.patch

Applied.

<    1   2   3   4   5   6   7   8   9   10   >