Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 28 Apr 2002 12:28:36 +0200 To: cygwin Subject: How do I get an up to date dejagnu (1.4.2 or cvs) on cygwin? Message-ID: <20020428102836.GA28060@j-son.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i From: =?iso-8859-1?Q?Christian_J=F6nsson?= I am trying to run the test suite of gcc under windows xp/cygwin. Gcc needs dejagnu that is of version newer than what cygwin has as a regular package. I thus would like to build a newer version myself. I tried the dejagnu-1.4.2.tar.gz sources, on configure and make, only this was done: chj AT D90V2D0J /usr/local/src/objdir-dejagnu $ make Making all in doc make[1]: Entering directory `/usr/local/src/objdir-dejagnu/doc' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/local/src/objdir-dejagnu/doc' make[1]: Entering directory `/usr/local/src/objdir-dejagnu' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `/usr/local/src/objdir-dejagnu' chj AT D90V2D0J /usr/local/src/objdir-dejagnu $ same this with a cvs sources based build. However, there is something bothering me that shows up while configuring: $ head -20 configure.log checking for a BSD compatible install... /usr/bin/install -c checking whether build environment is sane... yes /usr/local/src/dejagnu/missing: Unknown `--run' option Try `/usr/local/src/dejagnu/missing --help' for more informa configure: WARNING: `missing' script is too old or missing checking for mawk... no checking for gawk... gawk checking whether make sets ${MAKE}... yes checking whether to enable maintainer-specific portions of M checking whether make sets ${MAKE}... (cached) yes checking for gcc... gcc checking for C compiler default output... a.exe checking whether the C compiler works... yes checking whether we are cross compiling... no checking for executable suffix... .exe checking for object suffix... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for style of include used by make... GNU checking dependency style of gcc... none chj AT D90V2D0J /usr/local/src/objdir-dejagnu $ so I run the missing script with --help: $ /usr/local/src/dejagnu/missing --help /usr/local/src/dejagnu/missing [OPTION]... PROGRAM [ARGUMENT]... Handle `PROGRAM [ARGUMENT]...' for when PROGRAM is missing, or return an error status if there is no known handling for PROGRAM. Options: -h, --help display this help and exit -v, --version output version information and exit Supported PROGRAM values: aclocal touch file `aclocal.m4' autoconf touch file `configure' autoheader touch file `config.h.in' automake touch all `Makefile.in' files bison create `y.tab.[ch]', if possible, from existing .[ch] flex create `lex.yy.c', if possible, from existing .c lex create `lex.yy.c', if possible, from existing .c makeinfo touch the output file yacc create `y.tab.[ch]', if possible, from existing .[ch] chj AT D90V2D0J /usr/local/src/objdir-dejagnu $ the aclocal, auto*, bison, flex, and makeinfo are there. Adding symlinks from byacc to yacc and from flex to lex dows not change the "failure" on configury. Using rxvt gives me nothing better... The problem is as far as I can understand dejagnu configure not finding tclsh... But then, how come that cygwin's dejagnu package works? Any thoughts on how to get dejagnu-1.4.x going under cygwin? Cheers, /ChJ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/