From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: gcj: remove broken symlink and stump binaries.
Date: Sat, 2 May 2015 18:14:08 +0200 [thread overview]
Message-ID: <87h9rvx8hb.fsf@mango.localdomain> (raw)
In-Reply-To: <87pp6ly52e.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1500 bytes --]
Ludovic Courtès writes:
>> + (for-each delete-file
>> + (map (cut string-append out <>)
>> + '("/lib/jvm/jre/lib/amd64/libjawt.so"
>> + "/bin/c++"
>> + "/bin/cpp"
>> + "/bin/g++"
>> + "/bin/gcc"
>> + "/bin/gcc-ar"
>> + "/bin/gcc-nm"
>> + "/bin/gcc-ranlib"
>> + "/bin/x86_64-unknown-linux-gnu-c++"
>> + "/bin/x86_64-unknown-linux-gnu-g++"
>> + "/bin/x86_64-unknown-linux-gnu-gcc"
>> + "/bin/x86_64-unknown-linux-gnu-gcc-4.8.4"
>> + "/bin/x86_64-unknown-linux-gnu-gcc-ar"
>> + "/bin/x86_64-unknown-linux-gnu-gcc-nm"
>> + "/bin/x86_64-unknown-linux-gnu-gcc-ranlib"))))
>
> This is specific to x86_64-linux-gnu though. Wouldn’t it be better to
> use a white list instead, or maybe keep it a black list but use
> find-files and regexps?
Attached is a new patch using find-files and regular expressions. The
results look fine in the REPL, but I have not yet finished compiling the
gcj package (it takes a very long time on my machine).
~~ Ricardo
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-gcj-Remove-broken-symlink-and-conflicting-files.patch --]
[-- Type: text/x-patch, Size: 1409 bytes --]
From 86f2b4e7f182b5ea734eea4d72ef868b6a25f7eb Mon Sep 17 00:00:00 2001
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Date: Thu, 30 Apr 2015 17:11:39 +0200
Subject: [PATCH] gnu: gcj: Remove broken symlink and conflicting files.
* gnu/packages/gcc.scm (gcj)[arguments]: Add a build phase to remove a broken
symlink and generic stump binaries.
---
gnu/packages/gcc.scm | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/gcc.scm b/gnu/packages/gcc.scm
index e712e43..aa3e046 100644
--- a/gnu/packages/gcc.scm
+++ b/gnu/packages/gcc.scm
@@ -435,7 +435,18 @@ Go. It also includes runtime support libraries for these languages.")
(string-append jvm "/lib/tools.jar")))
(chmod target #o755)
#t))
- ,phases))))))
+ (alist-cons-after
+ 'install 'remove-broken-or-conflicting-files
+ (lambda _
+ (let ((out (assoc-ref %outputs "out")))
+ (for-each
+ delete-file
+ (append (find-files (string-append out "/lib/jvm/jre/lib")
+ "libjawt.so")
+ (find-files (string-append out "/bin")
+ ".*(c\\+\\+|cpp|g\\+\\+|gcc.*)"))))
+ #t)
+ ,phases)))))))
(define ecj-bootstrap-4.8
(origin
--
2.1.0
next prev parent reply other threads:[~2015-05-02 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 15:37 [PATCH] gnu: gcj: remove broken symlink and stump binaries Ricardo Wurmus
2015-04-30 16:05 ` Ludovic Courtès
2015-04-30 16:29 ` Ricardo Wurmus
2015-05-02 16:14 ` Ricardo Wurmus [this message]
2015-05-02 18:26 ` Ludovic Courtès
2015-05-02 19:09 ` Ricardo Wurmus
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=87h9rvx8hb.fsf@mango.localdomain \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=ludo@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).