Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
("fortran" denotes post-Fortran-77 dialects).
|
|
the package. For f2c, all Fortran 95+ programs are broken and it is
generally not possible to mix output from different Fortran compilers.
Default to g95 for now as fallback compiler.
|
|
|
|
tex-related logic and breaks the build of e.g. graphics/asymptote.
|
|
|
|
no longer using it.
|
|
remove it from xorg mirror list.
|
|
(1) mail/wl/Makefile
- Add LICENSE= gnu-gpl-v2.
- Use # none instead onf # defined (EMACS_BUILDLINK=).
- Use set instead of @set.
(2) mail/wl/patches/patch-aa
- Add comment from old cvs log.
(3) mail/wl/patches/patch-utils_ptexinfmt.el
Avoid diff -c confusion by pkglint:
-*** [info] Error code 255
+ *** [info] Error code 255
(4) mk/defaults/options.description 14 Jun 2013 04:48:54 -0000
Add following option:
+emacs-w3m W3m browser extention.
|
|
gcc packages. Bail out if runtime support is requested but we do not
provide runtime libraries for the chosen compiler.
|
|
This is a provisional kludge to work around PR pkg/47838. Sorry for
taking far too long to find a workaround that doesn't break various
other stuff too -- this duration of time was ridiculous, and it was
entirely my fault.
We can get rid of this kludge when we start using `env -i' in the
build phase or when we replace TARGET_ARCH by TARGET_MACHINE_PLATFORM
(and replace the make-internal variable MACHINE_ARCH by
MACHINE_PLATFORM -- that is part of what makes the logic in
pkgformat/pkg/depends.mk and bsd.prefs.mk so fragile). However,
although I intend to do both of these things, they were deemed too
likely to cause too much fallout just before the freeze, so they'll
wait until after the freeze.
|
|
Rationale: undocumented, easily replaced with "CONFIGURE_ARGS+=--libdir="
and only used by 10 packages.
|
|
USE_BUILTIN checking loop.
|
|
and force USE_BUILTIN.pkg=no for packages that depend on packages where
USE_BUILTIN.pkg is no. The names of any such packages are accumulated in
the variable FORCED_PKGSRC for reference; this is currently undocumented
and could be dropped in the future.
This makes it a lot safer to install pkgsrc versions of selected X
libraries without switching wholesale to pkgsrc X; however, other
issues may still exist and caution is still advisable.
As seen on tech-pkg.
Also note: this may affect the builds of packages we don't realize are
affected and that haven't been revbumped. If you find one, let us know
so we can bump its version (or do that yourself) -- most likely this
change will produce in working, properly-linked packages that were
previously broken, but if problems arise please speak up.
|
|
|
|
might fix PR pkg/47883.
|
|
in ${TOOLS_DIR}/bin, same as other tools.
|
|
1.) It breaks the build of "www/firefox" which gets upset if "SHELL" is
not defined in the environment. There are probably more packages
which similar problems.
2.) It breaks established use case like this one:
export ALLOW_VULNERABLE_PACKAGES=yes
cd pkgsrc/multimedia/ffmpeg2theora
bmake install
In this case the value of "ALLOW_VULNERABLE_PACKAGES" will not be
passed to the build of "pkgsrc/multimedia/ffmpeg". And the build of
this package will fail due to known vulnerabilities.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
`install' with USE_DESTDIR=yes.
This changes prevent to unwanted overwite of existing binary packages with
test installation (`stage-install', `replace' & `undo-replace', and so on).
To do both `install' and `package', you can still use `package-install' target,
same as USE_DESTDIR=no.
|
|
lang/gcc48 don't work otherwise.
|
|
|
|
|
|
* Set PATCH_DEBUG when PKG_DEVELOPER=yes.
No objection to
http://mail-index.netbsd.org/tech-pkg/2013/05/06/msg011276.html .
|
|
|
|
substitutions will not be correct.
Fixes issue with ABI=64 where /usr/lib/amd64 was being exposed, but
packages will need to be rebuilt for the change to take effect.
|
|
right now, `-b' option for Cygwin.
|
|
|
|
|
|
however that is not the case. To get that behaviour use ':S/c/ /g'.
Fixes a number of issues on various OPSYS introduced with the recent
COMPILER_* and SYSTEM_DEFAULT_RPATH abstractions.
|
|
|
|
|
|
It is used in limited case, and does not exist by default on some platforms.
proposed at over 30 months ago, and no negative feedback (only one request).
|
|
but it is never used now, so back to true `file' command.
|
|
|
|
|
|
hierarchy.
This values should be generated from output of some commands,
but I cannot find the rule.
Tested on armel and x86_64 Debian GNU/Linux environment.
The values are shown in http://wiki.debian.org/Multiarch/Tuples .
|
|
|
|
descriptions.
|
|
|