Re: Freebsd-7.4 + std gcc 4.2.1 fails to honour -march=i586

In the last episode (Jul 17), Julian H. Stacey said: > Hi all, > ENVIRONMENT: > Standard > gcc version 4.2.1 20070719 [FreeBSD] > that comes with > FreeBSD 7.4-RELEASE > on my 686 host with > CFLAGS += -march=i586 > in > /etc/make.conf > used with >

Freebsd-7.4 + std gcc 4.2.1 fails to honour -march=i586

Hi all, ENVIRONMENT: Standard gcc version 4.2.1 20070719 [FreeBSD] that comes with FreeBSD 7.4-RELEASE on my 686 host with CFLAGS += -march=i586 in /etc/make.conf used with cd /usr/src/bin/who ; make clean ; make cleandir ; make clean ; m

Re: FIB separation

On Jul 16, 2011, at 5:42 PM, Hiroki Sato wrote: > Vlad Galu wrote > in : > > du> Hello, > du> > du> A couple of years ago, Stef Walter proposed a patch[1] that enforced > du> the scope of routing messages. The general consesus was that the best > du> approach would be the OpenBSD way - transpo

Re: FIB separation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hiroki Sato wrote: > Vlad Galu wrote > in : > > du> Hello, > du> > du> A couple of years ago, Stef Walter proposed a patch[1] that enforced > du> the scope of routing messages. The general consesus was that the best > du> approach would be the Open

Re: FIB separation

Vlad Galu wrote in : du> Hello, du> du> A couple of years ago, Stef Walter proposed a patch[1] that enforced du> the scope of routing messages. The general consesus was that the best du> approach would be the OpenBSD way - transporting the FIB number in the du> message and letting the user appl

FIB separation

Hello, A couple of years ago, Stef Walter proposed a patch[1] that enforced the scope of routing messages. The general consesus was that the best approach would be the OpenBSD way - transporting the FIB number in the message and letting the user applications filter out unwanted messages. Are t