public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Blanchard <dave@killthe.net>
To: gcc@gcc.gnu.org
Subject: GNAT on GCC 10.x has build problems
Date: Sun, 3 Dec 2023 12:22:48 -0600	[thread overview]
Message-ID: <20231203122248.6f6d7c840a73f25f85ce1360@killthe.net> (raw)

Hello all, while bootstrapping GNAT onto my cross compiled system with GCC 10.x I found that the make script leaves something to be desired. 

First off it doesn't add the host prefix to the cross compiler binaries; it calls gnatmake, gnatlink, gnatbind, gnatls, and gcc without the x86_64-linux-gnu- prefix, requiring an ugly hack to symlink to those tools to complete the build. Also at the end of the build there is an error when it tries to install gnatdll, which isn't built, doesn't exist, and is for Windows only. 

Does anyone know if these problems are fixed in later GCC versions? And do these people even test their obviously broken crap before releasing it on the world?

I also note that the AdaCore team seem to be doing everything in their power to railroad people into giving them money for their proprietary compiler. First they disabled C and C++ languages in their 2018-up Community Edition binaries, which makes bootstrapping a full GCC impossible with these tools. I guess that didn't do the trick as people just used older CE releases to bootstrap with instead, so they discontinued CE entirely and removed links to the CE download page from their site, making it hard to find unless one knows what to search for. 

I've also been told that there is some kind of special licensing clause for the GNAT project which requires all code built by their GPL compiler to be GPL3 licensed, which is a laugh as I'm never doing that. Not sure if that's actually true or not. 

Anyhow, it's surprising (or should be surprising) to see such shoddy workmanship from an anti-freedom commercial organization joined to the hip with GCC.

Dave


             reply	other threads:[~2023-12-03 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03 18:22 Dave Blanchard [this message]
2023-12-03 19:05 ` Jonathan Wakely
2023-12-03 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=20231203122248.6f6d7c840a73f25f85ce1360@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).