RE: FW: GNU Autoconf 2.68] testsuite: 14 80 140 211 227 231 232 233 237 238 239 241 242 244 245 246 247 249 251 303 304 307 308 309 310 311 312 316 319 320 321 324 325 326 327 342 485 failed

[Joachim Schmitz]

Here's the winzip'ed version of testsuite.log and
testsuite.dir/080/script...

Bye, Jojo
-----Original Message-----
From: Eric Blake [mailto:address@hidden 
Sent: Tuesday, December 28, 2010 8:30 PM
To: Joachim Schmitz; address@hidden
Subject: Re: FW: GNU Autoconf 2.68] testsuite: 14 80 140 211 227 231 232 233
237 238 239 241 242 244 245 246 247 249 251 303 304 307 308 309 310 311 312
316 319 320 321 324 325 326 327 342 485 failed

On 12/26/2010 01:34 PM, Joachim Schmitz wrote:
> From: Joachim Schmitz [mailto:address@hidden
> Sent: Saturday, December 25, 2010 10:08 PM
> To: 'address@hidden'
> Subject: GNU Autoconf 2.68] testsuite: 14 80 140 211 227 231 232 233 
> 237 238
> 239 241 242 244 245 246 247 249 251 303 304 307 308 309 310 311 312 
> 316 319
> 320 321 324 325 326 327 342 485 failed

>
>
> Here's the result of me trying to port Autoconf 2.68 to HP NonStop
>

Thanks for the report (it ended up off-list because of size restrictions
rejecting the uncompressed attachment).  Here's some response to the first
few failures:

> #                             -*- compilation -*-
> 14. tools.at:478: testing autoconf: subdirectories ...
> ./tools.at:495: autoconf --force
> ./tools.at:496: ./configure $configure_options
> 0a1
>> sed: /datarootdir/ is not a recognized function.
> stdout:

Ouch - where are we invoking sed in such a way that a missing variable
expansion resulted in an invalid sed script?  Huh, this may be more fallout
of test 80...

> #                             -*- compilation -*-
> 80. m4sh.at:398: testing AS_ECHO and AS_ECHO_N ...
> ./m4sh.at:435: autom4te --language=m4sh script.as -o script
> ./m4sh.at:436: $CONFIG_SHELL ./script
> diff: Missing new line at the end of file
/home/jojo/Floss/autoconf-2.68/tests/testsuite.dir/at-groups/80/stderr.
> 0a1
>> AS_ECHO('^G^HAS_ECHO_N('^G^H
> 80. m4sh.at:398: 80. AS_ECHO and AS_ECHO_N (m4sh.at:398): FAILED 
> (m4sh.at:436)

The fact that there were literal BEL and BackSpace bytes (^G^H) in that
diff, rather than backslash sequences \a\b, makes me think that we're
botching echo detection for your shell.  Can you look at
tests/testsuite.dir/080/script, and make sure there are no literal BEL or BS
bytes?  And if that is the case (I hope it is, since autoconf is supposed to
generate machine-independent output), then it boils down to a question of
determining what your shell did during execution; showing the complete
output of

sh -vx tests/testsuite.dir/080/script

may help us get to the bottom of this.

I haven't looked any further at your failures, but if we can't even get
AS_ECHO right, I have no idea how many other testsuite failures are due to
fallout.

-- 
Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

testsuite.zip
Description: Zip compressed data

script.zip
Description: Zip compressed data