unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 49990@debbugs.gnu.org
Subject: bug#49990: [core-updates-frozen] Ant-bootstrap broken by classpath-bootstrap
Date: Wed, 01 Sep 2021 15:53:52 +0200	[thread overview]
Message-ID: <87y28g766n.fsf@gnu.org> (raw)
In-Reply-To: <20210901030255.27bfdd2d@tachikoma.lepiller.eu> (Julien Lepiller's message of "Wed, 1 Sep 2021 03:02:55 +0200")

[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]

Hi,

Julien Lepiller <julien@lepiller.eu> skribis:

> Le Wed, 01 Sep 2021 00:32:39 +0200,
> Ludovic Courtès <ludo@gnu.org> a écrit :
>
>> Hello!
>> 
>> As discussed on IRC, I had a semi-victory with the attached patch,
>> which works around a miscompilation issue in
>> ‘Java_java_io_VMFile_isFile’.
>
> another possibility I tested was to disable optimization by adding
> CFLAGS=-O0 to the configure-flags. This creates an unoptimized version,
> but that should be fine since it's only for the bootstrap. However, I
> noticed that my debug messages from my previous attempt were still
> visible when compiling icedtea. I don't know what happened, since
> there is at least another classpath version before it.
>
>> 
>> Unfortunately, with this patch applied, ‘ant-bootstrap’ fails to build
>> with:

The root cause is that, even tough we’re passing “-classpath
build/classes:src”, only the first element of the classpath is
searched.  If we pass “-classpath foobar:build/classes”, then Main.class
is not found.  That suggests another problem with ‘stat’-related
functions.

>> Ideas?  What a wonderful puzzle we have!  :-)

> Even more wonderful is the fact I do not get this error at all when
> using CFLAGS=-O0, but I do with your patch. I didn't have any issue
> either with my previous attempt with debugging. Could there be other
> problems with optimizations in classpath?

Hmm -O0 is brute-force.  It doesn’t work for me though if I also remove
the ‘remove-call-to-free’ phase, though.

I also tried this Classpath patch:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 392 bytes --]

diff --git a/include/jni_md.h b/include/jni_md.h
index 989dbfe..f7867d7 100644
--- a/include/jni_md.h
+++ b/include/jni_md.h
@@ -32,7 +32,7 @@ executable file might be covered by the GNU General Public License. */
 #define JNIEXPORT
 #define JNIIMPORT
 
-typedef unsigned char jboolean;
+typedef int jboolean;
 typedef signed char jbyte;
 typedef unsigned short jchar;
 typedef short jshort;

[-- Attachment #3: Type: text/plain, Size: 103 bytes --]


It seems to have the same effect as my initial patch.

I’m lacking inspiration now!

Ludo’.

  reply	other threads:[~2021-09-01 13:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 21:38 bug#49990: [core-updates-frozen] Ant-bootstrap broken by classpath-bootstrap Julien Lepiller
2021-08-30 11:51 ` Efraim Flashner
2021-08-31 22:32   ` Ludovic Courtès
2021-09-01  1:02     ` Julien Lepiller
2021-09-01 13:53       ` Ludovic Courtès [this message]
2021-09-02 14:15         ` Maxime Devos
2021-09-02 14:57           ` Julien Lepiller
2021-09-03 10:11             ` Ludovic Courtès
2021-09-02 22:27 ` bug#49990: [PATCH] gnu: Fix classpath-bootstrap compilation muradm
2021-09-02 22:38   ` muradm

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=87y28g766n.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=49990@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    /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).