Age | Commit message (Collapse) | Author | Files | Lines |
|
Added some code to check for unknown options.
Reindented the file so that the compiler options are better visible.
They had been hidden by the massive block comments before. Also, every
option has got its own line so that one only needs to read the first
column to find the relevant code.
|
|
make the wrapper code less frightening. For example, instead of
arg="${arg#-Wl,}"
$debug_log $wrapperlog " (transform-sunpro-cc) to: $arg"
addtocache=yes
one can simply write
transform_to "${arg-Wl,}"
The functions that are currently implemented are: transform_to,
transform_discard, transform_to_nocache, transform_discard,
transform_pass and transform_pass_unknown.
|
|
Makefile dependencies.
|
|
|
|
plain $.
|
|
allowed between the "#" and the "define", and the value must be of the
form "${varname}/...", that is, starting with a double quote, followed
by "${" and a variable name, and directly behind the closing brace must
be a slash. This should catch most false positives while still being
useful.
|
|
|
|
|
|
|
|
The program now exits with the correct exit status in case of errors.
|
|
|
|
|
|
huge performance problem: When reading files, it calls read(2) for every
single byte. awk instead reads a whole line at a time. For the lang/php5
package, the execution time changed from (7.8 real 4.5 user 3.1 sys) to
(1.6 real 1.5 user 0.4 sys).
|
|
explanation for an error message, nicely formatted.
Added explanations for the checks in check-portability.sh.
|
|
individual files.
|
|
|
|
|
|
since according to the comment in check/bsd.check.mk, they belong there.
Added a new check for all C and C++ header files to make sure they don't
contain strings like ${prefix} or ${exec_prefix}, which is currently a
problem with sysutils/dbus and has been noticed in PR 35019. This check
is disabled by default since I don't know anything about possible false
positives, but I plan to enable it for PKG_DEVELOPERs after some
testing.
Added two names for hooks that are placed in the configure and in the
build phase. Now the checks look more like becoming something one could
call a framework, sharing a common structure and a documented interface.
|
|
another process. It's a little more verbose now, but it helps
understanding what goes on.
|
|
|
|
|
|
|
|
Default value is kept but now set in mk/defaults/mk.conf.
|
|
don't use mkdir, as the latter uses the group permissions of the
parent directory under BSDs, resulting in group leaks for
USE_DESTDIR=yes. Discussed with agc@.
|
|
|
|
list for bulk builds. (Revert previous on bootstrap; the PKG_PRESERVE
hack didn't work as expected.)
|
|
wrong about some of its results when using implied privileges (e.g., an
account in group Administrators where the directory is writable by Users).
|
|
Assume those two can handle their own dependencies.
|
|
|
|
|
|
is not supported at all by pkgsrc, print an error message in that case.
|
|
|
|
|
|
SETUID_ROOT_PERMS.
|
|
|
|
|
|
the case of modular Xorg and the latter is more specific.
|
|
|
|
the fullly conditionalised bsd.prefs.mk still needs a considerable
amount of time and moving the include guard out kills most of that.
Preliminary tests with renaming bsd.prefs.mk and using the same logic
to point to the real files show 5%-10% reduced run time for
"make show-options" in x11/kdebase3 and no measurable regression in
simpler places. This versions allows incremental conversion of the
use in buildlink3.mk. Some care should be used in mk/ itself, as e.g.
bsd.pkg.mk is included from first level hierachies as well.
|
|
|
|
or [] is better, I have used [ to keep the code shorter. Noticed by wiz.
|
|
overwritten when the package-provided files are (possibly dead)
symlinks. Since on Mac OS X, ls(1) does not return the status I
expected, I investigated a little in the available options of test(1),
and found that the "-h" option should be quite portable. So let's try
that instead.
This fixes PR 34865.
|
|
|
|
mk/defaults/mk.conf.
|
|
doesn't match the *.mk pattern, and that's why it had been excluded up
to now, accidentally.
|
|
For that purpose, BUILD_DEFS_EFFECTS has just been introduced.
|
|
the user to affect how packages are built (BUILD_DEFS) and the effects
that those variables have (BUILD_DEFS_EFFECTS). The latter variable has
been introduced to clearly separate these two issues.
While here, reduced the indentation of the directives a little bit. One
visible change is that "make build-defs-message" will always show the
message when called directly. Before, it had been shown only once, which
makes debugging a bit more difficult.
|
|
|
|
|
|
need to specify INSTALLATION_DIRS itself. Instead, the list is generated
from the static PLIST files. Like for INSTALLATION_DIRS, mtree is
disabled when this variable is set.
|