unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: 03/03: gnu: clang-from-llvm: Clean up share/clang folder.
Date: Tue, 27 Nov 2018 18:35:15 -0500	[thread overview]
Message-ID: <874lc29jqp.fsf@netris.org> (raw)
In-Reply-To: <20181126135351.C5B4420427@vcs0.savannah.gnu.org> (guix-commits's message of "Mon, 26 Nov 2018 08:53:51 -0500 (EST)")

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

--8<---------------cut here---------------start------------->8---
phase `install' succeeded after 4.0 seconds
starting phase `install-clean-up-/share/clang'
Backtrace:
           7 (primitive-load "/gnu/store/9x14py3rqc0zlk131957r7a8lda…")
In ice-9/eval.scm:
   191:35  6 (_ _)
In srfi/srfi-1.scm:
    640:9  5 (for-each #<procedure c60ca0 at /gnu/store/qzsljkcllc0…> …)
In /gnu/store/qzsljkcllc01dmdq9z0yrqri3ajam3vp-module-import/guix/build/gnu-build-system.scm:
   799:31  4 (_ _)
In ice-9/eval.scm:
    619:8  3 (_ #(#(#<directory (guile-user) 7cc140>) (("out" . #))))
In ice-9/boot-9.scm:
    142:2  2 (dynamic-wind #<procedure e831e0 at ice-9/eval.scm:330…> …)
In ice-9/eval.scm:
    619:8  1 (_ #(#(#<directory (guile-user) 7cc140> "/gnu/store/…")))
In unknown file:
           0 (delete-file "clang-rename.el")

ERROR: In procedure delete-file:
In procedure delete-file: No such file or directory
builder for `/gnu/store/vc33s8dicyhzhysm90x2wli3n7q4y3si-clang-3.9.1.drv' failed with exit code 1
@ build-failed /gnu/store/vc33s8dicyhzhysm90x2wli3n7q4y3si-clang-3.9.1.drv - 1 builder for `/gnu/store/vc33s8dicyhzhysm90x2wli3n7q4y3si-clang-3.9.1.drv' failed with exit code 1
--8<---------------cut here---------------end--------------->8---

       reply	other threads:[~2018-11-27 23:36 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   ` Mark H Weaver [this message]
2018-11-28  9:32     ` 03/03: gnu: clang-from-llvm: Clean up share/clang folder 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

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=874lc29jqp.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).