From: ludo@gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: 03/03: gnu: clang-from-llvm: Clean up share/clang folder.
Date: Wed, 28 Nov 2018 14:23:48 +0100 [thread overview]
Message-ID: <87tvk149p7.fsf@gnu.org> (raw)
In-Reply-To: <20181128093247.GA28059@macbook41> (Efraim Flashner's message of "Wed, 28 Nov 2018 11:32:47 +0200")
Hello all,
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Tue, Nov 27, 2018 at 06:35:15PM -0500, Mark H Weaver wrote:
>> Hi Pierre,
>>
>> guix-commits@gnu.org writes:
>>
>> > ambrevar pushed a commit to branch master
>> > in repository guix.
>> >
>> > commit 1c7372a5aadea84165376a4b8e2664b67a663c56
>> > Author: Pierre Neidhardt <mail@ambrevar.xyz>
>> > Date: Mon Nov 26 14:51:40 2018 +0100
>> >
>> > gnu: clang-from-llvm: Clean up share/clang folder.
>> >
>> > * gnu/packages/llvm.scm (clang-from-llvm): Remove useless files, install completion.
>>
>> I guess you only tested this for clang@6.0.1. It broke the builds for
>> _all_ other versions of clang.
>>
>> https://hydra.gnu.org/eval/110341?filter=clang#tabs-now-fail
>>
>> For example, see below for the tail of the build log for clang-3.9.1 on
>> x86_64-linux.
>>
>> Regards,
>> Mark
>>
>
> I have a fix for this test-building clang@3.8 on my machine. I've
> wrapped the delete-file calls in "(when file-exists?" and will push if
> it builds with no problems.
Yes, please do! We can’t let Clang broken for this long.
Thanks,
Ludo’.
prev parent reply other threads:[~2018-11-28 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181126135350.20543.84585@vcs0.savannah.gnu.org>
[not found] ` <20181126135351.C5B4420427@vcs0.savannah.gnu.org>
2018-11-27 23:35 ` 03/03: gnu: clang-from-llvm: Clean up share/clang folder Mark H Weaver
2018-11-28 9:32 ` Efraim Flashner
2018-11-28 9:52 ` Pierre Neidhardt
2018-11-28 10:23 ` Pierre Neidhardt
2018-11-28 10:54 ` Efraim Flashner
2018-11-28 12:43 ` Pierre Neidhardt
2018-11-28 13:23 ` Ludovic Courtès [this message]
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=87tvk149p7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=efraim@flashner.co.il \
--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).