Re: yaccvpath.test

Hello, Alexandre! > Pavel> It fails on RedHat 6.2, but not 7.0. I believe it's a > Pavel> Perl issue. Not sure if I'll have time today to look at > Pavel> this. It's not Perl. It's a timestamp quantization. Some unices (including GNU/Linux) are not very precise with respect to the timestamps

Re: `make dist' with srcdir != builddir

Tom> I think what we want is for the positioning of the .c file not to Tom> matter for the developer, but for the file to end up in the Tom> distribution made by `make dist'. adl> The following is how I intended to fix this. I'm not sure adl> it's what you want. Anyway the patch below won't app

Re: Testsuite fails

> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes: adl> Is it an "ok" for my proposal or a "no, keep it as it is now"? adl> Right now, I would have to call AC_CHECK_TOOL([STRIP],[strip]) adl> in my configure.in *before* calling AM_INIT_AUTOMAKE to make adl> thinks work. Yeah. I thi

Re: *.o not in src_dir

> "Carsten" == Carsten Menn <[EMAIL PROTECTED]> writes: >> $ cd $(srcdir) >> $ mkdir bin-i686-linux; cd bin-i686-linux >> $ ../configure --prefix=... Carsten> thank you for your quick response. Carsten> Unfortunately that's not exactly what I wanted. Carsten> The OS and the architecture sh

Re: How about making it ten times faster?

On Tue, Feb 27, 2001 at 08:53:57PM +0100, [EMAIL PROTECTED] wrote: : How about making it ten times faster? Nah, it's fine like it is. Don't fix it if it's not broke, etc... ;-P Lars J

Re: How about making it ten times faster?

Instead of `eval $command' line per line in file_contents, just slurp it, and run the regexps *once*.

How about making it ten times faster?

Before the patch: ~/src/am/automake --amdir=/home/akim/src/am 7.84s user 0.06s system 92% cpu 8.535 total after: ~/src/am/automake --amdir=/home/akim/src/am 0.84s user 0.03s system 99% cpu 0.870 total I still have details to fix, but it's nothing important. Since it's fun finding ideas, I

Re: *.o not in src_dir

On Tue, Feb 27, 2001 at 08:12:33PM +0100, Carsten Menn wrote: : >> I have a simple (I hope so) problem. What I want to do is : >> to compile my project for/on different operating-systems. : >> I want to have only one src-directory and several : >> subdirectories like '$(srcdir)/bin-i686-linux' or

Re: yaccvpath.test

Hello, Alexandre! > >> Alexandre claims it fails. > > Yes it should. Then show us how it fails. > Perl? I guess you have found *another* issue :) What I'm trying We'll see when I get home. > to report is just a Makefile issue: $scrdir/parser.c is included > in the distribution insted of ./p

Re: *.o not in src_dir

>> I have a simple (I hope so) problem. What I want to do is >> to compile my project for/on different operating-systems. >> I want to have only one src-directory and several >> subdirectories like '$(srcdir)/bin-i686-linux' or >> '$(srcdir)/bin-sun-solaris-2.7', etc... > >Very simple. > > $

Re: yaccvpath.test

>>> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes: Pavel> Hello, Tom and Alexandre! Pavel> On 27 Feb 2001, Tom Tromey wrote: [...] >> Alexandre claims it fails. Yes it should. >> I've updated it a bit. Now it works for me. >> Alexandre, can you investigate the change? I will check

Re: `make dist' with srcdir != builddir

>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes: [...] Tom> I think what we want is for the positioning of the .c file not to Tom> matter for the developer, but for the file to end up in the Tom> distribution made by `make dist'. The following is how I intended to fix this. I'm not sure

Re: yaccvpath.test

> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes: Pavel> It fails on RedHat 6.2, but not 7.0. I believe it's a Perl Pavel> issue. Not sure if I'll have time today to look at this. I'm running 6.2 and it works for me. Tom

Re: *.o not in src_dir

Hi, Carsten Menn <[EMAIL PROTECTED]> writes: > I have a simple (I hope so) problem. What I want to do is > to compile my project for/on different operating-systems. > I want to have only one src-directory and several > subdirectories like '$(srcdir)/bin-i686-linux' or > '$(srcdir)/bin-sun-solar

Re: instdata2.test fails

My bad, and I don't know why :( I just moved %exec_dir_p right before am_install_vars, and it resulted in the failure you reported. I guess that a var must be visible before its first caller (when the first to initiate the chain that results in its consultation), which is something I had not und

Re: yaccvpath.test

Hello, Tom and Alexandre! On 27 Feb 2001, Tom Tromey wrote: > > "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes: > > Pavel> I don't quite understand whether your test is supposed to work > Pavel> or not. It's failing for me (besides the typo in > Pavel> tests/Makefile.am that I've just f

instdata2.test fails

Hello! I presume that tests not listed in XFAIL_TESTS are supposed to work. instdata2.test doesn't work for me. I'm compiling Automake (from CVS as of Tue Feb 27 15:44:08 UTC 2001) in a separate directory, and the only test that fails is instdata2.test: $ make check TESTS="instdata2.test" VERBO

*.o not in src_dir

Hello, I have a simple (I hope so) problem. What I want to do is to compile my project for/on different operating-systems. I want to have only one src-directory and several subdirectories like '$(srcdir)/bin-i686-linux' or '$(srcdir)/bin-sun-solaris-2.7', etc... All the generated *.o and the *

Re: dist-all

Tom Tromey <[EMAIL PROTECTED]> writes: > Akim -- > > I think one of your patches probably broke `make dist-all'. > > Right now it ends up depending on each dist target that is used. > However each such target ends by removing the dist directory. > The point of having dist-all is that it is more