On 12/29/2012 04:10 AM, Stefano Lattarini wrote:
> ## -------------------------------------- ##
> ## GNU Autoconf 2.69.59-adc84 test suite. ##
> ## -------------------------------------- ##

Thanks for the report.

> 
>  NUM: FILE-NAME:LINE     TEST-GROUP-NAME
>       KEYWORDS
> 
>  132: autotest.at:300    Tested programs
>       autotest

I've reproduced this locally, and hope to have it fixed soon (eek, my
day is almost over, and I'm still stalled with getting m4 1.4.17
released, because that turned up some needed gnulib work; so it looks
like autoconf 2.70 will have a 2013 copyright, rather than my original
goal of releasing today).

>  355: go.at:30           Go

Hmm, I wasn't able to reproduce this one yet; probably indicates I need
to install go on my devel machine, but even then, I have no idea what to
do there.


> ## ---------------------- ##
> ## Detailed failed tests. ##
> ## ---------------------- ##
> 
> #                             -*- compilation -*-
> 132. autotest.at:300: testing Tested programs ...

> +++ /home/stefano/src/ac/autoconf/tests/testsuite.dir/at-groups/132/stdout    
> 2012-12-29 11:07:33.000000000 +0100
> @@ -1,3 +1,4 @@
>  autoconf --version
>  autom4te --version
> +autoconf --version

This looks weird - why is 'autoconf --version' being tested twice?
Hopefully the fix is easy.


> #                             -*- compilation -*-
> 355. go.at:30: testing Go ...
> ./go.at:30: autoconf --force -W obsolete
> ./go.at:30: /bin/sh -n configure
> stderr:
> ./go.at:30: autoheader
> ./go.at:30: ./configure $configure_options -C
> --- /dev/null 2012-12-29 08:28:46.151945383 +0100
> +++ /home/stefano/src/ac/autoconf/tests/testsuite.dir/at-groups/355/stderr    
> 2012-12-29 11:20:36.000000000 +0100
> @@ -0,0 +1,4 @@
> +configure: error: in `/home/stefano/src/ac/autoconf/tests/testsuite.dir/355':
> +configure: error: cannot run Go compiled programs.
> +If you meant to cross compile, use `--host'.
> +See `config.log' for more details

Is this indicative of a problem with your environment, rather than the
autoconf testsuite?

>> configure:2051: gccgo -o conftest   conftest.go  >&5
>> configure:2055: $? = 0
>> configure:2077: result:
>> configure:2103: checking whether we are cross compiling
>> configure:2111: gccgo -o conftest   conftest.go  >&5
>> conftest.go:4:14: error: too many arguments

Or, maybe it is indicative of missing shell quoting in the macros for Go
compilation.  Is this something you can research a bit more?

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to