From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: guix-devel <guix-devel@gnu.org>
Subject: java: How to patch a jar-sources
Date: Mon, 15 Apr 2019 08:02:48 +0200 [thread overview]
Message-ID: <20190415080248.679c6749@alma-ubu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2544 bytes --]
Hi Guix,
I have a problem combining ".jar" sources with patches.
Here is my sources definition:
(define-public java-ecj
(package (inherit java-ecj-3)
(version "4.6.3")
(source (origin
(method url-fetch)
(uri (string-append "http://archive.eclipse.org/eclipse/downloads/drops4/R-"
version
"-201703010400/ecjsrc-"
version
".jar"))
(patches
(search-patches "java-ecj-buildxml-fix-manifest.patch"
"java-ecj-include-props.patch"))
(sha256
(base32
"11cfgsdgznja1pvlxkjbqykxd7pcd5655vkm7s44xmahmap15gpl"))))
[...]
This worked pretty well until I added the patches:
./pre-inst-env guix build java-ecj -K
;;; note: source file /home/bjoern/guix/wt/qt/gnu/packages/java.scm
;;; newer than compiled /home/bjoern/guix/wt/qt/gnu/packages/java.go
building /gnu/store/wppz7bix1r4mhddjz6k4alfnxkm919gq-ecjsrc-4.6.3.tar.xz.drv...
/gnu/store/bl3pxxj6frg0dww8pj5dvh2d1akwvj47-tar-1.30/bin/tar: This does not look like a tar archive
/gnu/store/bl3pxxj6frg0dww8pj5dvh2d1akwvj47-tar-1.30/bin/tar: Skipping to next header
/gnu/store/bl3pxxj6frg0dww8pj5dvh2d1akwvj47-tar-1.30/bin/tar: Exiting with failure status due to previous errors
Backtrace:
2 (primitive-load "/gnu/store/lg0dlhwf4mfz82697bvfdwi7d86?")
In ice-9/eval.scm:
619:8 1 (_ #f)
In guix/build/utils.scm:
616:6 0 (invoke _ . _)
guix/build/utils.scm:616:6: In procedure invoke:
Throw to key `srfi-34' with args `(#<condition &invoke-error [program: "/gnu/store/bl3pxxj6frg0dww8pj5dvh2d1akwvj47-tar-1.30/bin/tar" arguments: ("xvf" "/gnu/store/1vf8lxrnkgxw0zl8i2m8rf7jxcjg9f5b-ecjsrc-4.6.3.jar") exit-status: 2 term-signal: #f stop-signal: #f] 56dd40>)'.
note: keeping build directory `/tmp/guix-build-ecjsrc-4.6.3.tar.xz.drv-1'
builder for `/gnu/store/wppz7bix1r4mhddjz6k4alfnxkm919gq-ecjsrc-4.6.3.tar.xz.drv' failed with exit code 1
build of /gnu/store/wppz7bix1r4mhddjz6k4alfnxkm919gq-ecjsrc-4.6.3.tar.xz.drv failed
It looks like guix now wants to extract the jar-sources with "tar", no
longer with "jar". How can I tell Guix this is a jar-file to extract
from? Do I need to do that manually in a snippet? Any examples?
Thanks,
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2019-04-15 6:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 6:02 Björn Höfling [this message]
2019-04-15 12:26 ` java: How to patch a jar-sources Gábor Boskovits
2019-04-15 15:11 ` Björn Höfling
2019-04-15 15:18 ` Danny Milosavljevic
2019-04-15 15:19 ` Danny Milosavljevic
2019-04-15 23:49 ` Björn Höfling
2019-04-16 9:50 ` Gábor Boskovits
2019-04-16 18:00 ` Björn Höfling
2019-04-18 5:09 ` Björn Höfling
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=20190415080248.679c6749@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--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).