Commit Graph

11 Commits

Author SHA1 Message Date
naddy 3f5796b9fd drop RCS Ids 2022-03-11 19:45:43 +00:00
sthen a3e5de8f53 drop maintainer 2020-02-03 20:40:37 +00:00
sthen 9c6e9626b9 s/PERMIT_PACKAGE_CDROM/PERMIT_PACKAGE/ and some light whitespace tidying
in ports which I maintain
2019-06-03 16:06:50 +00:00
sthen b17bf3228e update curses WANTLIB entries following the change in base libraries to use soname 2019-05-17 16:19:37 +00:00
sthen 25f0e460f2 Add COMPILER lines to c++ ports which currently use the default. Adjust
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.
2018-10-24 14:27:57 +00:00
sthen 5e964ab0df bump LIBCXX/LIBECXX/COMPILER_LIBCXX ports. 2017-07-26 22:45:14 +00:00
espie c114d7057b add pthread to COMPILER_LIBCXX.
white lie, but it allows clang and gcc to be more similar
bump accordingly.
2017-07-23 09:26:25 +00:00
espie 8ac47fd9c6 use COMPILER_LIBCXX where applicable 2017-07-16 19:18:47 +00:00
sthen 073d25a37c use LIBCXX 2017-04-10 11:46:32 +00:00
jca 52b5acd7d6 Cope with latest bison; ok sthen@ 2015-11-15 11:55:59 +00:00
sthen db085ded4c import net/irrtoolset, ok benoit@
The IRRToolSet is a set of tools to work with Internet routing policies.
These policies are stored in Internet Routing Registries (IRR) in the
Routing Policy Specification Language (RPSL). The tools are used to
produce lists suitable for automating router configuration, etc.

- peval is a low level policy evaluation tool that can be used to write
router configuration generators. It takes policy expressions as input,
expands the AS sets, route sets, filter sets and (optionally) AS numbers,
and outputs the resulting list of AS numbers or prefixes.

- rpslcheck syntax-checks an RPSL object to determine whether it will
cause problems for any of the tools in IRRToolSet, such as rtconfig.
This does not guarantee that the syntax is valid for a particular IRR,
which may have different syntax constraints.

- rtconfig is a filter which can generate cisco/juniper configuration
sections based on information from IRRs.
2014-10-31 16:43:44 +00:00