From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Dave Blanchard <dave@killthe.net>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GNU = Junkware
Date: Sat, 26 Nov 2022 10:41:54 +0000 [thread overview]
Message-ID: <CAH6eHdRYv59fPfZkzXp-Bm4o7F2qc2kLBSrAZcaMr-U=qTOmkQ@mail.gmail.com> (raw)
In-Reply-To: <20221126032052.2f32ed2af88309edd76aa262@killthe.net>
[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]
Cool story bro
On Sat, 26 Nov 2022, 09:20 Dave Blanchard, <dave@killthe.net> wrote:
> No, I'm not trolling, just venting here for a moment. So sick of garbage
> ass, crusty junkware that's always a battle to the death to accomplish
> anything.
>
> I really understand where Liu Hao was coming from yesterday when he was in
> here raging against the AT&T assembler. I could sense the bitterness and
> disgust in him, the kind that can only come from a lifetime of bitter
> disappointment in the status quo. It's like he's just as sick and tired as
> I am of broken ass, buggy software.
>
> GNU GCC/GLIBC IS THE MOST PAINFUL PIECE OF SHIT FUCKING SOFTWARE ON THE
> PLANET TO BOOTSTRAP.
>
> Not even the flaming pile of dogshit that is PYTHON comes close to the
> misery and hell awaiting any hapless person who wants to accomplish what
> ought to be the Simple And Straightforward Fucking Task of bootstrapping a
> cross-compiled GNU gcc/glibc/binutils system.
>
> I have been working on this project FOR AN ENTIRE YEAR and the pain just
> never seems to end.
>
> I've encountered every shitty, stupid, inane, puzzling, worthless,
> completely nonsensical error message that could possibly be generated by a
> piece of software, which almost NEVER leads toward figuring out exactly
> went wrong, but usually just deeper into the quagmire.
>
> Seemingly the only way that will ever finally get this junk working is to
> just sit there randomly trying different stuff in the hope that it somehow
> moves one closer toward getting something that works right.
>
> /rant
>
> --
> Dave Blanchard <dave@killthe.net>
>
next prev parent reply other threads:[~2022-11-26 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 9:20 Dave Blanchard
2022-11-26 10:41 ` Jonathan Wakely [this message]
2022-11-26 14:24 ` Paul Smith
2022-11-26 16:15 ` Paul Koning
2022-11-27 14:53 ` LIU Hao
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='CAH6eHdRYv59fPfZkzXp-Bm4o7F2qc2kLBSrAZcaMr-U=qTOmkQ@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=dave@killthe.net \
--cc=gcc@gcc.gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).