as GIF implementation. They are src/binary compatible and mutually
exclusive, so this is a global choice.
Up to now, "libungif" is used by pkgs, due to patent problems. The
patents are said to be expired, and "giflib" gets somewhat better
maintainance upstream these days, so set the new default to "giflib".
Solaris 11 Express, too).
Changes 4.4.5:
The GNU project and the GCC developers are pleased to announce the
release of GCC 4.4.5.
This release is a bug-fix release, containing fixes for regressions in
GCC 4.4.4 relative to previous releases of GCC.
default in mk/defaults/mk.conf
remove the non-shared defaults and put in the setting that actually gets
used by more than one package (namely, MAJORDOMO_HOMEDIR)
don't make the majordom user own more than it actually needs to
make resend, archive, request-answer and medit honor the MAJORDOMO_CF
environment variable over the command line option, so that someone calling
these via the wrapper (which sets the environment variable) can't make
the majordom user execute random perl code by specifying it as config file.
Thanks to salo for finding this issue.
The problem is Darwin's libiconv does not have symbols for libiconv_<name>
(e.g. libiconv_open), but iconv_<name> (e.g. iconv_open).
BUT when there's pkgsrc/converters/libiconv installed instead, it doesn't
have symbols for iconv_<name>, but libiconv_<name>.
Some packages auto-configure looks for libiconv_open (like glib2), others
look for iconv_open (like proftpd), and there's a conflict.
The solution is to replace libiconv_open with iconv_open with SUBST framework.
Welcome to the modern world of computing.
This is known to break DragonFly at least,
either port g95 or fix lang/gcc44 to work on NetBSD.
Unless there're packages that still think that Fortran is F77,
this shouldn't affect anything.
outdated X libraries? Default to modular x11 for a more modern set of
features, bugfixes (and bugs), and to simplify application support
Does *not* affect 10.5 (Leopard) or later
require a libjpeg implementation. jpeg.buildlink3.mk will:
* set JPEGBASE to the base directory of the libjpeg files;
* set JPEG_TYPE to the libjpeg implementation used.
There are three variables that can be used to tweak the selection of
the libjpeg implementation:
JPEG_DEFAULT is a user-settable variable whose value is the default
libjpeg implementation to use.
JPEG_ACCEPTED is a package-settable list of libjpeg implementations
that may be used by the package.
This .mk is broadly based on fam.buildlink3.mk,v 1.7, and
currently supports selection between the default "graphics/jpeg"
and the alternative "graphics/libjpeg-turbo".
