bug-autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNU Autoconf 2.57] testsuite: 64 65 66 67 failed


From: Gerard Tromp
Subject: [GNU Autoconf 2.57] testsuite: 64 65 66 67 failed
Date: Sat, 1 Nov 2003 17:49:48 -0500

   To: <address@hidden>
   Subject: [GNU Autoconf 2.57] testsuite: 64 65 66 67 failed

Greetings!

Trying to build autoconf.
System:
======
SunOS penrose 5.8 Generic_108528-15 sun4u sparc SUNW,Ultra-60

make check resulted in a huge number of failures

50 52 53 54 57 58 61 65 66 68 70 73 75 76 81 83 84 90 105 111 128 130 132
133 134
135 136 138 139 141 142 143 144 145 146 147 150 152 154 155 158 159 161 162
165
166 167 171 173 (testsuite.log1)


The vast majority were due to "Broken Pipe" at the start of each test.
I was running the tests under bash v 2.0.3.


Running the tests under the standard Solaris Bourne shell (/bin/sh) made
mosts of the
errors go away.

failures under /bin/sh
64 65 66 67 (testsuite.log)

these failures are due to the lack of the -R option to force recording of
the
path to shared library in the compiled binary.
I need to figure out which command-line options to pass to configure to
register use of
-R/path/to/libs


At any rate I thought it may be of use to know that the shell can influence
the behavior
of the tests.

Gerard
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Gerard Tromp, Ph.D.                             vox: 313-577-8773
Center for Molecular Medicine and Genetics      fax: 313-577-7736
Wayne State Univ. Schl. of Medicine
540 E. Canfield, Detroit, MI 48201    address@hidden
                                mailto:address@hidden
                                     http://cmmg.biosci.wayne.edu



Context of "Broken Pipe" errors:
52. c.at:111: testing AC_PROG_CPP with warnings...
c.at:127: autoconf
c.at:127: autoheader
c.at:127: top_srcdir=$abs_top_srcdir ./configure
0a1
> Broken Pipe
stdout:
checking for gcc... /opt/SUNWspro/bin/cc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... no
checking whether /opt/SUNWspro/bin/cc accepts -g... yes
checking for /opt/SUNWspro/bin/cc option to accept ANSI C... none needed
checking how to run the C preprocessor... /opt/SUNWspro/bin/cc -E
checking for egrep... egrep
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... no
checking for unistd.h... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking autoconf_io.h usability... no
checking autoconf_io.h presence... no
checking for autoconf_io.h... no
configure: creating ./config.status
config.status: creating config.h
./../../c.at:127: config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by configure, which was
generated by GNU Autoconf 2.57.  Invocation command line was

  $ ./configure



Attachment: testsuite.log
Description: application/sas-log

Attachment: testsuite.log1
Description: Binary data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]