[Bug 234784] graphics/gdk-pixbuf2: Fails to build with PNG option disabled

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234784

--- Comment #17 from John Hein <jcfyecrayz at liamekaens.com> ---
(In reply to Mikhail Teterin from comment #16)
A little late on this reply, but no, I did not have gdk-pixbuf2 already
installed when I did the PREFIX=/opt build (comment 15).  But it's possible
(that was a while ago) that it was with the PNG option enabled.

Certainly when I try building today (time has moved on and the version of
gdk-pixbuf2 is now 2.40.0 vs 2.36.12 for the OP's reported issue), it
consistently fails if PNG is off and consistently builds if PNG is on.  This is
with concurrent building enabled or not (on a 4 cpu system).  Other things have
changed since Jan 2019 (meson, ninja) as well.

I think the OP's problem is a mystery and need not be pursued.  Basically, he
had PNG on, libpng was installed and detected, but for some silent reason,
pixbufloader-png.so was just never built.  That triggers the later problems in
the build.

Since we don't have enough information to solve the OP problem, we could just
close this bug.  Except that there seems to be a real problem _now_ when PNG is
disabled (-Dpng=false passed to meson).

I think any talk of parallel builds causing problems is just unverified
guessing that _maybe_ was a possible problem in the 2019 version of everything.
 Let's assume it's not a problem now.

The only problem that still remains as far as I can see is that the build fails
with default options except PNG off.  And it fails in a test because
pixbufloader-png.so was never built.  This seems to be an upstream issue - and
the probable fix is: whatever test is failing should  be modified or disabled
if configured via meson with -Dpng=false.

Possible courses of action:

 - remove PNG option and require libpng it unconditionally

 - submit problem upstream and see if they can reproduce/fix

 - 

 - just punt and close the bug WONT

-- 
You are receiving this mail because:
You are the assignee for the bug.