From: Dave Blanchard <dave@killthe.net>
To: gcc@gcc.gnu.org
Subject: Re: Good grief Charlie Brown
Date: Tue, 13 Dec 2022 13:09:31 -0600 [thread overview]
Message-ID: <20221213130931.c0275819db8865ffa75d1dd6@killthe.net> (raw)
Since my response did not get posted (maybe one of the words wasn't allowed? or because I attached binaries?) here it is again:
Begin forwarded message:
Date: Tue, 13 Dec 2022 11:35:39 -0600
From: Dave Blanchard <dave@killthe.net>
To: gcc@gcc.gnu.org
Cc: paul@mad-scientist.net
Subject: Re: Good grief Charlie Brown
> I guess if you were one of the "everybody" needing "everything" on
> "every" environment, instead of you needing what you need in your
> environment, you might think differently!
*angry, grumpy, pi$$ed off, GNU-hating distro maintainer enters the chat*
Yeah, and if you were one of those people who has spent the last 14 MONTHS banging your head on the wall trying to *properly* bootstrap gcc, and to *ensure* that the bootstrap is correct--while still having no clue after all this time if it is *really* correct now, or only *pretending* to be correct for a while, until the next time something screws up with the weirdest error messages imaginable, showing that it's not--YOU might feel differently.
Just like the other day when I thought it would be a simple matter to add 'D' language to my distro. I'm on GCC 9, switching the distro and build scripts over to GCC 12, and thought "hey, I'll take advantage of GCC 9 while it's here to build GDC9, then bootstrap GDC12 with it, and I'll have D also, finally! hooray!" Yeah, right.
SOMETHING somewhere is wrong/misconfigured with the bootstrap I guess, because on the second build of GCC12 it dies with some ridiculous libatomic-related error message, and nobody on the mailing list has any idea what it could possibly be I guess, since nobody responded to my email.
My response: just delete D from --enable-languages and forget I ever heard about it, because I'm definitely not spending ANOTHER year trying to figure out this junk.
Don't get me wrong, I'm happy to have GCC, but it is HORRIBLY DESIGNED SOFTWARE. As is GLIBC. Matter of fact, pretty much everything out of GNU is the most overcomplicated and/or painful junk imaginable. (gnulib anyone?) And don't tell me it has to be this way. I know that it doesn't.
The freshly-generated manual pages for GCC 12.2 are attached to this email, for OP. [edit: removed. Sorry.]
Dave
next reply other threads:[~2022-12-13 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 19:09 Dave Blanchard [this message]
2022-12-13 19:20 ` Paul Koning
2022-12-13 19:29 ` Dave Blanchard
2022-12-13 20:35 ` Jonathan Wakely
-- strict thread matches above, loose matches on Subject: below --
2022-12-13 16:28 Jim Anderson
2022-12-13 16:41 ` Paul Smith
2022-12-13 17:35 ` Dave Blanchard
2022-12-13 18:31 ` Paul Smith
2022-12-13 19:16 ` Dave Blanchard
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=20221213130931.c0275819db8865ffa75d1dd6@killthe.net \
--to=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).