Fri Dec 31 13:28:00 GMT 1999
On Sun, Dec 05, 1999 at 11:21:18AM -0500, N8TM@aol.com wrote:
>In a message dated 12/5/99 7:59:52 AM Pacific Standard Time, firstname.lastname@example.org
>> 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.
Want to unsubscribe from this list?
Send a message to email@example.com
More information about the Cygwin