* yywrap problems
@ 1999-12-05 7:57 Jorge Valenzuela
1999-12-31 13:28 ` Jorge Valenzuela
0 siblings, 1 reply; 6+ messages in thread
From: Jorge Valenzuela @ 1999-12-05 7:57 UTC (permalink / raw)
To: cygwin
Hello:
I am compiling a c app. in dos Windows with cygwin but I have the follow
message:
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
lex.yy.o(.text+0xf0c):lex.yy.c: undefined reference to `yywrap'
lex.yy.o(.text+0x17a1):lex.yy.c: undefined reference to `yywrap'
collect2: ld returned 1 exit status
MAKE.EXE: *** [advent.exe] Error 1
What is the problem ?
What setting must I chechk to include the flex library ?
thanks in advance
Jorge
V.S.'991205
--
//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\
\\// Jorge Valenzuela S.; Santiago, Chile.
<|>. \\// e-mail > jvalen@mailnet.rdc.cl
/| |X| \\//
\\//
//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* yywrap problems
1999-12-05 7:57 yywrap problems Jorge Valenzuela
@ 1999-12-31 13:28 ` Jorge Valenzuela
0 siblings, 0 replies; 6+ messages in thread
From: Jorge Valenzuela @ 1999-12-31 13:28 UTC (permalink / raw)
To: cygwin
Hello:
I am compiling a c app. in dos Windows with cygwin but I have the follow
message:
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
lex.yy.o(.text+0xf0c):lex.yy.c: undefined reference to `yywrap'
lex.yy.o(.text+0x17a1):lex.yy.c: undefined reference to `yywrap'
collect2: ld returned 1 exit status
MAKE.EXE: *** [advent.exe] Error 1
What is the problem ?
What setting must I chechk to include the flex library ?
thanks in advance
Jorge
V.S.'991205
--
//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\
\\// Jorge Valenzuela S.; Santiago, Chile.
<|>. \\// e-mail > jvalen@mailnet.rdc.cl
/| |X| \\//
\\//
//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: yywrap problems
1999-12-05 8:22 N8TM
1999-12-05 9:55 ` Chris Faylor
@ 1999-12-31 13:28 ` N8TM
1 sibling, 0 replies; 6+ messages in thread
From: N8TM @ 1999-12-31 13:28 UTC (permalink / raw)
To: jvalen, cygwin
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: yywrap problems
1999-12-05 9:55 ` Chris Faylor
@ 1999-12-31 13:28 ` Chris Faylor
0 siblings, 0 replies; 6+ messages in thread
From: Chris Faylor @ 1999-12-31 13:28 UTC (permalink / raw)
To: N8TM; +Cc: jvalen, cygwin
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, 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.
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@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: yywrap problems
1999-12-05 8:22 N8TM
@ 1999-12-05 9:55 ` Chris Faylor
1999-12-31 13:28 ` Chris Faylor
1999-12-31 13:28 ` N8TM
1 sibling, 1 reply; 6+ messages in thread
From: Chris Faylor @ 1999-12-05 9:55 UTC (permalink / raw)
To: N8TM; +Cc: jvalen, cygwin
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, 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.
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@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: yywrap problems
@ 1999-12-05 8:22 N8TM
1999-12-05 9:55 ` Chris Faylor
1999-12-31 13:28 ` N8TM
0 siblings, 2 replies; 6+ messages in thread
From: N8TM @ 1999-12-05 8:22 UTC (permalink / raw)
To: jvalen, cygwin
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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~1999-12-31 13:28 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-12-05 7:57 yywrap problems Jorge Valenzuela
1999-12-31 13:28 ` Jorge Valenzuela
1999-12-05 8:22 N8TM
1999-12-05 9:55 ` Chris Faylor
1999-12-31 13:28 ` Chris Faylor
1999-12-31 13:28 ` N8TM
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).