Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
to tech-pkg:
=====
* USE_BUILDLINK3=YES will be unconditional. (In fact, USE_BUILDLINK3 will
be ignored altogether by mk/; but see below.)
* NO_BUILDLINK and NO_WRAPPER will be ignored by mk/. If a build happens,
these phases will happen.
* The existing NO_BUILD will imply the previous NO_BUILDLINK and NO_WRAPPER.
If no build happens, those phases are not needed.
* NO_TOOLS will be ignored by mk/. The tools phase, which provides much
more than just the C compiler, will always happen regardless of package.
This will make metapackage builds only slightly slower, in trade for far
less user error.
|
|
old and buggy, and if a package wants USE_GNU_TOOLS+=awk, pull in lang/gawk
instead for less problems.
|
|
There's no need to check for a do-tools target; nothing should override it.
Vertically consolidate the dependency.
|
|
This solves the problem of building GNU tools that explicitly or
implicitly depend on other GNU tools. This problem has presented a
bootstrap issue on platforms with few GNU tools, especially where
USE_PKGSRC_GCC is used.
Based on a patch posted by sketch on tech-pkg in December 2003.
|
|
is flex, but libfl.a and FlexLexer.h are missing. So use pkgsrc flex
on an as-needed basis.
|
|
that native perl is never used.
Suggested by jlam@.
|
|
-b Compile stubs in "backwards compatible" mode, disabling
support for transport-independent RPC. The -b should always
be specified when generating files for NetBSD, since there is
no transport-independent RPC support in NetBSD.
Therefore, force "-b" to be the first argument whenever rpcgen is invoked
via the wrapper.
|
|
The wrapper will correctly set the CPP environment variable to a
stat((2)able path to a C preprocessor, then rely on the PATH to
find and invoke the real rpcgen.
Remove NO_EXPORT_CPP in package Makefiles where it was used just to
avoid problems with rpcgen. The build system now just does the right
thing automatically without needing package-specific knowledge.
This fixes PR pkg/27272.
|
|
|
|
in PR pkg/27258.
|
|
|
|
(how did this ever work?)
|
|
explicitly undef YACC.
YACC?=yacc is set in sys.mk, but this interferes with building some
packages that require bison because they try ${YACC} and fail.
|
|
version of gawk in /usr/contrib/bin, so use that instead.
|
|
_TOOLS_REPLACE_OPSYS setting to pick up nbsed in tools.mk; no need to
throw more into autoconf's environment.
|
|
(1) defs.${OPSYS}.mk --> platform/${OPSYS}.mk.
The "platform" subdirectory is where all of the ${OPSYS}-specific
infrastructure logic should reside.
(2) bsd.pkg.defaults.mk --> defaults/mk.conf
bsd.pkg.obsolete.mk --> defaults/obsolete.mk
Renaming bsd.pkg.defaults.mk to defaults/mk.conf is to mimic the way
that NetBSD has /etc/rc.conf as well as /etc/defaults/rc.conf, where
the latter is a full list of user-settable variables, and the two
files share the same name to reinforce the fact /etc/defaults/rc.conf
can be directly copied in place as /etc/rc.conf. This is the same
relationship shared by defaults/mk.conf and /etc/mk.conf.
|
|
For me this fixed the build of devel/kdevelop-base version 3.1.0 with latest
automake package version 1.9.1 installed.
|
|
|
|
${TOOLS_DIR}/bin. It will either point to /usr/bin/tbl or will depend
on groff otherwise.
This should allow removing dependencies on groff just for the sake of
forcing the existence of tbl.
|
|
|
|
pull in devel/flex/buildlink3.mk instead of just listing a BUILD_DEPENDS.
This is needed because flex installs a library.
|
|
cope with "new" files (i.e., -0+0 starting line). Do what AIX does and
make pkgsrc depend on textproc/patch for Interix.
|
|
|
|
|
|
|
|
|
|
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.
|
|
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.
|
|
This allows any autoconf/automake we execute at pre-configure time to find
its own scripts, yet still prevents "make build" from clobbering any
changes we may have made.
|
|
due to a type on gcc.mk that causes the ${_GCC_PREFIX}/bin to always be
prepended to the PATH. The problem that was hiding was "make" resolving
to ${TOOLS_DIR}/bin/make if the package used GNU make, which broke
building since the package Makefile is a BSD Makefile and we passed
PATH to some phases of the build. Fix this by expanding MAKE to the
full path to ${MAKE} in bsd.prefs.mk. We also garbage collect the now
useless checks for PHASES_AFTER_BUILDLINK that cluttered the PREPEND_PATH
code.
|
|
(by checking PREPEND_PATH) and only for those phases of the build that
care about the PATH (buildlink or later). We also pass the PATH to
those same phases of the build so that executing ${CC} will work correctly
from custom {pre,do,post}-* targets that occur at buildlink time or
later.
|
|
to build some packages on some platforms.
|
|
in fact, the last revision didn't contain unwanted changes, but two
minor errors, now fixed. sorry for the mess.
|
|
|
|
|
|
If problems arise, we can always remove it later.
jlam@ agrees (see tech-pkg).
|
|
|
|
|
|
Pointed out by Bas van Oostveen in PR pkg/23514.
|
|
fixes PR pkg/22844.
|
|
|
|
cd pkgsrc/mk
cvs update -Pd -A
cvs update -Pd -j pkgviews-mk-base -j pkgviews-mk
|
|
${LOCALBASE}/bin/gmake. ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}/make
technically works, too, but this covers the (unsupported!!) case where the
user has GNU_PROGRAM_PREFIX="" and has moved the "make" binary directly
over the "gmake" symlink created by pkgsrc (Jeremy Reed reported this
problem on tech-pkg@ because he uses this a a debugging technique to find
out whether GNU make is actually needed by a package or not).
|
|
|
|
${TOOLS_DIR}/bin/make. If a package wants GNU make, then it should
set:
USE_GNU_TOOLS+= make
in the package Makefile. Allow for USE_GMAKE to continue to work
until we get a chance to sweep through pkgsrc and remove the usage
of this now-redundant variable.
This change allows us to avoid patching makefiles that use a bare
"make" command to invoke sub-make processes. Idea suggested by
salo@netbsd.org in pkg/22509.
|
|
either the environment or in /etc/mk.conf by telling dependencies of the
named GNU tool to ignore any USE_GNU_TOOLS settings when they are built.
|
|
sure that tool is symlinked into ${TOOLS_DIR}/bin.
|
|
|
|
|