From: Carl Dong <contact@carldong.me>
To: Marius Bakke <mbakke@fastmail.com>
Cc: "37999@debbugs.gnu.org" <37999@debbugs.gnu.org>
Subject: bug#37999: clang fails to pickup/supply startfiles to ld
Date: Mon, 04 Nov 2019 20:31:24 +0000 [thread overview]
Message-ID: <Z9c3XBmWFNEfNxmMSZjO3foLe7KdBIdCUcjN9umVBd8hXN6-0gbprFZgXw-w_00Cj_-wQS4-gU0v8oh-s-mLW8esjnciZPAbCZQFgENRq_U=@carldong.me> (raw)
In-Reply-To: <8736f8plpf.fsf@devup.no>
Thank you so much Mathieu for the patch!
Marius: I believe this will only cause a rebuild for clang and not llvm, which means that it only affects ~30 packages. Perhaps this can go in master? Would love to know your thoughts.
Cheers,
Carl Dong
contact@carldong.me
"I fight for the users"
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, October 31, 2019 10:57 PM, Marius Bakke <mbakke@fastmail.com> wrote:
> Mathieu Othacehe m.othacehe@gmail.com writes:
>
> > From f126146880e3904f39728313dfc10288b51fc23a Mon Sep 17 00:00:00 2001
> > From: Mathieu Othacehe m.othacehe@gmail.com
> > Date: Thu, 31 Oct 2019 15:05:54 +0100
> > Subject: [PATCH] gnu: clang-from-llvm: Fix set-glibc-file-names phase.
> >
> > - gnu/packages/llvm.scm (clang-from-llvm)[arguments]: Turn case on major
> > version into a cond, so that newer versions of clang have the same behaviour as
> > version 6 and 7.
> >
>
> LGTM. It will have to wait for the next 'staging' window, though.
next prev parent reply other threads:[~2019-11-04 20:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 20:48 bug#37999: clang fails to pickup/supply startfiles to ld Carl Dong
2019-10-31 7:55 ` Mathieu Othacehe
2019-10-31 13:16 ` Bengt Richter
2019-10-31 14:11 ` Mathieu Othacehe
2019-10-31 22:57 ` Marius Bakke
2019-11-04 20:31 ` Carl Dong [this message]
2019-11-05 7:55 ` Mathieu Othacehe
2019-11-07 16:23 ` Danny Milosavljevic
2019-11-16 14:31 ` Mathieu Othacehe
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='Z9c3XBmWFNEfNxmMSZjO3foLe7KdBIdCUcjN9umVBd8hXN6-0gbprFZgXw-w_00Cj_-wQS4-gU0v8oh-s-mLW8esjnciZPAbCZQFgENRq_U=@carldong.me' \
--to=contact@carldong.me \
--cc=37999@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/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).