Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Richard Leitner <richard.leitner@skidata.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-java][PATCH 4/4] openjdk-8: add recipes for openjdk-8 and openjre-8
Date: Thu, 29 Oct 2015 08:41:33 +0100	[thread overview]
Message-ID: <5631CDAD.7030703@skidata.com> (raw)
In-Reply-To: <D1946B41-2BFF-49FA-A4C7-19A2A1D6C731@gmail.com>

On 10/28/2015 07:01 PM, Jens Rehsack wrote:
> This adds openjdk-8 for native and target builds and allows a stripped
> openjre-8 being built as well instead of trying to cherry-pick jre
> components from jdk-image.
> 
> The recipes allow building openjdk-8 with or without:
> * x11
> * cups
> * alsa/pulseaudio
> and let packager enable unlimited-crypto, if desired.
> 
> Since there can be only one PROVIDES for virtual/java-native and virtual/javac-native,
> move the provides to openjdk-8-native (I think everyone agrees it's a better
> choice than ecj-bootstrap-native).
> 
> Plus: Applying a fix from openjdk-9 repository which fixes build issues using gcc5
> 
> Signed-off-by: Jens Rehsack <sno@netbsd.org>
> ---
>  README                                             |   13 +-
>  recipes-core/cacao/cacao_1.6.1.bb                  |    2 +-
>  recipes-core/ecj/ecj-bootstrap-native.bb           |    2 -
>  recipes-core/openjdk/openjdk-8-72b00/LICENSE       |  347 +++
>  .../dont-expect-fqpn-for-make.patch                |   18 +
>  .../openjdk-8-72b00/filter-aclocal-copy-too.patch  |   11 +
>  recipes-core/openjdk/openjdk-8-72b00/jvm.cfg       |   41 +
>  .../openjdk8-find-compiler-fix-env-respect.patch   |  140 +
>  .../openjdk-8-72b00/openjdk8-fix-shark-build.patch |  453 ++++
>  .../openjdk8-fix-shark-stdc++11.patch              | 2730 ++++++++++++++++++++
>  .../openjdk8-no-genx11-in-headless.patch           |   17 +
>  .../openjdk-8-72b00/openjdk8-no-unused-deps.patch  |   94 +
>  ...o-in-favour-of-openembedded-package-split.patch |  120 +
>  .../openjdk8-restrict-to-staging-dir.patch         |   11 +
>  ..._than_returning_address_of_local_variable.patch |   23 +
>  .../remove-shell-variables-from-autoheader.patch   |   31 +
>  recipes-core/openjdk/openjdk-8-common.inc          |  229 ++
>  recipes-core/openjdk/openjdk-8-cross.inc           |  202 ++
>  recipes-core/openjdk/openjdk-8-native.inc          |   63 +
>  recipes-core/openjdk/openjdk-8-native_72b00.bb     |   16 +
>  recipes-core/openjdk/openjdk-8-release-72b00.inc   |   89 +
>  recipes-core/openjdk/openjdk-8_72b00.bb            |   36 +
>  recipes-core/openjdk/openjre-8_72b00.bb            |   30 +
>  23 files changed, 4706 insertions(+), 12 deletions(-)
>  create mode 100644 recipes-core/openjdk/openjdk-8-72b00/LICENSE
>  create mode 100644 recipes-core/openjdk/openjdk-8-72b00/dont-expect-fqpn-for-make.patch
>  create mode 100644 recipes-core/openjdk/openjdk-8-72b00/filter-aclocal-copy-too.patch
>  create mode 100644 recipes-core/openjdk/openjdk-8-72b00/jvm.cfg
>  create mode 100644 recipes-core/openjdk/openjdk-8-72b00/openjdk8-find-compiler-fix-env-respect.patch
>  create mode 100644 recipes-core/openjdk/openjdk-8-72b00/openjdk8-fix-shark-build.patch
>  create mode 100644 recipes-core/openjdk/openjdk-8-72b00/openjdk8-fix-shark-stdc++11.patch
>  create mode 100644 recipes-core/openjdk/openjdk-8-72b00/openjdk8-no-genx11-in-headless.patch
>  create mode 100644 recipes-core/openjdk/openjdk-8-72b00/openjdk8-no-unused-deps.patch
>  create mode 100644 recipes-core/openjdk/openjdk-8-72b00/openjdk8-prevent-debuginfo-in-favour-of-openembedded-package-split.patch
>  create mode 100644 recipes-core/openjdk/openjdk-8-72b00/openjdk8-restrict-to-staging-dir.patch
>  create mode 100644 recipes-core/openjdk/openjdk-8-72b00/openjdk8-use_builtin_frame_address_0_rather_than_returning_address_of_local_variable.patch
>  create mode 100644 recipes-core/openjdk/openjdk-8-72b00/remove-shell-variables-from-autoheader.patch

IMHO a version independent patches directory like for openjdk-7 would
also be good here.

To cite Otavio:
We could rename the patches directory for openjdk-7 and avoid the
version number on it. This would make easier for upgrades and to see
the diff between the patches.

>  create mode 100644 recipes-core/openjdk/openjdk-8-common.inc
>  create mode 100644 recipes-core/openjdk/openjdk-8-cross.inc
>  create mode 100644 recipes-core/openjdk/openjdk-8-native.inc
>  create mode 100644 recipes-core/openjdk/openjdk-8-native_72b00.bb
>  create mode 100644 recipes-core/openjdk/openjdk-8-release-72b00.inc
>  create mode 100644 recipes-core/openjdk/openjdk-8_72b00.bb
>  create mode 100644 recipes-core/openjdk/openjre-8_72b00.bb

Furthermore I had problems building OpenJDK-7 with this patch applied.
But I will verify that again and come back to you!

best regards,
Richard L


  parent reply	other threads:[~2015-10-29  7:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 18:01 [meta-java][PATCH 4/4] openjdk-8: add recipes for openjdk-8 and openjre-8 Jens Rehsack
2015-10-28 19:34 ` Dan McGregor
2015-10-28 19:59   ` Jens Rehsack
2015-10-29  7:41 ` Richard Leitner [this message]
2015-10-29  9:22   ` Jens Rehsack
2015-10-29 10:46     ` Otavio Salvador
2015-10-29 11:24       ` Jens Rehsack
2015-10-29 11:54         ` Richard Leitner
2015-10-29 12:08           ` Jens Rehsack
2015-10-29 15:51             ` Richard Leitner
2015-10-29 12:24           ` Otavio Salvador
2015-10-29 15:49             ` Richard Leitner
2015-10-29 16:03               ` Otavio Salvador
2015-10-29 18:51                 ` Richard Leitner
2015-10-29 18:59                   ` Otavio Salvador
2015-11-03 10:25                     ` Jens Rehsack
  -- strict thread matches above, loose matches on Subject: below --
2015-10-27 20:31 Jens Rehsack
2015-10-30  9:09 ` Kaaria, Erkka
2015-10-30 11:46   ` Jens Rehsack
2015-10-30 12:41     ` Kaaria, Erkka
2015-10-30 12:59       ` Otavio Salvador
2015-10-30 13:26         ` Jens Rehsack
2015-10-30 13:23       ` Jens Rehsack

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=5631CDAD.7030703@skidata.com \
    --to=richard.leitner@skidata.com \
    --cc=openembedded-devel@lists.openembedded.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