From: Ricardo Wurmus <rekado@elephly.net>
To: Guix-devel <guix-devel@gnu.org>
Subject: enabling all supported languages in GCC
Date: Thu, 19 May 2016 10:20:30 +0200 [thread overview]
Message-ID: <87eg8yihm9.fsf@elephly.net> (raw)
Hi Guix,
we have some problems with GCC. Since the “gcc” executables produced by
the “custom-gcc” procedure did not provide a functioning “gcc” for C and
C++ one could not just install, say, “gfortran” into a profile and have
both a fortran compiler and a C compiler.
To fix this we added a phase to the “custom-gcc” to delete executables
such as “gcc” that are also provided by the C compiler, such that
installing “gfortran” would not break the C compiler.
Still, it is currently not possible to use GCC with languages other than
C or C++. Installing “gcc-objc” along with the regular GCC, for
example, you won’t get a working compiler for Objective C as the default
GCC’s “gcc” binary does not know about the Objective C language. Even
setting COMPILER_PATH to point at the tools for the Objective C compiler
won’t fix this.
I propose this:
* enable all languages in GCC by default so that their “lang-spec.h”
headers are included. This does not mean we should build all language
frontends. We only want to ensure that the “gcc” won’t refuse to
compile something just because it doesn’t know about the language.
* when installing “gcc”, set COMPILER_PATH to use additional languages.
I don’t know if this is feasible or if there’s a different way to
achieve this. It may even be enough to patch GCC’s “gcc/Makefile.in”
such that “lang_specs_files” holds the names of all supported languages,
which will ensure that all available “lang-spec.h” files end up being
included.
If you have other ideas for fixing GCC for languages other than C and
C++ please do comment.
~~ Ricardo
next reply other threads:[~2016-05-19 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 8:20 Ricardo Wurmus [this message]
2016-05-19 13:10 ` enabling all supported languages in GCC Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eg8yihm9.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).