Compilation troubles

Hi,

I 'm developing a parser. And I have a couple of troubles.
The first is that I can’t compile my c files when I use the math.h
library.
I released that the problem is solved when i change the name of the file
from *.c to cpp


The second, is that I’m using the tools flex and bison to generate a parser.
But I got always the same compilation error.
gcc doesn’t find the path to understand the function ‘yywrap’

What I must to configure in order to solve these matters?
Some idea?

Julián.

“Julián” <jruiz@ieee.org> wrote in message news:3BCDE062.2080407@ieee.org

Hi,

I 'm developing a parser. And I have a couple of troubles.

Try qnd.public.qnxrtp.devtools instead.

“Julián” <jruiz@ieee.org> wrote in message news:3BCDE062.2080407@ieee.org

The second, is that I’m using the tools flex and bison to generate a
parser.
But I got always the same compilation error.
gcc doesn’t find the path to understand the function ‘yywrap’

Link with /usr/local/lib/libfl.a

Marty

yywrap() at it’s most basic will always return 1. This is the function
that is called when the scanner hits EOF. If it returns false then it
assumes a new file has been set up for scanning. You have three options.
Define a function yywrap() which returns 1 (or a macro I suppose). As
Marty said, link with libfl.a (for flex). Or, (the easiest), use
‘%option noyywrap’ in your flex file.

cheers,

Kris

Marty Doane <marty.doane@rapistan.com> wrote:

“Julian” <> jruiz@ieee.org> > wrote in message news:> 3BCDE062.2080407@ieee.org> …
The second, is that I’m using the tools flex and bison to generate a
parser.
But I got always the same compilation error.
gcc doesn’t find the path to understand the function ‘yywrap’

Link with /usr/local/lib/libfl.a

Marty


Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“Computer science is no more about computers than astronomy is about telescopes”
–E.W.Dijkstra

Hello!

When I type

…/mig4nto-procmgr -vv &

from /x86/bin, it gives me an error and terminates saying “unable to attach
name.” Does anyone know why I’m getting that error or how to fix it? I suspect
I’m not running some other essential driver, but I don’t know which one that
might be. I’ve searched through the docs and can’t find anything!

Thanks!

Neville

Something may already be using the name. Perhaps a copy is already running?

“Neville Bonwit” <neville@erg.sri.com> wrote in message
news:3BE6F7EF.F0C2C81E@erg.sri.com

Hello!

When I type

./mig4nto-procmgr -vv &

from /x86/bin, it gives me an error and terminates saying “unable to
attach
name.” Does anyone know why I’m getting that error or how to fix it? I
suspect
I’m not running some other essential driver, but I don’t know which one
that
might be. I’ve searched through the docs and can’t find anything!

Thanks!

Neville