Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: openjdk11: libjvm.so inside java.base.jmod isn't stripped
Date: Thu, 21 Apr 2022 00:17:29 +0200	[thread overview]
Message-ID: <20220420221729.PtbL2QoolV-blJVL2AVVwovy5MxBwGmutFOlf-IHamo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25183@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/25183#issuecomment-1104513185

Comment:
Ok, so:

- dbg doesn't work because jdk11 is built with `--with-native-debug-symbols=none`
	- this should work with `internal`, and xbps-src should strip them correctly (tested with jdk17 and gdb)
- I currently don't see any way to strip inside the jmods
- alpine ships jmods as a subpackage, but with `--with-native-debug-symbols=none`
- arch leaves all debug info and jmods in the main jdk package and does not set any debug-related configure options (not sure how they have such a small package size?)

personally I think subpackaging them is the best option for now.

  parent reply	other threads:[~2022-04-20 22:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29  3:06 [ISSUE] " Logarithmus
2020-09-29  4:33 ` Logarithmus
2020-09-29  4:35 ` ericonr
2020-09-29  4:40 ` Logarithmus
2020-09-29  5:02 ` Logarithmus
2020-09-29  5:02 ` Logarithmus
2020-09-29 19:38 ` leahneukirchen
2020-09-29 19:42 ` Logarithmus
2020-10-06 17:08 ` SevereOverfl0w
2022-04-20  2:14 ` github-actions
2022-04-20 12:15 ` leahneukirchen
2022-04-20 22:17 ` classabbyamp [this message]
2022-04-20 22:17 ` classabbyamp
2022-04-20 22:19 ` classabbyamp
2022-04-20 22:23 ` Logarithmus
2022-04-20 22:24 ` classabbyamp
2022-04-20 22:25 ` classabbyamp
2022-04-27 22:34 ` [ISSUE] [CLOSED] " leahneukirchen

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=20220420221729.PtbL2QoolV-blJVL2AVVwovy5MxBwGmutFOlf-IHamo@z \
    --to=classabbyamp@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 NNTP newsgroup(s).