From: Ricardo Wurmus <rekado@elephly.net>
To: cmmarusich@gmail.com
Cc: guix-devel@gnu.org, 36685@debbugs.gnu.org
Subject: Re: bug#36685: ant-bootstrap fails on core-updates (409 dependents)
Date: Thu, 18 Jul 2019 12:51:23 +0200 [thread overview]
Message-ID: <87r26nfwes.fsf@elephly.net> (raw)
In-Reply-To: <871ryogu6j.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> I have confirmed that this is the problem by replacing “while
>> (VMFile.exists(file.path))” with “while (false)”. The build doesn’t
>> fully complete then either, but it gets past the compilation of the Ant
>> source files. This clears JamVM and Jikes.
>
> It doesn’t.
>
> VMFile.exists always returns “true”, no matter what. The C part is
> fine, but the Java part is not, so I suspected the JVM to be at fault.
>
> I managed to build ant-bootstrap successfully with this patch: […]
Here’s a shorter patch:
--8<---------------cut here---------------start------------->8---
diff --git a/gnu/packages/java.scm b/gnu/packages/java.scm
index 403c446a82..bd98784232 100644
--- a/gnu/packages/java.scm
+++ b/gnu/packages/java.scm
@@ -152,6 +152,13 @@ and binary format defined in The Java Virtual Machine Specification.")
"--disable-gjdoc")
#:phases
(modify-phases %standard-phases
+ (add-after 'unpack 'foo
+ (lambda _
+ (substitute* "native/jni/java-io/java_io_VMFile.c"
+ (("result = cpio_isFileExists.*" m)
+ (string-append m "
+//Without a long comment the Java side will return \"true\" on x86_64 all the time.")))
+ #t))
(add-after 'install 'install-data
(lambda _ (invoke "make" "install-data"))))))
(native-inputs
--8<---------------cut here---------------end--------------->8---
This only adds a comment. If the comment is too short it won’t work.
I suspected some misguided optimizations, so I built jamvm-1-bootstrap
and classpath-bootstrap with -O0, -O1, and I disabled stripping of
binaries, but to no avail.
Any ideas?
--
Ricardo
next parent reply other threads:[~2019-07-18 10:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8736j61n57.fsf@gmail.com>
[not found] ` <87o91ugdot.fsf@elephly.net>
[not found] ` <87ftn5gjzw.fsf@elephly.net>
[not found] ` <871ryogu6j.fsf@elephly.net>
2019-07-18 10:51 ` Ricardo Wurmus [this message]
2019-07-18 11:09 ` bug#36685: ant-bootstrap fails on core-updates (409 dependents) Efraim Flashner
2019-07-21 17:44 ` Ricardo Wurmus
2019-07-19 8:09 ` Ricardo Wurmus
2019-07-19 12:37 ` Gábor Boskovits
2019-07-19 12:56 ` Ricardo Wurmus
2019-07-19 16:30 ` Ricardo Wurmus
2019-07-20 8:42 ` Ricardo Wurmus
2019-07-20 9:06 ` Julien Lepiller
2019-07-20 21:07 ` Ricardo Wurmus
2019-07-21 11:29 ` Ricardo Wurmus
2019-07-21 15:57 ` Gábor Boskovits
2019-07-24 21:07 ` Ricardo Wurmus
2019-09-06 13:40 ` Ricardo Wurmus
2019-09-06 13:41 ` Gábor Boskovits
2019-09-07 14:28 ` Ricardo Wurmus
2019-09-07 15:01 ` Julien Lepiller
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=87r26nfwes.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=36685@debbugs.gnu.org \
--cc=cmmarusich@gmail.com \
--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).