public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "classpath@gnu.org" <classpath@gnu.org>,
	"Mark Wielaard" <mark@klomp.org>,
	"Andrew Hughes" <gnu.andrew@redhat.com>,
	Andïï <gnu_andrew@member.fsf.org>,
	Andïï <gnu.andrew.rocks@gmail.com>,
	"Andrew Haley" <aph@redhat.com>,
	"Mario Torre" <neugens@redhat.com>,
	java@gcc.gnu.org
Subject: Re: Status of GNU Classpath
Date: Mon, 6 Feb 2023 17:16:30 +0100	[thread overview]
Message-ID: <CABDcavayzQpzt=8+CJir4bKUe_LORXGASEN18-RTzyimCVrfhA@mail.gmail.com> (raw)
In-Reply-To: <87357i7tuf.fsf@elephly.net>

Hi Ricardo,

> > I can see that development halted around 2016 (from the commit logs of
> > the official git repo), but would like to know if someone else is
> > still using GNU Classpath.
>
> GNU Guix is using GNU Classpath in the bootstrap path from C to modern JDKs.

Thanks a lot for your answer.

I had a look at Guix and specifically this comment:
https://github.com/ecbrown/guix/blob/master/gnu/packages/java.scm#L92

I see you use GNU Classpath as a bootstrap toolchain in order to build
OpenJDK. In that process you need to build 0.93, then 0.99, then
finally the "development" version (basically 0.99 plus a few
additional commits).

I understand that the above already does the job, and that GNU
Classpath is not used in Guix anymore once OpenJDK is built. Is this
correct?

Thanks,

Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

  reply	other threads:[~2023-02-06 16:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABDcavY1sfVXs=zhF3fB+LS+HbszaDzs4KUzbkryFyz13ngtwQ@mail.gmail.com>
2023-02-06 12:55 ` Guillermo Rodriguez Garcia
2023-02-06 14:25   ` Ricardo Wurmus
2023-02-06 16:16     ` Guillermo Rodriguez Garcia [this message]
2023-02-08 10:42       ` Ricardo Wurmus
2023-02-08 15:55         ` Guillermo Rodriguez Garcia
2023-02-10 19:08           ` Ricardo Wurmus
2023-02-07 10:34     ` Andrew Haley
2023-02-07 10:55       ` Mark Wielaard
2023-02-07 10:47   ` Mark Wielaard
2023-02-07 13:00     ` Guillermo Rodriguez Garcia
2023-09-13 10:06       ` Guillermo Rodriguez Garcia
2023-09-14  8:15         ` Mark Wielaard

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='CABDcavayzQpzt=8+CJir4bKUe_LORXGASEN18-RTzyimCVrfhA@mail.gmail.com' \
    --to=guille.rodriguez@gmail.com \
    --cc=aph@redhat.com \
    --cc=classpath@gnu.org \
    --cc=gnu.andrew.rocks@gmail.com \
    --cc=gnu.andrew@redhat.com \
    --cc=gnu_andrew@member.fsf.org \
    --cc=java@gcc.gnu.org \
    --cc=mark@klomp.org \
    --cc=neugens@redhat.com \
    --cc=rekado@elephly.net \
    /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).