public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Bill Chatfield via java" <java@gcc.gnu.org>
To: "'Andrew Haley'" <aph@redhat.com>,	<bill.chatfield@yahoo.com>,
	"'mohan NMH'" <mohan.nmh2@gmail.com>
Cc: <java@gcc.gnu.org>
Subject: RE: Fwd: gcj can not import packages
Date: Tue, 17 Jan 2017 15:21:00 -0000	[thread overview]
Message-ID: <5a2e01d270d5$52a22a30$f7e67e90$@yahoo.com> (raw)
In-Reply-To: <18313a22-8b60-58c4-7ba4-4c3fc8932990@redhat.com>

OK, then I'm going to fork it to github and someday gcj is going to overtake gcc and g++. Haha. :-) Actually, I'll be lucky if I can get it to compile. My previous attempts have all failed. I can get a working gcc and g++, but gcj never succeeds for me. It takes several days to get through just one iteration of the preliminary gcc build on my PowerBook G4 before it fails. I'd probably be better off to run a cross compile on my i5 Fedora machine to get a version for my PowerBook G4. I could probably pull the old Fedora source rpm as a starting point to get the right configuration parameters. I think it's the missing gcj dependencies that always cause the failures. I've never gotten a successful compile of gcj on Windows either. I've tried using other people's configure parameters, but they're always for a different version of gcc/gcj than what I'm trying to compile and they don't work.

-----Original Message-----
From: Andrew Haley [mailto:aph@redhat.com] 
Sent: Tuesday, January 17, 2017 4:59 AM
To: bill.chatfield@yahoo.com; 'mohan NMH' <mohan.nmh2@gmail.com>
Cc: java@gcc.gnu.org
Subject: Re: Fwd: gcj can not import packages

On 16/01/17 17:40, Bill Chatfield via java wrote:
> 
> Also, I feel that gcj was a great achievement on the part of the FSF 
> and the open source community. It's nothing to be ashamed of. It shows 
> the resourcefulness and ingenuity of the community.

Well, yeah, but it'd take a lot of work to maintain GCJ.  And unmaintained software is a major liability.  For anyone who needs GCJ, its old sources are not going to disappear.

Andrew.

      reply	other threads:[~2017-01-17 15:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANV4OqjehvrZUaMGbwn0Gu3KsesTy7aWVhY9cPETpnqwf_Zo0A@mail.gmail.com>
2016-11-09 11:29 ` mohan NMH
2016-11-09 12:26   ` Andrew Haley
2016-11-09 12:49     ` mohan NMH
2016-11-09 13:29       ` Andrew Haley
2017-01-16 17:41         ` Bill Chatfield via java
2017-01-16 20:10           ` Ricardo Wurmus
2017-01-16 22:58             ` Bill Chatfield via java
2017-01-16 23:24               ` Anthony Green
2017-01-17  9:56               ` Andrew Haley
2017-01-18 20:29                 ` Ricardo Wurmus
2017-01-18 20:40                   ` Matthias Klose
2017-01-18 20:59                     ` Ricardo Wurmus
2017-01-19  9:59                       ` Andrew Haley
     [not found]                         ` <CAFXTvn525N1D_EOuCAWXSJugCpZCZCkc5GfuhNJ1nPoDK0DAoQ@mail.gmail.com>
2017-05-17 20:26                           ` Ricardo Wurmus
2017-01-17  9:58           ` Andrew Haley
2017-01-17 15:21             ` Bill Chatfield via java [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='5a2e01d270d5$52a22a30$f7e67e90$@yahoo.com' \
    --to=java@gcc.gnu.org \
    --cc=aph@redhat.com \
    --cc=bill.chatfield@yahoo.com \
    --cc=mohan.nmh2@gmail.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).