On 2002-03-12 07:52 -0800, Ricardo Rugerio wrote:
> this trouble isn't with Xmame, is with VDK instead.
Okay. Sorry, for the confusion, I hadn't read closely enough.
> > - look on Sun's site for the appropriate patch and
> > ask your
> > sysadmin to apply it.
>
> what kind of patch do you refer ?
>
> "cc patchs" or something like this?
Basically a file that you download from Sun's site. When you
install it, it fixes a bug in their software. Others call them
"security updates", "PTF"s, "fixes", "service packs", etc.
> > - try another compiler, like GCC.
>
> that is the worst!, I am using gcc version 2.95.2
> :-(
Sorry, I thought you were using Sun's Forte, hence more
confusion.
> > - look in the doc of your compiler for an option to
> > turn these
> > errors into warnings (the equivalent of GCC's
> > -fpermissive).
>
> about this, how can I see the gcc flags?
gcc --help
man gcc
info gcc
> I say is there anything like:
>
> gcc --flags
>
> I put -fpermissive and I didn't get an error, but
> it didn't work, I put in this line:
>
> CFLAGS = -fpermissive -g -O2
> -I/usr/local/include/gtk-1.2
> -I/usr/local/include/glib-1.2
>
> and later in this line
>
> CXXFLAGS = -s -O2 -Wall -Wcast-qual -fpermissive
> -Woverloaded-virtual -Wconversion -Wstrict-pr
> ototypes -Winline
>
> but the errors exists yet.
If gcc barfs even with -fpermissive, it doesn't look good. Did
you try to put extern "C" { } around the offending #include, as
another poster said ?
As a last resort, you can copy the headers in a place where they
will be found before the originals (like ./), and fix the
prototypes in the copies.
--
Andr� Majorel <[EMAIL PROTECTED]>
http://www.teaser.fr/~amajorel/
_______________________________________________
Xmame mailing list
[EMAIL PROTECTED]
http://toybox.twisted.org.uk/mailman/listinfo/xmame
