delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f |
Message-ID: | <46AC33E7.1090909@iki.fi> |
Date: | Sun, 29 Jul 2007 09:29:59 +0300 |
From: | Andris Pavenis <andris DOT pavenis AT iki DOT fi> |
User-Agent: | Thunderbird 2.0.0.5 (X11/20070719) |
MIME-Version: | 1.0 |
To: | djgpp AT delorie DOT com |
Subject: | Re: "configure" script fails catastrophically |
References: | <1185666705 DOT 728871 DOT 33770 AT z24g2000prh DOT googlegroups DOT com> |
In-Reply-To: | <1185666705.728871.33770@z24g2000prh.googlegroups.com> |
X--MailScanner-Information: | Please contact the ISP for more information |
X--MailScanner: | Found to be clean |
X--MailScanner-From: | andris DOT pavenis AT iki DOT fi |
X-Spam-Status: | No |
Reply-To: | djgpp AT delorie DOT com |
mike3 wrote: > Hi. > > I was trying to run the "configure" script for GMP (GNU MP Bignum > Package) on DJGPP with "bash", and this happened: > > bash-2.04$ ./configure > configure: loading site script c:/djgpp/share/config.site > configure: loading cache /dev/null > /configure: .: /dev/null: not a regular file > checking build system type... pentium4-pc-msdosdjgpp > checking host system type... pentium4-pc-msdosdjgpp > checking for a BSD-compatible install... /dev/env/DJDIR/bin/ > ginstall.exe -c > checking whether build environment is sane... yes > checking for gawk... no > checking for mawk... no > checking for nawk... no > checking for awk... no > checking whether make sets $(MAKE)... > C:\unzipped\gmp-4.2.1> > > Bam -- right there it goes back to the DOS prompt. Not to the bash > prompt but bash completely crashes somehow (without giving me any sort > of error message) and goes back to the DOS prompt. What is wrong here? > > PS. I'm using Windows 2000 as the main operating system. Run it yesterday for both DJGPP v2.03 and and DJGPP v2.04 and there were no problems building GMP-4.2.1 and MPFR-2.2.1. You perhaps have some too old DJGPP binary packages installed built using DJGPP version 2.03r2. You may try inserting line 'set -x' in configure script and to look where it crashes, to get some hint which package to upgrade.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |