[Xorp-hackers] FreeBSD ports/net/xorp-devel added.
Bruce Simpson
bms at incunabulum.net
Tue Dec 8 02:56:14 PST 2009
FYI all,
In lieu of a 1.7 release, which is long overdue:
I've checked in a FreeBSD port entry, for the current line of
development in SVN, as of today:
http://www.freshports.org/net/xorp-devel
A few things are now turned on by default in the FreeBSD package, these are:
* Optimization level -O1 in GNU C++ is now the default.
XORP uses the C++ Standard Template Library.
-O1 is necessary with gcc to generate reasonable code in this case.
This offers a measurable binary size reduction, without compromising
the ability to debug any code where needed.
* Shared libraries.
This offers a significant, measurable binary size reduction.
FreeBSD/amd64 binaries for a full router are ~22MB.
* Using UNIX domain sockets for IPC by default.
These offer a measurable increase in RPC performance, when XORP
components need only run on a single local router.
* Using rtld ORIGIN; package relocation.
On systems with a modern ELF runtime linker (FreeBSD 8.0, Linux),
this allows the package to be relocated on disk.
Other changes:
* The Boost C++ libraries are now used by XORP, and you will need
these to compile.
* PCAP is now only linked by the FEA process.
* SNMP support has been retired, as it was, in fact, mostly a no-op
for all of the protocol modules except BGP.
The implementation really needs to be revisited, to be scalable in
BGP default-free-zone deployments.
* The package now confirms to BSD hier(7), and should be compliant
with the Linux Filesystem Hierarchy Standard (FHS), which should help
folk packaging the community XORP tree for distribution in e.g. Ubuntu,
Debian, Fedora.
The only changes I'd plan further here, for now, would be to bring
xorp_rtrmgr in line with the behaviour of other UNIX-like daemons; right
now, the -d switch enables daemonization, rather than disabling it.
thanks,
BMS
More information about the Xorp-hackers
mailing list