Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Sat, 24 Jun 2000 12:12:36 -0400
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Testing a freshly built cygwin1.dll
Message-ID: <20000624121236.D6591@cygnus.com>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To: cygwin AT sourceware DOT cygnus DOT com
References: <39546C79 DOT 1A29935 AT wanadoo DOT fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <39546C79.1A29935@wanadoo.fr>; from gilles.rajaobelina@wanadoo.fr on Sat, Jun 24, 2000 at 10:08:26AM +0200

On Sat, Jun 24, 2000 at 10:08:26AM +0200, Gilles-Claude Rajaobelina wrote:
>Is there any recommended way to "safely" test a freshly built winsup in
>the real worlds?
>After the build completed, I issued
>
>$ make -w check
>
>which failed as:
>
>make: Entering directory `/obj/winsup/src'
>make[1]: Entering directory `/obj/winsup/src/etc'
>make[1]: Nothing to be done for `check'.
>make[1]: Leaving directory `/obj/winsup/src/etc'
>make[1]: Entering directory `/obj/winsup/src/libiberty'
>make[2]: Entering directory `/obj/winsup/src/libiberty/testsuite'
>echo 'int prepends_underscore = 0;' > test-us.c
>gcc -DHAVE_CONFIG_H -g -O3 -I..
>-I/src/CYGWIN/winsup/src/libiberty/testsuite/../../include  -o
>test-filter -DMAIN -DVERSION='"none"' -DHAVE_CONFIG_H \
> /src/CYGWIN/winsup/src/libiberty/testsuite/../cplus-dem.c test-us.c
>-L.. -liberty
>/tmp/cc5CIort.o: In function `consume_count_with_underscores':
>/src/CYGWIN/winsup/src/libiberty/testsuite/../cplus-dem.c:556: undefined
>reference to `_imp___ctype_'
>/src/CYGWIN/winsup/src/libiberty/testsuite/../cplus-dem.c:530: undefined
>reference to `_imp___ctype_'
>/src/CYGWIN/winsup/src/libiberty/testsuite/../cplus-dem.c:531: undefined
>reference to `_imp___ctype_'
>/src/CYGWIN/winsup/src/libiberty/testsuite/../cplus-dem.c:537: undefined
>reference to `_imp___ctype_'
>/tmp/cc5CIort.o: In function `cplus_demangle_opname':
>/src/CYGWIN/winsup/src/libiberty/testsuite/../cplus-dem.c:687: undefined
>reference to `_imp___ctype_'
>/tmp/cc5CIort.o:/src/CYGWIN/winsup/src/libiberty/testsuite/../cplus-dem.c:1271:
>more undefined references to `_imp___ctype_' follow
>collect2: ld returned 1 exit status
>make[2]: *** [test-filter] Error 1
>make[2]: Leaving directory `/obj/winsup/src/libiberty/testsuite'
>make[1]: *** [check-subdir] Error 2
>make[1]: Leaving directory `/obj/winsup/src/libiberty'
>make: *** [check-libiberty] Error 2
>make: Leaving directory `/obj/winsup/src'
>Command exited with non-zero status 2

The _imp___ctype errors are an indication of linking with an old cygwin
import library.  You should not be linking with older objects or libraries.
Any .o or .a has to be recompiled.

We do not have much of a testsuite currently but what is available is in
winsup/testsuite.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com