Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Date: Mon, 12 Jul 1999 17:43:33 +0100 X-Mailer: emacs 20.3.10.1 (via feedmail 9-beta-7 I); VM 6.72 under Emacs 20.3.10.1 From: David Starks-Browning MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14218.6965.398000.973453@bryce.ebi.ac.uk> To: cygwin AT sourceware DOT cygnus DOT com CC: bash-maintainers AT prep DOT ai DOT mit DOT edu Subject: building bash-2.03? Greetings, This is cygwin B20.1 with 1999-01-15 snapshot of cygwin1.dll, on NT4/SP5. Trying to build bash-2.03 (release). Background: Now that I am trying to get "real work done" in bash under cygwin, I can no longer tolerate that bash cannot read its .bash_history file. (I have, and wish to keep, text != binary mounts under cygwin.) I thought I could apply Mark Levedahl's patch (Ref: ) to bash-2.03. I thought I had read elsewhere that bash builds out-of-the-box on cygwin, but I got almost nowhere: > ./configure > ----------- > creating cache ./config.cache > configure: error: can not run ./support/config.sub Has anyone else built bash-2.03 successfuly for cygwin? Is there something special I need to do, or should I start looking for problems in my cygwin setup? (I've built other gnu software in the past without difficulty.) Thanks for your help. Regards, David ------------------------------------------------------------------- David Starks-Browning | starksb AT ebi DOT ac DOT uk EMBL Outstation -- | The European Bioinformatics Institute | Wellcome Trust Genome Campus | tel: +44 (1223) 494 616 Hinxton, Cambridge, CB10 1SD, UK | fax: +44 (1223) 494 468 ------------------------------------------------------------------- -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com