From: Attila Lendvai <attila.lendvai@gmail.com>
To: 64929@debbugs.gnu.org
Cc: Attila Lendvai <attila@lendvai.name>
Subject: [bug#64929] [PATCH] gnu: gcc-toolchain: Create a 'bin/cc' symlink.
Date: Sat, 29 Jul 2023 13:50:29 +0200 [thread overview]
Message-ID: <dd5d375b64b71dd138fb37fc1714628f029e85f3.1690631428.git.attila@lendvai.name> (raw)
There are many projects that don't have a configure script that finds gcc.
Also makes it more symmetric with the clang-toolchain, that also does this.
* gnu/packages/commencement.scm (make-gcc-toolchain): Create the symlink.
---
i'm not sure what was the conclusion about this. clang-toolchain does
create a cc symlink, so i have mirrored what clang-toolchain does into
gcc-toolchain.
i thought i'll send this patch lying in my kludges branch, and
offer it either for rejection or inclusion, as you see fit.
gnu/packages/commencement.scm | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/gnu/packages/commencement.scm b/gnu/packages/commencement.scm
index fe6f025257..fceda97ad5 100644
--- a/gnu/packages/commencement.scm
+++ b/gnu/packages/commencement.scm
@@ -3554,6 +3554,12 @@ (define* (make-gcc-toolchain gcc
((_ . directory) directory))
%build-inputs))
+ ;; Create 'cc' so that one can use it as a drop-in
+ ;; replacement for the default tool chain and have
+ ;; configure scripts find the compiler. Note that
+ ;; 'c++' is already present, no need to symlink it.
+ (symlink "gcc" (string-append out "/bin/cc"))
+
(union-build (assoc-ref %outputs "debug")
(list (assoc-ref %build-inputs
"libc-debug")))
base-commit: e43cbeafd1b632f39b08b3644af5230d5350a656
prerequisite-patch-id: 6793c8ad24215c5f14ce71a4741fff5f6ccd7eeb
prerequisite-patch-id: 3a8dd737d11f37987641af9bc7f512a0bb1a1591
--
2.40.1
next reply other threads:[~2023-07-29 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 11:50 Attila Lendvai [this message]
2023-08-21 13:40 ` [bug#64929] [PATCH] gnu: gcc-toolchain: Create a 'bin/cc' symlink Maxime Devos
2023-08-21 14:30 ` Attila Lendvai
2023-08-21 15:08 ` Maxime Devos
2024-02-28 20:59 ` John Kehayias via Guix-patches via
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=dd5d375b64b71dd138fb37fc1714628f029e85f3.1690631428.git.attila@lendvai.name \
--to=attila.lendvai@gmail.com \
--cc=64929@debbugs.gnu.org \
--cc=attila@lendvai.name \
/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).