We'd love to rsync the repository more real-time, but haven't got the bandwidth.
And even if we did, there still would be moments between when you fetch, start a build. Hint to everyone: Fetch. Build. See error? re-fetch, rebuild. If it happens the 2nd time, then maybe... Do you understand it is a lot of noise? >OK, I'll try again. I do follow the source changes via gmane with a >newsreader but I think there's a bit of delay. > >Thanks. > >On Sun, Apr 13, 2014 at 11:27 PM, Ted Unangst <[email protected]> wrote: >> On Sun, Apr 13, 2014 at 23:15, Chris Smith wrote: >>> Guess I'm missing the point, Downloaded src from scratch and now >>> getting a different error (on two separate systems) when trying to >>> build userland: >>> >>> mandoc -Tlint -Wfatal /usr/src/usr.sbin/ntpd/ntpctl.8 >>> ===> usr.sbin/openssl >>> cc -O2 -pipe -DMONOLITH -DTERMIOS -DANSI_SOURCE -DOPENSSL_NO_RC5 >>> -DOPENSSL_NO_SSL2 -I/usr/src/usr.sbin/openssl/../../lib/libssl/src >>> -c /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c >>> /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c:72: >>> error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cb' >> >>> These things built -current fine a week ago. >> >> If you're not subscribed to source-changes, you should be. And if you >> are, you should have seen a few dozen commits to libssl recently. >> >> Do you need to build current? Probably not. That's why we provide >> snapshots. >> >> Build errors that don't come with patches aren't very interesting >> because by the time you report it, somebody else will have found it >> and fixed it.
