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 19:14:00 -0000	[thread overview]
Message-ID: <560056F2.5010006@bothner.com> (raw)
In-Reply-To: <20150921154745.263d90d5@capac>

On 09/21/2015 11:47 AM, David Pirotte wrote:

>>> 	david@capac:/usr/local/src/kawa/svn 26 $ java -version
>>> 	java version "1.7.0_85"
>>> 	OpenJDK Runtime Environment (IcedTea 2.6.1) (7u85-2.6.1-3)
>>> 	OpenJDK 64-Bit Server VM (build 24.85-b03, mixed mode)
>>>
>>> It still fails:
>>
>> The above is not a version string from one of OpenJDK 8, Java SE 7, or Java SE 8.
>> (It is OpenJDK 7.)
>
> Sorry, I don't understand what you're are trying to tell me, neither why neither what
> to do to make it compile.

Your installed Java implementation is not supported.

Note that OpenJDK (the open-source project) is not the same as Java SE / JDK
(the bundle released by Oracle).  The latter is based on the former, but there
are some differences.  The differences are bigger for Java 7, but still there
for Java 8.  (For example OpenJDK 8 does not include JavaFX.)

The easiest fix is to grab and install Java SE 8 aka JDK 8 from here:

http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

Just untar the download file somewhere convenient, and have your PATH
point to the bin directory (containing javac).

Or upgrade to OpenJDK 8 - though of course this depends on your OS:

http://openjdk.java.net/install/

>My understanding is if configure pass, compile must pass,

Where did you get that from?  configure is not required or expected
to guard against every possible bad compiler or environment.

True, some configure scripts do check for known bad compilers or other
known problems, and that's a good thing to do.  Perhaps Kawa should do
that - though not many people have run into this problem, to my knowledge.

> that's my experience, maybe you should improve your configure.ac file

Patches welcome.
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2015-09-21 19:14 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
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 [this message]
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=560056F2.5010006@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).