FreeBSD and QNX - first results

Hello! One thing was broken recently: /bin/sh -n autoconf doesn't work on FreeBSD and QNX if autoconf is not in the current directory. This patch should probably be reverted, at least partially: 2000-10-23 Akim Demaille [EMAIL PROTECTED] * tests/tools.m4: Globally, don't use `../'

Re: FreeBSD and QNX - first results

| Hello! | One thing was broken recently: | | /bin/sh -n autoconf | | doesn't work on FreeBSD and QNX if autoconf is not in the current | directory. No kidding!?! That's only with `-n' or any `sh autoconf' will fail? | This patch should probably be reverted, at least partially: I'm taking

autoupdate requires GNU sed

bor@itsrm2% ./autoupdate --help autoupdate requires GNU sed Just curious, what are the reasons behind it? This is with current CVS. cheers -andrej Have a nice DOS! B

Re: autoupdate requires GNU sed

"Andrej" == Andrej Borsenkow [EMAIL PROTECTED] writes: Andrej bor@itsrm2% ./autoupdate --help autoupdate requires GNU sed Andrej Just curious, what are the reasons behind it? This is with Andrej current CVS. It uses regexps that are not supported by other seds, which is just one aspect of the

RE: autoupdate requires GNU sed

"Andrej" == Andrej Borsenkow [EMAIL PROTECTED] writes: Andrej bor@itsrm2% ./autoupdate --help autoupdate requires GNU sed Andrej Just curious, what are the reasons behind it? This is with Andrej current CVS. It uses regexps that are not supported by other seds, which is just one aspect

Re: autoupdate requires GNU sed

"Andrej" == Andrej Borsenkow [EMAIL PROTECTED] writes: Andrej 1. Currently, it prevents me (and everybody without GNU sed) Andrej from making autoconf: That's a bug in CVS. Run touch man/autoupdate.1. Andrej 2. I've installed GNU sed as gsed, but autoconf's confgiure Andrej does not even

Re: autoupdate requires GNU sed

"Andrej" == Andrej Borsenkow [EMAIL PROTECTED] writes: Andrej 1. Currently, it prevents me (and everybody without GNU sed) Andrej from making autoconf: Admittedly `autoupdate --help/--version' should not fail when GNU Sed is not installed. I'll fix that.

Re: No, I *don't* HAVE_IO_H!

On Oct 23, 2000, David Andrew Michael Noelle [EMAIL PROTECTED] wrote: Can anyone tell me what might cause this? A config.cache or config.site that incorrectly sets cache variables. -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer

Re: FreeBSD and QNX - first results

Hello, Akim! | Hello! | One thing was broken recently: | | /bin/sh -n autoconf | | doesn't work on FreeBSD and QNX if autoconf is not in the current | directory. No kidding!?! That's only with `-n' or any `sh autoconf' will fail? Any "sh autoconf": [proski@fonzie proski]$ ash

Re: Success (mostly) with the testsuite

Hi Pavel, Did you download Neutrino or QNX 4? My uname -r says H (I hoped for 425!) As was said in other email the fix is to do the proper quoting and have it done consistently - this will probably mean autoconf will then work on QNX 4. So I think the only thing that was broken for 4.25 was

Re: Success (mostly) with the testsuite

Hi All, Since there was no tarball;) I thought I would checkout the CVS just to have some fun. I started to test here and there, and got some positive tests (make checks) with a SPARC(-clone) running Solaris 7. Just a tiny weird thing, it ignored every test in update.m4: 125. ./update.m4:10

Re: Success (mostly) with the testsuite

Hello, David! Did you download Neutrino or QNX 4? My uname -r says H (I hoped for 425!) It was a 91M ISO image from http://packages.qnx.com/download/qnxrtp.iso I think it is called Neutrino. As was said in other email the fix is to do the proper quoting and have it done consistently - this

Re: Success (mostly) with the testsuite

Pavel Roskin wrote: Hello, David! Did you download Neutrino or QNX 4? My uname -r says H (I hoped for 425!) It was a 91M ISO image from http://packages.qnx.com/download/qnxrtp.iso I think it is called Neutrino. Neutrino is very different from QNX 4 - it is more Unix compliant - I

Re: FreeBSD and QNX - first results

On Oct 24, 2000, Pavel Roskin [EMAIL PROTECTED] wrote: Any "sh autoconf": Yep. Not all shells search the PATH for a script. The problem is that requiring GNU sed for autoupdate is essentially requiring GNU sed for the testsuite which means not testing other sed's Good point. --

Re: Success (mostly) with the testsuite

Pavel Roskin wrote: Hello, David! Neutrino is very different from QNX 4 - it is more Unix compliant - I think :) I see. You can also mail me /bin/sh. I hope we'll not be prosecuted for that :-) But as you don't have the same OS do you still want it? At least I could try to

Re: Success (mostly) with the testsuite

Hi Pavel I have investigated further The best I can come up with so far is the line that does the sed replacement. /^X\(\/\).*/{ s//\1/p; q;} When presented with ac_file=Makefile this substitution is returning . XMakefile which I am not sure where we get this from. It seems to work

Re: Success (mostly) with the testsuite

Hello, Daniele! Since there was no tarball;) I thought I would checkout the CVS just to have some fun. I started to test here and there, and got some positive tests (make checks) with a SPARC(-clone) running Solaris 7. Just a tiny weird thing, it ignored every test in update.m4: 125.