From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <877fl6ronj.fsf@rudra.copyninja.info> Date: Thu, 26 Nov 2015 21:56:44 +0000 Message-ID: From: Charles Forsyth To: Ryan Gonzalez Content-Type: multipart/alternative; boundary=001a11467fc69649a1052578a62d Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Compiling ken-cc on Linux Topicbox-Message-UUID: 78830d9c-ead9-11e9-9d60-3106f5b1d025 --001a11467fc69649a1052578a62d Content-Type: text/plain; charset=UTF-8 On 26 November 2015 at 21:51, Charles Forsyth wrote: > On 26 November 2015 at 21:49, Ryan Gonzalez wrote: > >> All that is bad...but glibc is worse. The issue is that you kinda *have* >> to use it, > > > true, very true. i remember glibc being my first instance of having to buy a bigger drive just to build the thing. with clang+llvm, I revisited that, and also had to buy more RAM and CPU. i wondered whether to have a cron entry to speak "WTF?" into /dev/audio every so often, to save my voice (cron would be good because it could switch to "blistering barnacles!" when children were present). --001a11467fc69649a1052578a62d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 26 November 2015 at 21:51, Charles Forsyth <charles.forsyth@gma= il.com> wrote:
On 26 November 2015 at 21:49, Ryan Gonzale= z <rymg19@gmail.com> wrote:
All that is bad...but glibc is worse. The issue is that you kinda *have* t= o use it,

true, very true.
<= br>i remember glibc being my first instance of having to buy a bigger drive= just to build the thing.
with clang+llvm, = I revisited that, and also had to buy more RAM and CPU.
i wondered whether to have a cron entry to speak "WTF?&qu= ot; into /dev/audio every so often, to save my voice
(cron would be good because it could switch to "blistering b= arnacles!" when children were present).
--001a11467fc69649a1052578a62d--