Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Sun, 5 Dec 1999 12:54:52 -0500 To: N8TM AT aol DOT com Cc: jvalen AT rdc DOT cl, cygwin AT sourceware DOT cygnus DOT com Subject: Re: yywrap problems Message-ID: <19991205125452.B826@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: N8TM AT aol DOT com, jvalen AT rdc DOT cl, cygwin AT sourceware DOT cygnus DOT com References: <0 DOT 4a573f9 DOT 257beafe AT aol DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <0.4a573f9.257beafe@aol.com>; from N8TM@aol.com on Sun, Dec 05, 1999 at 11:21:18AM -0500 On Sun, Dec 05, 1999 at 11:21:18AM -0500, N8TM AT aol DOT com wrote: >In a message dated 12/5/99 7:59:52 AM Pacific Standard Time, jvalen AT rdc DOT cl >writes: >> gcc -Iy:\include,y:\H-i586-cygwin32\i586-cygwin32\include y.tab.o >> lex.yy.o adventM.o actionsM.o particM.o -Lfl -o advent > >Does this work the same as > >gcc -L//y/include -L//y/H-i586-cygwin32/i586-cygwin32/include \ > lex.yy.o adventM.o actionsM.o particM.o -lfl -o advent > >? > >Yes, -lfl should take care of linking libfl. I'm confused about how >many DOSish variations cygwin may permit; I like to stick with trying >to learn what should work both in cygwin and linux. It's not a question of cygwin permitting things. The issue is whether the individual application attempts to parse UNIX paths. If it does, then it will invariably be confused by x:\foo paths. There is really no reason to be confused. Don't use the DOS paths and you should have very few problems. That's why we invented Cygwin. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com