-O[12] builds make jade(1) segfault in libostyle.so on sparc64,
-O0 runs fine; this is triggered through the docbook-utils build:
> SGML_SEARCH_PATH=../..:../../doc:.. \
> jade -t sgml -i html -d ../../docbook-utils.dsl\#html \
> -V '%use-id-as-filename%' ../../doc/docbook-utils.sgml
> Segmentation fault (core dumped)
Regen PLIST while here.
OK kmos
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
individual port, introduce a new variable for bsd.port.mk, VMEM_WARNING.
By setting this variable to `Yes', the user is given a warning about the
virtual memory requirements just before the pre-build stage.
o Also give some examples for different shells for what to do about
it, and mention login.conf(5). bash, for example, has a confusing
-v flag to ulimit.
o Document this in bsd.port.mk.5
espie@ ok
(this is silently ignored if the catalog file doesnt exist)
- install DTD files in prefix/share/sgml/openjade which weren't done before
- MAKE_FLAGS now respect CFLAGS and CC
- take MAINTAINER, bump NEED_VERSION
ok matthieu@
