From: Ryan Gonzalez <rymg19@gmail.com>
To: Charles Forsyth <charles.forsyth@gmail.com>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Compiling ken-cc on Linux
Date: Thu, 26 Nov 2015 16:02:33 -0600 [thread overview]
Message-ID: <835ECE9E-472C-448D-8125-67BBACB09752@gmail.com> (raw)
In-Reply-To: <CAOw7k5jps0Zpv38+5fjA_5OSsLqhGC5aYwsarSDkmh4oBQs-sw@mail.gmail.com>
On November 26, 2015 3:56:44 PM CST, Charles Forsyth <charles.forsyth@gmail.com> wrote:
>On 26 November 2015 at 21:51, Charles Forsyth
><charles.forsyth@gmail.com>
>wrote:
>
>> On 26 November 2015 at 21:49, Ryan Gonzalez <rymg19@gmail.com> 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 remember the time I was trying to build LLVM+Clang on Windows in debug mode. Because...MinGW...I actually surpassed the file size limit when linking Clang, so I had to rebuild EVERYTHING. Stupid thing took about an hour each time.
Because MinGW.
>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).
It would be so funny if it malfunctioned:
WTF barnacles!
blistering WTF?
--
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2015-11-26 22:02 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 17:10 Vasudev Kamath
2015-11-25 17:15 ` Ryan Gonzalez
2015-11-25 17:24 ` Vasudev Kamath
2015-11-26 12:08 ` Charles Forsyth
2015-11-27 16:50 ` Vasudev Kamath
2015-11-27 16:59 ` Ryan Gonzalez
2015-11-27 17:16 ` Vasudev Kamath
2015-11-27 18:24 ` Ryan Gonzalez
2015-11-29 9:41 ` Vasudev Kamath
2015-11-29 14:38 ` Ryan Gonzalez
2015-11-27 18:11 ` trebol
2015-11-26 12:10 ` Charles Forsyth
2015-11-26 12:18 ` David du Colombier
2015-11-26 18:15 ` Ryan Gonzalez
2015-11-26 21:31 ` Charles Forsyth
2015-11-26 21:49 ` Ryan Gonzalez
2015-11-26 21:51 ` Charles Forsyth
2015-11-26 21:56 ` Charles Forsyth
2015-11-26 22:02 ` Ryan Gonzalez [this message]
2015-11-26 22:08 ` Charles Forsyth
2015-11-26 22:30 ` David du Colombier
2015-11-26 23:08 ` Ryan Gonzalez
2015-11-26 23:21 ` Charles Forsyth
2015-11-26 23:41 ` Ryan Gonzalez
2015-11-27 0:02 ` Brantley Coile
2015-11-27 8:13 ` Giacomo Tesio
2015-11-27 8:56 ` arnold
2015-11-27 13:33 ` Steffen Nurpmeso
2015-11-28 0:55 ` erik quanstrom
2015-11-30 15:46 ` Steffen Nurpmeso
2015-11-27 12:42 ` tlaronde
2015-11-27 14:07 ` Giacomo Tesio
2015-11-27 14:34 ` tlaronde
2015-11-28 1:01 ` erik quanstrom
2015-11-27 12:05 ` Steffen Nurpmeso
2015-11-27 12:32 ` lucio
2015-11-26 21:40 ` Andrew Simmons
2015-11-28 6:42 da Tyga
2015-11-28 7:40 ` Brantley Coile
2015-11-28 20:31 ` Anthony Sorace
2015-11-28 23:33 ` Brantley Coile
2015-11-29 6:12 ` lucio
2015-11-28 20:13 ` Ryan Gonzalez
2015-11-29 5:57 ` lucio
2015-11-29 16:17 ` tlaronde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=835ECE9E-472C-448D-8125-67BBACB09752@gmail.com \
--to=rymg19@gmail.com \
--cc=9fans@9fans.net \
--cc=charles.forsyth@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).