From: N8TM@aol.com
To: jvalen@rdc.cl, cygwin@sourceware.cygnus.com
Subject: Re: yywrap problems
Date: Fri, 31 Dec 1999 13:28:00 -0000 [thread overview]
Message-ID: <0.4a573f9.257beafe@aol.com> (raw)
Message-ID: <19991231132800.p8c0BrcYyANTODVZ1COD7SuU1DOc6gAZBSj5q2qg2ac@z> (raw)
In a message dated 12/5/99 7:59:52 AM Pacific Standard Time, jvalen@rdc.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.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-12-31 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-05 8:22 N8TM [this message]
1999-12-05 9:55 ` Chris Faylor
1999-12-31 13:28 ` Chris Faylor
1999-12-31 13:28 ` N8TM
-- strict thread matches above, loose matches on Subject: below --
1999-12-05 7:57 Jorge Valenzuela
1999-12-31 13:28 ` Jorge Valenzuela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0.4a573f9.257beafe@aol.com \
--to=n8tm@aol.com \
--cc=cygwin@sourceware.cygnus.com \
--cc=jvalen@rdc.cl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).