Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3136A952E020D211882000805FE687B1029CAB77@nssmx2.cpd.harris.com> From: "Killion, Richard" To: "'cygwin AT sourceware DOT cygnus DOT com'" Subject: Re: STATUS ACCESS VIOLATION - Transferring Flex & Bison to anothe r machine - Advice needed Date: Thu, 20 Jul 2000 11:25:47 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" --- In gnu-win32 AT egroups DOT com, "Paul Garceau" wrote: > forgive me, please --- but I need to ask: Why not simply > update your Cygwin development environment to the latest Cygwin > release (1.1.2)? Paul: Thank you for your reply. The statement probably was hard to find in my lengthy and wordy message, but "I installed the latest flex and bison , but still get errors. " After Bison failing in the same way with the latest (1.1.2), I backtracked to the other engineers b19 setup which was working fine on his machine but not mine. I found what I was missing. I needed a "tmp" file in the root. This is what bombed Bison. The dos "temp" wasn't enough. I am surprised that the 1.1.2 version did not install "tmp". Now that it is fixed, I will work with 1.1.2 with confidence. Thanks again for your reply. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com