All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Madison <matt@madison.systems>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>,
	Henning Heinold <henning@itconsulting-heinold.de>,
	Otavio Salvador <otavio@ossystems.com.br>,
	Richard Leitner <richard.leitner@skidata.com>
Subject: Re: [OE-core] [meta-java] icedtea7-native build fails on kirkstone and in master
Date: Thu, 9 Jun 2022 03:13:48 -0700	[thread overview]
Message-ID: <CAGgRHJqubBN6mq6PxVMre98Xj5x_WnKZJywYwhM-0HA1ZdbiAA@mail.gmail.com> (raw)
In-Reply-To: <CAMRc=Md3LRW3OZ-AOkG5g1iNrH_k_gQdP3y03cKahgMN7aXF0A@mail.gmail.com>

(Dropping oe-core and leaving openembedded-devel, as that's the right
list for this)

On Thu, Jun 9, 2022 at 2:28 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
>
> Hi!
>
> I'm trying to build java support with the following configuration:
>
> Build Configuration:
> BB_VERSION           = "2.0.0"
> BUILD_SYS            = "x86_64-linux"
> NATIVELSBSTRING      = "universal"
> TARGET_SYS           = "x86_64-poky-linux"
> MACHINE              = "qemux86-64"
> DISTRO               = "poky"
> DISTRO_VERSION       = "4.0.1"
> TUNE_FEATURES        = "m64 core2"
> TARGET_FPU           = ""
> meta
> meta-poky            = "kirkstone:45d7615dfef8093a2467d52ca1130e62db6a1187"
> meta-oe              = "kirkstone:fcc7d7eae82be4c180f2e8fa3db90a8ab3be07b7"
> meta-java            = "kirkstone:1a8059f6b257ebe6fcae6416e499784d976afd24"
>
> ---
>
> PREFERRED_PROVIDER_virtual/java-initial-native = "cacao-initial-native"
> PREFERRED_PROVIDER_virtual/java-native = "jamvm-native"
> PREFERRED_PROVIDER_virtual/javac-native = "ecj-bootstrap-native"
>
> ---
>
> The build fails for icedtea7-native but it's hard to tell why exactly
> from the logs. Here is the full output: https://pastebin.com/3dRt6J0Y

I ran into this recently, too, after upgrading Ubuntu to 22.04.  Near
as I can tell, there's a bug in the dynamic linker in glibc 2.35 that
causes a segfault when it's invoked through ldd in some cases. One of
my colleagues that uses Manjaro for his development host also saw
this, and it, too, had glibc 2.35, so I think that's the common
factor.

I worked around the problem by disabling the ldd checks with

EXTRA_OEMAKE:append = " LDD=:"

in a bbappend.  This isn't specific to kirkstone, btw; my builds have
been dunfell-based.

The ldd checks in the makefiles don't seem particularly useful except
to the JDK developers, so turning them off didn't seem too terrible.

I see at least one bug open in the glibc bugzilla for something that
looks similar to this problem, but apparently not easily reproducible
with a small test case. I haven't had time to look into it further.

-Matt

>
> It seems to be failing here:
>
> | Checking for mapfile use in:
> /home/brgl/workspace/target-build-yocto/build/tmp/work/x86_64-linux/icedtea7-native/2.1.3-r1.0/icedtea-2.1.3/build/openjdk.build-boot/lib/amd64/libmanagement.so
> | Library loads for:
> /home/brgl/workspace/target-build-yocto/build/tmp/work/x86_64-linux/icedtea7-native/2.1.3-r1.0/icedtea-2.1.3/build/openjdk.build-boot/lib/amd64/libmanagement.so
> | make[5]: Leaving directory
> '/home/brgl/workspace/target-build-yocto/build/tmp/work/x86_64-linux/icedtea7-native/2.1.3-r1.0/icedtea-2.1.3/build/openjdk-boot/jdk/make/java/management'
> | make[5]: *** [../../common/Library.gmk:225:
> /home/brgl/workspace/target-build-yocto/build/tmp/work/x86_64-linux/icedtea7-native/2.1.3-r1.0/icedtea-2.1.3/build/openjdk.build-boot/lib/amd64/libmanagement.so]
> Error 1
> | make[4]: Leaving directory
> '/home/brgl/workspace/target-build-yocto/build/tmp/work/x86_64-linux/icedtea7-native/2.1.3-r1.0/icedtea-2.1.3/build/openjdk-boot/jdk/make/java'
> | make[4]: *** [Makefile:63: all] Error 1
> | make[3]: Leaving directory
> '/home/brgl/workspace/target-build-yocto/build/tmp/work/x86_64-linux/icedtea7-native/2.1.3-r1.0/icedtea-2.1.3/build/openjdk-boot/jdk/make'
> | make[3]: *** [Makefile:247: all] Error 1
> | make[2]: Leaving directory
> '/home/brgl/workspace/target-build-yocto/build/tmp/work/x86_64-linux/icedtea7-native/2.1.3-r1.0/icedtea-2.1.3/build/openjdk-boot'
> | make[2]: *** [make/jdk-rules.gmk:79: jdk-build] Error 2
> | make[1]: Leaving directory
> '/home/brgl/workspace/target-build-yocto/build/tmp/work/x86_64-linux/icedtea7-native/2.1.3-r1.0/icedtea-2.1.3/build/openjdk-boot'
> | make[1]: *** [Makefile:244: build_product_image] Error 2
> | make: *** [Makefile:2252: stamps/icedtea-boot.stamp] Error 2
>
> But not sure why.
>
> Thanks in advance for any help.
> Bart
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#166766): https://lists.openembedded.org/g/openembedded-core/message/166766
> Mute This Topic: https://lists.openembedded.org/mt/91641852/3618418
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [matt@madison.systems]
> -=-=-=-=-=-=-=-=-=-=-=-
>


  parent reply	other threads:[~2022-06-09 10:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09  9:28 [meta-java] icedtea7-native build fails on kirkstone and in master Bartosz Golaszewski
2022-06-09 10:03 ` [OE-core] " Jacob Kroon
2022-06-09 10:13 ` Matt Madison [this message]
2022-06-09 14:13   ` Bartosz Golaszewski
2023-03-01  2:53 ` leimaohui

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=CAGgRHJqubBN6mq6PxVMre98Xj5x_WnKZJywYwhM-0HA1ZdbiAA@mail.gmail.com \
    --to=matt@madison.systems \
    --cc=brgl@bgdev.pl \
    --cc=henning@itconsulting-heinold.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=richard.leitner@skidata.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.