My two tests consist of either using your binaries or compiling from
source with my own mangled version.  Basically I'm using the whole thing
as a learning experience.  Should have picked a smaller project to learn
on :P

BTW, I added the #define UNIX stuff to my unixconf.h file and I still
get that stricmp problem during linking, so I'm back to my original fix
until I figure out what's going on.

Mark Gordon wrote:
> 
> Carl Bartels wrote:
> >
> > Actually, I was using my own compile at the time (under Linux).  I get
<snip  stuff about chess2.pov looping/crashing>
> > images still worked.)
> 
> My version also hangs on chess2.pov, just to clarify.  I've had this
> same experience.  Carl, are you using my binaries or compiling from
> source?
> 
> -Mark Gordon

-- 
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

Carl Bartels wrote:
> 
> My two tests consist of either using your binaries or compiling from
> source with my own mangled version.  Basically I'm using the whole thing
> as a learning experience.  Should have picked a smaller project to learn
> on :P

There's a suggested fix out there I mean to try out tonight...
 
> BTW, I added the #define UNIX stuff to my unixconf.h file and I still
> get that stricmp problem during linking, so I'm back to my original fix
> until I figure out what's going on.

Weird.  Was this before or after you independently discovered that you
need to #include "frame.h"?

-Mark Gordon

Post a reply to this message

Mark Gordon wrote:
> 
> Carl Bartels wrote:
> >
<snip>
> 
> > BTW, I added the #define UNIX stuff to my unixconf.h file and I still
> > get that stricmp problem during linking, so I'm back to my original fix
> > until I figure out what's going on.
> 
> Weird.  Was this before or after you independently discovered that you
> need to #include "frame.h"?

This was before.  I gotta stop posting in different places.  It get's
confusing.

As for the single binary idea I  mentioned in the povray.unix group,
there was one point in a readme for the source where it suggested doing
make newunix ; make xwin ; make svga  to get all the binaries.  I don't 
know if that was just with 3.02 or something more recent though.  This
has be noticed before, but I guess it was pretty low priority since it's
easy to work around it.

Another reason I wanted just one binary was because all three takes up
space.  But then, I only ever use x-povray so I guess it doesn't really
matter much.

-- 
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