Re: Running make for autoconf V2.13 with HP-UX 11.0

> > I am trying to build autoconf V2.13 for HP-UX 11.0 > Ah, then this is the explanation of it all :) [...] autoconf-2.13 should build out of the box on hpux 11.0. At least I had no trouble with building it there. However, you will really want the functionality of autoconf-2.50 and the associa

prefix:subpaths macro anyone? i.e. moveable packages

Hi everyone, has someone somewhen written some ac-macro to detect the subpaths of a prefixed installation? The idea is to have a moveable package where the compilation prefix path is just the default that can be changed at runtime. hmm, consider a package named 'foo' that has a bin/foo, a lib/

Re: Ultrix autotest/autoconf problem

A first quick reading seems to demonstrate you found a flow in the test suite itself, we should not conditionally run tests. Better have them be skipped. Thanks, I'll keep you informed!

Force alternate path for lib?

Hi all, How would I go about forcing an alternate path for a libraray to be used in my project? For example, I have libfoo installed in /usr/local, and I have a development version installed in /usr/local/libfoo-dev. I have another software module that uses libfoo; usually I would just add a --wi

Ultrix autotest/autoconf problem

Here's the log generated from running: % sh -x ./testsuite 1 >& sh-x.log --- + test -n + test -n + expr a : \(a\) as_expr=expr + rm -f conf23322 conf23322.exe conf23322.file + echo + ln -s conf23322.file conf23322 + test -f conf23322.exe as_ln_s=ln -s + rm -f conf23322 conf23322.exe conf

RE: testsuite problem

> Niah? I don't understand. Are you telling us that your host does not > honor PATH assignments? Hmm - right - I think I was seeing this wrong... > This is not good, as we don't mean to pass the new PATH to conftest, > rather we want to have the shell change its own PATH, and *then* to > look f

Re: Autoconf testing results.

Pavel Roskin <[EMAIL PROTECTED]> writes: > Hello, Akim! > > > Ash 0.2 is already burned for being too broken. Does it fail > > gracefully? Is the user warned properly? > > It dumps core gracefully, without saying a single word: > > $ ash configure > Segmentation fault That seems like a mess

Re: testsuite problem

"Tim Van Holder" <[EMAIL PROTECTED]> writes: > You _might_ be running into a pathsep bug. > > acgeneral.m4 runs > > PATH=".;`pwd`"; conftest.sh > > to check whether ';' works as pathsep. But because of the ';' after > the PATH assignment, conftest gets the regular path. Niah? I don't

Re: Autoconf testing results.

Hello, Akim! > Ash 0.2 is already burned for being too broken. Does it fail > gracefully? Is the user warned properly? It dumps core gracefully, without saying a single word: $ ash configure Segmentation fault > Could you had this limitation in the documentation? If we make a patch, the doc

Re: testsuite problem

You _might_ be running into a pathsep bug. acgeneral.m4 runs PATH=".;`pwd`"; conftest.sh to check whether ';' works as pathsep. But because of the ';' after the PATH assignment, conftest gets the regular path. So if your regular PATH contains the current dir, autoconf will assume ';' i

Re: Autoconf testing results.

Pavel Roskin <[EMAIL PROTECTED]> writes: > Hello! > > Here are some results. I didn't try to investigate the problems. Instead > I tried to get a general picture. That's good, thanks! >RedHat Linux 7.0 > bash-2.04: ok > >RedHat Linux 6.2 > bash-1.14.7: ok (very rare intermittent failu

Re: Harlan Stenn:

Unfortunately you have an Autotest problem, not an Autoconf problem. I think there is nothing better than sh -x ./testsuite 1 >log 2>&1 to do here. Thanks!