Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-Id: <4.3.1.2.20001206103322.020c8370@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 06 Dec 2000 10:39:16 -0500
To: "Avraham H. Fraenkel" <avraham DOT fraenkel AT comMATCH DOT com>,
        cygwin AT sources DOT redhat DOT com
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: flex + bison problem and upgrade to new cygwin version
In-Reply-To: <Pine.GHP.4.10.10012040813380.13818-100000@tcmmh003>
References: <20001102084525 DOT A1037 AT dothill DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 01:26 AM 12/4/2000, Avraham H. Fraenkel wrote:
>Hello,
>   I am using cygwin 1.1.4 for a long time.
>   I tried now to use flex and bison and failed on parsing the files.
>   probebly my problem is 0x15 (^M) problem.
>   (I tried to replace them without any sucssess.)
>   
>   I want to ask:
>   1) Does the last version od flex and bison solve such problem 
>      ( I didn't find in the archive but I rembeber i saw it in the list.)


I'm not sure but you should run the latest regardless.


>   2) If I upgrade to latest do I need to re-compile my .exe ?


Executables dependent on cygwin1.dll don't need to be recompiled until
further notice (the most likely clue to that will be that cygwin1.dll will
change to cygwin2.dll).


>   3) What I have to backup if I want to go back to version 1.1.4?
>      Only the install dir (c:\cygwin)
>      or maybe more (like registry file or some other files)


Nope.  You only need to back up the DLL and, if you're building stuff, the
build environment (basically everything that comes in the cygwin-inst tarball
if you were to pull down a development snapshot).  Still, you can back up
*everything* if you find that easier.



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com