Am 09.07.2012 21:56, schrieb Le_Forgeron:

> Indeed, the portability note on
>   http://www.libpng.org/pub/png/libpng.html
> does state that png_struct & png_info are now private.
>
> png_structp  (as type: png_struct * , p for pointer) is actually used in
> source/base/image/png.cpp, and same goes for png_infop .
> That might not help :->

Obviously if that was the issue, it would cause problems not during 
linkage but during compilation.

In fact, png_struct and png_info are still declared in the headers - 
they're just not defined any more; so pointers to them can still be 
passed around without problem, and have to be.

The breaking API changes in 1.5 - as far as they're officually 
documented - have already been taken care of even before the fact, when 
making POV-Ray ready for 1.4 of libpng.


The linker gags on something called "png_set_longjmp_fn" - an identifier 
that is nowhere in the POV-Ray code, so it must have found its way into 
the object code via libpng headers; this means that the headers used by 
the compiler don't match what the linker tries to link against - either 
because the libpng team have goofed it, or because the compiler and 
linker have different ideas about which libpng version to use.

Post a reply to this message

On 07/09/2012 07:01 PM, clipka wrote:
> Am 09.07.2012 20:31, schrieb Chaanakya:
>> Hey guys!  Quick question.
>>
>> Currently, I have POV-Ray 3.6 installed and working.  I am trying to
>> get POV-Ray
>> 3.7 working (mainly for the multithreading).  ./configure works fine
>> (exits with
>> no errors).  However, make throws several errors, the most severe of
>> which is:
>>
>> ...../source/base/libbase.a(png.o): In function `ReadPNGUpdateInfo':
>> png.cpp:(.text+0x36b): undefined reference to `png_set_longjmp_fn'
>> ...../source/base/libbase.a(png.o): In function `ReadPNGImage':
>> png.cpp:(.text+0x3bb): undefined reference to `png_set_longjmp_fn'
>> ...../source/base/libbase.a(png.o): In function
>> `pov_base::Png::Write(pov_base::OStream*, pov_base::Image const*,
>> pov_base::Image::WriteOptions const&)':
>> png.cpp:(.text+0x21a5): undefined reference to `png_set_longjmp_fn'
>> png.cpp:(.text+0x2c5b): undefined reference to `png_set_longjmp_fn'
>> collect2: error: ld returned 1 exit status
>> make[2]: *** [povray] Error 1
>> make[1]: *** [all-recursive] Error 1
>> make: *** [all] Error 2
>>
>> I googled the error and did not get much to go from.  Has anyone else
>> encountered this error and if so, how did you fix it?
>
> Do you happen to have multiple versions of libpng installed? Is the
> libpng-dev up to date to match the libpng version?

I have multiple versions installed ... 1.2.49-9.9.1 and 1.4.11-3.9.1 and 
configure has always found 1.4 just fine.

Post a reply to this message

Am 10.07.2012 13:24, schrieb James Holsenback:
> On 07/09/2012 07:01 PM, clipka wrote:
>>
>> Do you happen to have multiple versions of libpng installed? Is the
>> libpng-dev up to date to match the libpng version?
>
> I have multiple versions installed ... 1.2.49-9.9.1 and 1.4.11-3.9.1 and
> configure has always found 1.4 just fine.

That's how it should be. But it might not necessarily be always the 
case, especially with Experimental add-ons for a distro.

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:
> Am 10.07.2012 13:24, schrieb James Holsenback:
> > On 07/09/2012 07:01 PM, clipka wrote:
> >>
> >> Do you happen to have multiple versions of libpng installed? Is the
> >> libpng-dev up to date to match the libpng version?
> >
> > I have multiple versions installed ... 1.2.49-9.9.1 and 1.4.11-3.9.1 and
> > configure has always found 1.4 just fine.
>
> That's how it should be. But it might not necessarily be always the
> case, especially with Experimental add-ons for a distro.

By "Experimental" I mean the Experimental channel available in Debian
(http://wiki.debian.org/DebianExperimental).  libpng is up to version 1.5.11 and
libpng-dev is matching (1.5.11).

- Chaanakya

Post a reply to this message

Am 11.07.2012 17:18, schrieb Chaanakya:
> clipka <ano### [at] anonymousorg> wrote:
>> Am 10.07.2012 13:24, schrieb James Holsenback:
>>> On 07/09/2012 07:01 PM, clipka wrote:
>>>>
>>>> Do you happen to have multiple versions of libpng installed? Is the
>>>> libpng-dev up to date to match the libpng version?
>>>
>>> I have multiple versions installed ... 1.2.49-9.9.1 and 1.4.11-3.9.1 and
>>> configure has always found 1.4 just fine.
>>
>> That's how it should be. But it might not necessarily be always the
>> case, especially with Experimental add-ons for a distro.
>
> By "Experimental" I mean the Experimental channel available in Debian
> (http://wiki.debian.org/DebianExperimental).  libpng is up to version 1.5.11 and
> libpng-dev is matching (1.5.11).

Quote from that web page: "This directory contains packages and tools 
which are still being developed, and are still in the alpha testing 
stage. Users shouldn't be using packages from here, because they can be 
dangerous and harmful even for the most experienced people."

Given this statement, I'm very much inclined to blame the problems on 
the experimental status of the libpng 1.5.11 Debian package, so my 
proposed solution is to run POV-Ray on a Debian stable distribution, 
and/or contact the people responsible for the libpng 1.5.11 Debian 
package for support (and/or to inform them that they /may/ have a 
problem there).

(That said, I guess I'll have a look at Debian experimental myself; no 
promise though.)

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:
> Am 11.07.2012 17:18, schrieb Chaanakya:
> > clipka <ano### [at] anonymousorg> wrote:
> >> Am 10.07.2012 13:24, schrieb James Holsenback:
> >>> On 07/09/2012 07:01 PM, clipka wrote:
> >>>>
> >>>> Do you happen to have multiple versions of libpng installed? Is the
> >>>> libpng-dev up to date to match the libpng version?
> >>>
> >>> I have multiple versions installed ... 1.2.49-9.9.1 and 1.4.11-3.9.1 and
> >>> configure has always found 1.4 just fine.
> >>
> >> That's how it should be. But it might not necessarily be always the
> >> case, especially with Experimental add-ons for a distro.
> >
> > By "Experimental" I mean the Experimental channel available in Debian
> > (http://wiki.debian.org/DebianExperimental).  libpng is up to version 1.5.11 and
> > libpng-dev is matching (1.5.11).
>
> Quote from that web page: "This directory contains packages and tools
> which are still being developed, and are still in the alpha testing
> stage. Users shouldn't be using packages from here, because they can be
> dangerous and harmful even for the most experienced people."
>
> Given this statement, I'm very much inclined to blame the problems on
> the experimental status of the libpng 1.5.11 Debian package, so my
> proposed solution is to run POV-Ray on a Debian stable distribution,
> and/or contact the people responsible for the libpng 1.5.11 Debian
> package for support (and/or to inform them that they /may/ have a
> problem there).
>
> (That said, I guess I'll have a look at Debian experimental myself; no
> promise though.)

I will see what happens if I install both libpng and libpng-dev from unstable
(as you suggest, it may just be a packaging problem on their end).

- Chaanakya

Post a reply to this message

"Chaanakya" <nomail@nomail> wrote:
> clipka <ano### [at] anonymousorg> wrote:
> > Am 11.07.2012 17:18, schrieb Chaanakya:
> > > clipka <ano### [at] anonymousorg> wrote:
> > >> Am 10.07.2012 13:24, schrieb James Holsenback:
> > >>> On 07/09/2012 07:01 PM, clipka wrote:
> > >>>>
> > >>>> Do you happen to have multiple versions of libpng installed? Is the
> > >>>> libpng-dev up to date to match the libpng version?
> > >>>
> > >>> I have multiple versions installed ... 1.2.49-9.9.1 and 1.4.11-3.9.1 and
> > >>> configure has always found 1.4 just fine.
> > >>
> > >> That's how it should be. But it might not necessarily be always the
> > >> case, especially with Experimental add-ons for a distro.
> > >
> > > By "Experimental" I mean the Experimental channel available in Debian
> > > (http://wiki.debian.org/DebianExperimental).  libpng is up to version 1.5.11 and
> > > libpng-dev is matching (1.5.11).
> >
> > Quote from that web page: "This directory contains packages and tools
> > which are still being developed, and are still in the alpha testing
> > stage. Users shouldn't be using packages from here, because they can be
> > dangerous and harmful even for the most experienced people."
> >
> > Given this statement, I'm very much inclined to blame the problems on
> > the experimental status of the libpng 1.5.11 Debian package, so my
> > proposed solution is to run POV-Ray on a Debian stable distribution,
> > and/or contact the people responsible for the libpng 1.5.11 Debian
> > package for support (and/or to inform them that they /may/ have a
> > problem there).
> >
> > (That said, I guess I'll have a look at Debian experimental myself; no
> > promise though.)
>
> I will see what happens if I install both libpng and libpng-dev from unstable
> (as you suggest, it may just be a packaging problem on their end).
>
> - Chaanakya

I found out that I have more serious problems (parts of boost are missing) - I
will rectify those and report back.  Reverting to libpng12 got rid of the libpng
error.

- Chaanakya

Post a reply to this message

"Chaanakya" <nomail@nomail> wrote:
> "Chaanakya" <nomail@nomail> wrote:
> > clipka <ano### [at] anonymousorg> wrote:
> > > Am 11.07.2012 17:18, schrieb Chaanakya:
> > > > clipka <ano### [at] anonymousorg> wrote:
> > > >> Am 10.07.2012 13:24, schrieb James Holsenback:
> > > >>> On 07/09/2012 07:01 PM, clipka wrote:
> > > >>>>
> > > >>>> Do you happen to have multiple versions of libpng installed? Is the
> > > >>>> libpng-dev up to date to match the libpng version?
> > > >>>
> > > >>> I have multiple versions installed ... 1.2.49-9.9.1 and 1.4.11-3.9.1 and
> > > >>> configure has always found 1.4 just fine.
> > > >>
> > > >> That's how it should be. But it might not necessarily be always the
> > > >> case, especially with Experimental add-ons for a distro.
> > > >
> > > > By "Experimental" I mean the Experimental channel available in Debian
> > > > (http://wiki.debian.org/DebianExperimental).  libpng is up to version 1.5.11
and
> > > > libpng-dev is matching (1.5.11).
> > >
> > > Quote from that web page: "This directory contains packages and tools
> > > which are still being developed, and are still in the alpha testing
> > > stage. Users shouldn't be using packages from here, because they can be
> > > dangerous and harmful even for the most experienced people."
> > >
> > > Given this statement, I'm very much inclined to blame the problems on
> > > the experimental status of the libpng 1.5.11 Debian package, so my
> > > proposed solution is to run POV-Ray on a Debian stable distribution,
> > > and/or contact the people responsible for the libpng 1.5.11 Debian
> > > package for support (and/or to inform them that they /may/ have a
> > > problem there).
> > >
> > > (That said, I guess I'll have a look at Debian experimental myself; no
> > > promise though.)
> >
> > I will see what happens if I install both libpng and libpng-dev from unstable
> > (as you suggest, it may just be a packaging problem on their end).
> >
> > - Chaanakya
>
> I found out that I have more serious problems (parts of boost are missing) - I
> will rectify those and report back.  Reverting to libpng12 got rid of the libpng
> error.
>
> - Chaanakya

This issue has now been rectified.  I reverted to libpng12 and installed the
missing boost libraries.  POV-Ray then compiled fine.  As an aside, does anyone
know how to change the number of render threads?

- Chaanakya

Post a reply to this message

Le 12/07/2012 17:40, Chaanakya nous fit lire :

> This issue has now been rectified.  I reverted to libpng12 and installed the
> missing boost libraries.  POV-Ray then compiled fine.  As an aside, does anyone
> know how to change the number of render threads?

Yes.



ok, the option is -WT<number>

and it should be in the wiki-doc, I hope so.

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> Le 12/07/2012 17:40, Chaanakya nous fit lire :
>
> > This issue has now been rectified.  I reverted to libpng12 and installed the
> > missing boost libraries.  POV-Ray then compiled fine.  As an aside, does anyone
> > know how to change the number of render threads?
>
> Yes.
>
>
>
> ok, the option is -WT<number>
>
> and it should be in the wiki-doc, I hope so.

Thanks - the manpage hasn't been updated, but I checked the docs.  Also, it
should be +WT (I think...that's what the docs said IIRC).  Anyway, this issue is
closed.  Thank you everyone for helping me with this problem!

- Chaanakya

Post a reply to this message