From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa@sourceware.org
Subject: Re: gnu.bytecode.ParameterizedType does not implement Externalizable
Date: Sat, 15 Oct 2022 22:11:00 +0200 [thread overview]
Message-ID: <CAMFYt2Y98QqPqOSV+c46xnkRhnhwa5iv47Mx6CkHui9s4DhcyQ@mail.gmail.com> (raw)
In-Reply-To: <9ca0f114-ec5e-b932-f4b2-8d9323e76cb6@bothner.com>
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
Thanks.
This seems to resolve the issue (at least as long as the compilation
process is concerned) - now the process issues some warnings and terminates
normally, and the .class files appear in the desired directory.
sob., 15 paź 2022, 19:08 użytkownik Per Bothner <per@bothner.com> napisał:
> Please try the attached patch.
> I haven't tested it, except to verify that it compiles.
> --
> --Per Bothner
> per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2022-10-15 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 15:55 Panicz Maciej Godek
2022-10-15 17:07 ` Per Bothner
2022-10-15 20:11 ` Panicz Maciej Godek [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMFYt2Y98QqPqOSV+c46xnkRhnhwa5iv47Mx6CkHui9s4DhcyQ@mail.gmail.com \
--to=godek.maciek@gmail.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.com \
/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.
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).