From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13001] openjdk-bin replaces libfreetype.so from host-freetype
Date: Wed, 17 Jun 2020 18:13:26 +0000 [thread overview]
Message-ID: <bug-13001-163-lZvVu7yFaQ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13001-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13001
--- Comment #6 from Adam Duskett <aduskett@gmail.com> ---
Sorry for the delayed response, as this ticket is mine.
I would propose doing what we did with OpenJDK, which is installing
host-openjdk-bin to /usr/lib/jvm. This directory structure provides two
advantages:
1) The directory structure is consistent with how we handle the target OpenJDK.
2) I have been spending some time with OpenJDK and Buildroot as of late. Part
of what I have had to do was set up Maven with Buildroot, and in doing so I
found that the host-openjdk-bin install step does not copy the conf file from
the source directory to the host directory.
This lack of copying causes Maven to crash with the error "Can't read
cryptographic policy directory: unlimited."
After some research, I found that Maven looks for conf files in
$(JAVA_HOME)/conf, which Buildroot does not provide.
Maven also searched for $(JAVA_HOME)/bin and $(JAVA_HOME)/lib which do exist.
So there are two options to fix this issue:
Copy the conf directory to $(HOST_DIR), which would result in a
$(HOST_DIR)/conf directory.
OR
Follow the standard practice of installing the entire JVM to /usr/lib/jvm
I would propose the second option as it also looks nicer and allows us not to
have a $(HOST_DIR)/conf directory.
Yann, thoughts?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-06-17 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 16:38 [Buildroot] [Bug 13001] New: openjdk-bin replaces libfreetype.so from host-freetype bugzilla at busybox.net
2020-06-10 20:10 ` [Buildroot] [Bug 13001] " bugzilla at busybox.net
2020-06-11 13:29 ` bugzilla at busybox.net
2020-06-14 9:06 ` bugzilla at busybox.net
2020-06-15 13:09 ` bugzilla at busybox.net
2020-06-15 16:32 ` bugzilla at busybox.net
2020-06-15 20:08 ` bugzilla at busybox.net
2020-06-17 18:13 ` bugzilla at busybox.net [this message]
2020-06-17 22:02 ` bugzilla at busybox.net
2020-06-18 11:41 ` bugzilla at busybox.net
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=bug-13001-163-lZvVu7yFaQ@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.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