Hello,

  I've mannaged to get megapov going nicely under Linux, but had to mess
with the uniutils.c file to make it compile.  Could anyone tell me if
what I did will break something?  (I kept getting a compile error at the
end complaining about an undefined reference to stricmp in function
uniGetEncodingByName)

  In the area around line 40 of uniutils.c I commented out most of the
#ifdef stuff
except the one line to "#define STRICMP strcasecmp" which is the unix
choice (force it to make the unix choice.)

  This change finally allowed everything to compile, but is it likely to
break the
unicode stuff?

-- 
Carl Bartels, Department of Chemsitry, Mcgill University, to reply to
me,
just kill a and 5 from the email name, Montreal, QC, cAnAdA

Post a reply to this message

What compiler did you use? How did you avoid the problems with the
//-comments and a couple of undefined variables named 'false'?

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Carl Bartels wrote:
> 
> Hello,
> 
>   I've mannaged to get megapov going nicely under Linux, but had to mess
> with the uniutils.c file to make it compile.  Could anyone tell me if
> what I did will break something?  (I kept getting a compile error at the
> end complaining about an undefined reference to stricmp in function
> uniGetEncodingByName)

I had problems with that too, initially.  It turns out UNIX wasn't
defined (YS must have thought it was), so I #defined UNIX in config.h,
which is a platform-specific file.  I got it to compile though; I'm not
sure why you had problems.  BTW, the default compile is going to whine
like nobody's business.  I turned on all the warnings in the compiler
flags in the makefile, and there's a lot of stuff to be warned about.
;-)
 
>   In the area around line 40 of uniutils.c I commented out most of the
> #ifdef stuff
> except the one line to "#define STRICMP strcasecmp" which is the unix
> choice (force it to make the unix choice.)
> 
>   This change finally allowed everything to compile, but is it likely to
> break the
> unicode stuff?

No, that code is just there for portability.  You may have to repeat
your change if the code is updated, and since I'm not sure why you had
this problem (or why your fix made it any different), I'm not sure how
to change it on my end.

Let me know if you find out anything else.

-Mark Gordon

Post a reply to this message

Nieminen Juha wrote:
> 
>   What compiler did you use? How did you avoid the problems with the
> //-comments and a couple of undefined variables named 'false'?
> 
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

I used gcc, more or less (egcs-2.91.66). I replaced the //... with
/*...*/ and replaced "false" with "FALSE".

-Mark Gordon

Post a reply to this message

I used gcc (whichever one came with slackware 7.0 ... not the computer
I'm on right now, so I can't check what version very easily.

"//" style comments were weaded out by hand.  I then had to put some
back in because it complained about /*'s withint comments and I didn't
want to hunt down a compiler flag to ignore this.

I blindly converted the "false" variables to "FALSE".

BTW, the makefile I used was a modified version of the official one that
came with 3.1g.  To get the extra stuff, I recommend "gcc -MM -MG >
dependancies" which you can then modify and splice into the makefile
with emacs.  That's probably the biggest part of fixing up the
makefile.  My programming's not that good though, so I'd recommend Mark
Gordon's version over my own.

Nieminen Juha wrote:
> 
>   What compiler did you use? How did you avoid the problems with the
> //-comments and a couple of undefined variables named 'false'?
> 
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

-- 
Carl Bartels, Department of Chemsitry, Mcgill University, to reply to
me,
just kill a and 5 from the email name, Montreal, QC, cAnAdA

Post a reply to this message

Nieminen Juha wrote:

>   What compiler did you use? How did you avoid the problems with the
> //-comments and a couple of undefined variables named 'false'?
>

Sorry. My fault.

I did that initial work back when I was a Windows programmer. Just after
that I switched to Linux at home and started getting things cleaned up
(Other stuff at work, but I did all POV-Ray hacking at home). First thing
was to get it all happy with gcc, so as soon as I update that stuff, it will
be happy. RSN.

BTW,

--
"My new computer's got the clocks, it rocks
But it was obsolete before I opened the box" - W.A.Y.

Post a reply to this message