fpc doesn't seem to respect the -v,X> flags for me.

I'm compiling a shared object library (on an Ubuntu Linux 64-bit platform cross-compiling to 32-bit) and I've tried -ve, -vew, -v0, but I still get hints.

Anyone else experience this?

-SG

Sorry, not sure what happened on the first line of that email, I meant the -v flag described in the fpc help as " -v<x> Be verbose. <x> is a combination of the following letters:.."

-SG

Seth Grover wrote

I'm compiling a shared object library (on an Ubuntu Linux 64-bit platform cross-compiling to 32-bit) and I've tried -ve, -vew, -v0, but I still get hints.

Maybe the source code contains {$hints on}

Jonas

Maybe the source code contains {$hints on} Jonas

Ah, why didn't I think of that. I had a function and I was doing something like:

{$HINTS OFF}
my function here
{$HINTS ON}

but in my mind for some reason I was thinking this would mean "turn hints back on only if they were on before." Of course that's not right.

Thanks, it's working great now.

-SG