firefox & png
Polytropon
freebsd at edvax.de
Thu Aug 23 16:50:48 UTC 2012
On Thu, 23 Aug 2012 12:26:18 -0400, david coder wrote:
> +++ Jamie Paul Griffin [23/08/12 07:54 +0100]:
> >[ Polytropon wrote on Thu 23.Aug'12 at 2:00:15 +0200 ]
> >
> >> On Wed, 22 Aug 2012 19:43:55 -0400, david coder wrote:
> >> > thx, i hadn't seen the reply to my earlier message.
> >> >
> >> > unfortunately, though i've got the png port installed w/
> >> >
> >> > OPTIONS= APNG "Animated PNG support" On
> >>
> >> That should be the default. Anyway, you can always check which
> >> options had been in use when building and installing a port:
> >>
> >> % cat /var/db/ports/png/options
> >> # This file is auto-generated by 'make config'.
> >> # No user-servicable parts inside!
> >> # Options for png-1.4.8
> >> _OPTIONS_READ=png-1.4.8
> >> WITH_APNG=true
> >>
> >> In this example you can see that it has been properly installed.
> >>
> >>
> >>
> >> > the install of freebsd fails w/ the error message given below.
> >>
> >> Sadly the Firefox build error message is not included.
> >>
> >>
> >>
> >> > is there something else required in the png makefile or elsewhere that i'm
> >> > missing?
> >>
> >> I'm sure this entry of /usr/ports/UPDATING applies:
> >>
> >> 20120531:
> >> AFFECTS: users of graphics/png
> >> AUTHOR: dinoex at FreeBSD.org
> >>
> >> The PNG library has been updated to version 1.5.10. Please rebuild all
> >> ports that depend on it.
> >
> >I built Firefox 14 a couple of days ago and png installed is now version 1.5.12. So an updated ports tree should incorporate that change now shouldn't it.
>
> true, but from what i have been able to sniff out on my own, ports
> configuration data are stored in /usr/local/include, not anywhere in the ports
> tree, so that if png has been installed already & you do a "make showconfig"
> in /usr/ports/graphics/png, the data are read from files in /usr/local/include,
> & if you run "make config" in /usr/ports/graphics/png, the files affected by
> any change are in /usr/local/include, not anywhere in the ports tree.
That's not fully correct. Ports _configuration_ (what you select
with "make configure") is not stored inside the ports tree -- so
far correct. It's _not_ stored in /usr/local/include. Anything
that will go to those directory subtree will be installed there
only by a "make install" step, not by "make configure". The
options set for a port by "make configure" (even if no "make" or
"make install" follows) is /var/db/ports/<name>/options, where
<name> is the name of the port in question. This data will be
queried by "make showconfig". See the example shown above.
make configure -> data into /var/db/ports/<name>/options
make -> data into /usr/ports/<category>/<name>/work/...
make install -> data into /usr/local and its subtrees
The directory /usr/local/include is intended to hold header files
for interfacing with various libraries. It doesn't have anything
to do with ports _configuration_; it's designated content _may_
be affected by how a port is configured (by its own options or
by implicit dependencies and _their_ content).
> this has been a learning experience for me & prolly will continue to be as
> others here correct me.
See "man 7 ports" for an overview of how ports are utilized on
FreeBSD. There's also a chapter in The FreeBSD Handbook dealing
with ports. As soon as you have understood the simple mechanisms
that build the basic parts the ports infrastructure works on,
you will be quickly able to resolve all issues easily.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
More information about the freebsd-questions
mailing list