public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: David Pirotte <david@altosw.be>
Cc: kawa@sourceware.org
Subject: Re: kawa build from source fails - revision 8603
Date: Mon, 21 Sep 2015 15:55:00 -0000	[thread overview]
Message-ID: <56002845.6070309@bothner.com> (raw)
In-Reply-To: <20150921121330.0f21023b@capac>



On 09/21/2015 08:13 AM, David Pirotte wrote:
>
>> Looks like you're not neither OpenJDK or Java SE, but some other Java
>> implementation. Is that correct?  Looks like Eclipse-style error message, IIRC.
>>
>> Either that, or or you're using Java 5.
>> If so you may need to --with-java-source=5 as an extra configure flag.
>> However, I haven't tested that in a while.
>
> david@capac:/usr/local/src/kawa/svn 19 $ java -version
> java version "1.7.0_75"
> OpenJDK Runtime Environment (IcedTea 2.5.4) (7u75-2.5.4-2)
> OpenJDK 64-Bit Server VM (build 24.75-b04, mixed mode)

Strange.  I tried all of:

openjdk version "1.8.0_60"
OpenJDK Runtime Environment (build 1.8.0_60-b27)
OpenJDK 64-Bit Server VM (build 25.60-b23, mixed mode)

and

java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

and

java version "1.6.0_37"
Java(TM) SE Runtime Environment (build 1.6.0_37-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01, mixed mode)

They all compile the 'import javax.lang.model.element.*;'
without problem.

I don't have OpenJDK 1.7 (just Java SE 1.7) to try with,
but I wouldn't expect it to be missing javax.lang.model.element.
OTOH I vaguely remember there were some problems with OpenJDK 7.
I generally run Fedora, and in the past there were some problems when
using /usr/bin/javac, so I mostly used Java SE.  However, on Fedora 22
we have OpenJDK 1.8, which works much better.  (There are still
some test-suite discrepancies I haven't tracked down.)

So I suggest switching to one of OpenJDK 8, Java SE 7, or Java SE 8.
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2015-09-21 15:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21  5:00 David Pirotte
2015-09-21  5:51 ` Per Bothner
2015-09-21 15:13   ` David Pirotte
2015-09-21 15:55     ` Per Bothner [this message]
2015-09-21 16:14       ` Per Bothner
2015-09-21 18:26       ` David Pirotte
2015-09-21 18:37         ` Per Bothner
2015-09-21 18:48           ` David Pirotte
2015-09-21 19:14             ` Per Bothner
2015-09-21 19:28               ` David Pirotte
2015-09-21 19:36                 ` Felipe Bueno
2015-09-21 20:05                   ` Jamison Hope
2015-09-21 20:35                     ` David Pirotte
2015-09-21 20:59                       ` Andrea Bernardini
2015-09-21 21:32                         ` David Pirotte
2015-09-21 22:18                           ` Andrea Bernardini
2015-09-22  1:57                             ` David Pirotte
2015-09-22  3:01                               ` Per Bothner
2015-09-21 22:32                           ` Jamison Hope
2015-09-21 21:38                       ` Jamison Hope
2015-09-21  6:43 ` Per Bothner
2015-09-21 15:17   ` David Pirotte

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=56002845.6070309@bothner.com \
    --to=per@bothner.com \
    --cc=david@altosw.be \
    --cc=kawa@sourceware.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.
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).