bytedeco/javacpp

Raspberry Pi failure with OpenJDK

Open

#349 opened on Oct 6, 2019

View on GitHub
 (22 comments) (0 reactions) (1 assignee)Java (4,279 stars) (620 forks)batch import
enhancementhelp wanted

Description

Yes, I know you already know but that was tagged on to the HDF5 stuff so proper bug report time

Is there still a skip tests switch? I wanna do presets hdf5 for you.

This is an ARMHF 32bit on a Raspberry Pi4 with stock OS (a Debian Buster fork)

Of note is this which occurs right at the start - possibly the problem? Full log attached.

debug.jcpp.zip

WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release

Contributor guide

Tech stack
javacpp
Domain
backendbuild system
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Javanative compilationRaspberry Pi
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the illegal reflective access warning and verify if it is related to the build failure on ARMHF. Check the native compilation scripts in the repository for ARM specific flags. Look into the HDF5 presets mentioned. Consider reproducing the issue on a similar setup or using a cross compiler.