James Holsenback <nom### [at] nonecom> wrote:
> Yep ... I'm getting similar message from my fresh new opesuse12.1 install.
>
> JPEG parameter struct mismatch: library thinks size is 372, caller
> expects 376
> JPEG parameter struct mismatch: library thinks size is 372, caller
> expects 376
>
> Notice the different size(s) in my message. Your follow up indicated
> that you installed 8d ... I'm surprised that you didn't have a libtif
> conflict. I did some investigation and found that (via the software
> manager) as I was making sure all the build environment stuff was
> installed I decided to give jpegv8 a try (I knew better but was curious)
> it uninstalled my libtif! Hey didn't want to break dependencies, and
> didn't realize my foo until configure complained. Sooo ... I'd say
> jpegv8 is definitively out, and the povray build README says it ain't a
> happening thing. Once I got the v8 stuff removed and the v62 stuff back
> (and libtif) ... I'm still having problems writing jpg output. The
> version that the repositories (12.1) have MUST be wrong!

I spent a lot of time trying to decide between openSUSE and Ubuntu.  It just
occurred to me that since Mark Shuttleworth is a POV-Ray fan, Ubuntu might have
worked more smoothly.

> I think there
> must be older versions of libjpeg out there, but since I'm more apt to
> write png, I'm willing to live with it, and keep OTHER things from being
> busted ;-)

I'm with you there.  Before 3.7 there was the GIMP.

> On a similar note ... I also had a problem /reading/ png files until
> installed libpng14-compat-devel the synopsis recommended the package for
> programs that don't care about certain header (.h file) information. I
> guess this was necessary because the 12.1 repositories version got
> bumped up a notch from the last time I did a build.

I just used a PNG image map with no problem, but it had only 2 pixel values, <0,
0, 0> and <1, 1, 1>, so there wasn't much opportunity to blunder into any bugs.

*nix ASSumes that the user knows what he's doing.  Micro$haft ASSumes that the
user doesn't know what he's doing.  Isn't there a middle ground somewhere?  Of
course, what with the safety and the interception and all the butterfingers, I'm
not in the best mood right now.

Post a reply to this message