On 25 Dec 2016, at 19:21, Nikolai Lifanov wrote:
>
> I would like to understand why WITH_SHARED_TOOLCHAIN is not the default.
This has been a long standing tradition. Mainly, because you could
theoretically rescue yourself out of some bad situations by being able
to compile yourself out of it,
On 25 Dec 2016, at 19:21, Nikolai Lifanov wrote:
>
> Hi list,
>
> I would like to understand why WITH_SHARED_TOOLCHAIN is not the default.
> My Raspberry Pi 3 is self-hosting with -j4 and doesn't run out of memory
> if the toolchain is shared. Is there a downside to this option?
Yes, there is a
Hi list,
I would like to understand why WITH_SHARED_TOOLCHAIN is not the default.
My Raspberry Pi 3 is self-hosting with -j4 and doesn't run out of memory
if the toolchain is shared. Is there a downside to this option?
Thanks,
- Nikolai Lifanov
signature.asc
Description: OpenPGP digital signa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863
--- Comment #12 from Antoine Brodin ---
(In reply to Jan Beich (mail not working) from comment #11)
Unless the FreeBSD Security Officer changes his mind, at 23:59 UTC December
31, 2016, FreeBSD 9.3, 10.1 and 10.2 will reach end-of-life and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863
--- Comment #11 from Jan Beich (mail not working) ---
What's portmgr's plan for quarterly? Will 2017Q1 still support 9.x, 10.1, 10.2
and tag RELEASE_9_EOL at the end?
--
You are receiving this mail because:
You are on the CC list for the
