W dniu 24.11.2021 o 14:00, Arkadiusz Miśkiewicz pisze:
> W dniu 22.10.2021 o 11:37, Jan Palus pisze:
>> On 22.10.2021 10:44, Jan Rękorajski wrote:
>>> Ah, it wasn't icedtea but openjdk8 that was installed on i686 and x86_64.
>>> I'm uninstalling it and blocking in poldek on builders so that we have
>>> only openjdk11 installable there.
>> Currently openjdk8 requires either JDK 1.7 or 1.8 for build, I guess we
>> can patch it and try to build with openjdk11, no guarantees it would
>> work though. Not sure what is the difference but I had no issues
>> building openjdk8 with openjdk8 and glibc 2.34 on
>> x86_64, aarch64 and armv7hnl. I'll try to reproduce in fresh VM.
> For me our openjdk8 from ftp hangs on just doing "java -version". Not
> always. Sometimes I need to run that 5-10 times but I do get the hang
> easily. kernel 4.9.194, glibc 2.34, x86_64, vserver guest
> while (true); do date; java -version; done
> openjdk version "1.8.0_302-ga"
> OpenJDK Runtime Environment (build 1.8.0_302-ga-1)
> OpenJDK 64-Bit Server VM (build 25.302-b1, mixed mode)
> Build Date  : pon, 2 sie 2021, 16:46:33

More fun with that.

working system, glibc 2.34, on any kernel

mkdir /test/
rsync -avPH / /test/ --exclude /test/ --exclude /proc --exclude /sys
mount /proc /test/proc -o bind
chroot /test/; java -version - hangs at some retry

mkdir -p /test/sys/devices/system/cpu
chroot /test/; java -version - no hangs
(so proc is mounted but /sys is not; just dir exists)

Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
pld-devel-en mailing list

Reply via email to