Age | Commit message (Collapse) | Author | Files | Lines |
|
per report from hubertf that it fixed his kdetoys3 build and nudge from
Sverre Froyen on tech-pkg.
|
|
(There's no randr pkg.)
|
|
Xrender render Xft2 freetype2 Xrandr randr xcursor
to fix lots of build problems on systems where the libraries
coming with X are too old for some packages (but not for others).
Ok'd by recht@ and agc@.
Attention: for this to take effect, you must recompile your packages
that depend on freetype2/Xrender, especially pango.
|
|
|
|
some pickier awks (e.g nawk) refuse the regex otherwise
|
|
--recheck from re-executing the configure script by inserting "exit 0"
judiciously. This works with configure scripts generated by autoconf>=2.13
and fixes problems with running config.status on Solaris systems where
/bin/sh isn't POSIX enough.
|
|
|
|
|
|
|
|
does, so rearrange the arguments so that "-f -" is always at the end.
noted by krister@.
while I'm here, make sure we use the same tar(1) program pkgsrc does.
|
|
|
|
|
|
modifer expression.
|
|
|
|
|
|
|
|
to ccache. This now correctly passes CCACHE_HASHCC to ccache if the
package has a custom do-build target that invokes ${CC} directly.
|
|
BUILD_ENV is used to set the environment for the sub-make processes that
are invoked for each phase after and including buildlink.
|
|
trivial libtool archive.
|
|
configure script under ${WRKSRC}. The symlink is called "libtool.m4",
which is the name expected by the autoconf tools. The symlinking is
only done if ${AUTOCONF_REQD} == 2.13 and USE_LIBTOOL is defined. This
allows autoconf-2.13, autoreconf-2.13 and aclocal-2.13 to use the older
libtool.m4 file when regenerating files. This is okay, because we later
override the generated libtool file anyway.
This fixes problems when libtool-1.5.x is installed and a package tries
to invoke autoconf-2.13 programs at pre-configure time, e.g., gnome-games,
xpuyopuyo, faad2, libwww, etc. These packages no longer need to be
worked around by bumping AUTOCONF_REQD to 2.50.
|
|
|
|
lists, then just assume that we need gcc3. The rest of the code in the
file assumes that we either need gcc2 or gcc3, so this provides a
fall-through, default value.
|
|
http://fink.sourceforge.net/doc/porting/shared.php
It's okay to link against a name like "libqt.2.3.0.dylib" using
"-lqt.2.3.0", which means we never need to do anything more than just
strip the trailing ".dylib" from shared library names when converting from
a full path to "-L... -l...". This should fix PR 24402.
|
|
|
|
${LOCALBASE}. Some packages' configure scripts resolve all paths to
physical paths, and since buildlink3 suppresses references outside of
${LOCALBASE}, it can break the build of those packages.
This should fix the problem noted by Nathan Williams in the thread
titled "x11/tk build failure" at:
http://mail-index.netbsd.org/tech-pkg/2004/02/17/0004.html
|
|
uses {} to list several "or" dependencies.
|
|
cd: cd BUILDLINK_PREFIX.foo_not_found
We now say that the package wasn't installed at the time that we were
trying to buildlink its files.
|
|
|
|
Package Makefiles may now directly include compiler.mk.
* Don't include compiler.mk within bsd.prefs.mk any longer. It was only
included for the purposes of defining CC_VERSION. Packages that want
to test the value of CC_VERSION should now first include
"../../mk/compiler.mk". Any GCC_REQD statements in package Makefiles
should be set before compiler.mk is included.
* Simpllfy pkgsrc/mk/compiler/*.mk files as a result of not needing to
be included indirectly by bsd.prefs.mk. We remove the special handling
associated with detecting whether the file was included from within
bsd.prefs.mk. These files are now much more straightforward to write
and understand.
* G/C the BSD_PREFS_MK stack mechanism as the only users (compiler/*)
no longer need it.
* Ensure that directories are prepended to the PATH only from within
bsd.pkg.mk.
|
|
ucode compilers only support building the "o32" ABI.
|
|
|
|
|
|
|
|
|
|
|
|
foo>=0.3 foo>=0.4" are collapsed into a single "foo>=0.4" dependency.
|
|
after the changes in revision 1.27 of tools.mk to hide the auto* tools
between pre-configure and do-configure.
|
|
target. This still allows any autoconf/automake we execute at
pre-configure time to find its own scripts, but forces the configure script
find our stubs instead. This should prevent the need to constantly
override the missing script using GNU_MISSING_OVERRIDE.
|
|
|
|
|
|
pkg-config to only look in ${BUILDLINK_DIR}/lib/pkgconfig for *.pc files.
This will correctly hide the presence of software from configure scripts
that query pkg-config for that information.
Idea suggested by Julio M. Merino Vidal.
|
|
|
|
|
|
config.status. Instead, only block "config.status --recheck", which
re-executes the GNU configure script. This still allows config.status to
overwrite post-configure changes to Makefiles and config.h files, so those
changes should (properly) be applied to Makefile.in and config.h.in
instead.
|
|
|
|
|
|
As seen in devel/libg++ with its libg++.info file...
|
|
actually has some effect.
|
|
|
|
|