X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Trace-PostClient-IP: 68.147.131.211 From: Brian Inglis Newsgroups: comp.os.msdos.djgpp Subject: Re: Subject: [GNU Bison 1.875] testsuite: 5 8 12 13 20 24 25 27 33 41 45 46 47 69 73 75 76 89 93 99 100 101 102 103 failed Organization: Systematic Software Message-ID: References: <1099444656 DOT 418831b0c0b87 AT webmail DOT wilkes DOT edu> X-Newsreader: Forte Agent 1.93/32.576 English (American) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 43 Date: Wed, 03 Nov 2004 02:58:57 GMT NNTP-Posting-Host: 24.71.223.147 X-Complaints-To: abuse AT shaw DOT ca X-Trace: pd7tw3no 1099450737 24.71.223.147 (Tue, 02 Nov 2004 19:58:57 MST) NNTP-Posting-Date: Tue, 02 Nov 2004 19:58:57 MST To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com On Tue, 2 Nov 2004 20:17:36 -0500 in comp.os.msdos.djgpp, fdonahoe AT wilkes DOT edu wrote: >Quoting Paul Eggert : > >> .... >> For this sort of thing I suggest using the latest Bison CVS, or if >> that's too much trouble, the latest Bison test snapshot. >> >> http://savannah.gnu.org/projects/bison >> ftp://alpha.gnu.org/gnu/bison/bison-1.875d.tar.gz >> >Going to the Bison CVS without a native guide is too much a >challenge. I have downloaded the bison tar ball and extracted >the files. I was able to add the patches Juan Manuel Guerrero >found for the v 1.875 release. However the configure script >failed after creating "config.status." > >cd . && C:/djg/bin/sh.exe ./config.status config.h >/config.status: line 731: syntax error near unexpected token `newline' >/config.status: line 731: `abs_builddir='../../.'' > >This is very much like the error encountered with the linked >files in the gmp package but I have found no way around it. > >Importing and patching the Makefile from the v 1.875 release >did not solve the problem. The makefile reads config.status >too and encountered the same syntax error. The "newline" token suggests your files/patchfiles may have DOS crlf line terminators instead of Unix newline terminators. Your un-zip/tar program may also have an option for line terminator conversion which can be fatal for files used by some utilities. Try stripping the patch file using crlf, dtou, or your favourite editing program, then reapplying. If that still fails, then try unzipping the tarball ensuring no line terminator conversion. -- Thanks. Take care, Brian Inglis Calgary, Alberta, Canada Brian DOT Inglis AT CSi DOT com (Brian[dot]Inglis{at}SystematicSW[dot]ab[dot]ca) fake address use address above to reply