powerpc64le-linux "Syslog not supported on this platform" #4885
Comments
kisgezenguz
changed the title
|
These particular files (and maybe other FFI files) are sorted out by processor-OS, and it appears we simply don't have a syslog definition for PowerPC LE at all. We do have syslog definitions for powerpc-aix and powerpc-darwin...perhaps they would be easy to adapt? Without access to a ppcle machine I won't be able to help, so maybe you can give it a try? |
|
Thanks headius, I follow you advise and create a new platform definition. rb3test:/tmp/jruby-9.1.14.0 # /tmp/jruby-9.1.14.0/bin/jruby -r etc -e 'puts "OK"' rb3test:~ # /tmp/jruby-9.1.14.0/bin/jruby -r syslog -e 'puts "OK"' I don't have experience with ruby/jruby and under ./lib/ruby/stdlib/ffi/platform/powerpc-aix are some configuration files (platform.conf, types.conf) how to check the content is correct or not for powerpc64le-linux? and for understanding |
|
I can't say with certain why it uses a different name. It is probably in the FFI logic shared between JRuby and MRI, or this mechanism existed before we used FFI extensively in JRuby proper. In any case, congratulations on fixing this! Can you submit a PR? |
|
sorry I am not a developer, PR meaning is? |
|
@kisgezenguz PR means pull request, a way to submit modifications back to a project. The primary reason we don't have a syslog for ppc64le is because none of us have access to ppc4le machines. Without that access, we have no way to adapt the other ppc64 logic to the ppc64le environment. You say you are not a developer, so perhaps we can work together to get this implemented. I'd recommend copying one of the ppc64 syslogs into the right location and see what happens. |
|
Oops, I lost track of this bug. I see now that you literally just copied the AIX files to the right location and they worked. I will make your change and attribute it to you. |
I noticed this now and I'm not sure either. It's possible that the resolution of the processor name changed, or it could be that in different environments or on different JVMs this resolves slightly differently. For now I believe the best option is to copy the ppc64le-linux files to powerpc64-linux with a note about the duplication. That should fix this issue. Then we can look into why we have both names. |
|
thank you headius, learned something new again regarding the changes I have now 3 week holiday so test the changes from my side is next year possible. |
|
I will push a commit that copies the related file and adds comments noting the duplication. |
|
I believe the commit that introduced this file (in the wrong directory) is 17c7a15. Note that it uses POWERPC64LE as the CPU_TYPE, but then puts the file in the directory with the short name. I don't believe any of the ppc dirs under platform are being used, so I'll remove them. |
Environment
on a SLES 12 SP1 on Power server
rb3test:~ # uname -a
Linux rb3test 4.4.90-92.45-default #1 SMP Tue Oct 24 15:03:15 UTC 2017 (1094ae5) ppc64le ppc64le ppc64le GNU/Linux
fresh build jruby
rb3test:~ # /tmp/jruby-9.1.14.0/bin/jruby -v
jruby 9.1.14.0 (2.3.3) 2017-12-06 fffffff OpenJDK 64-Bit Server VM 25.151-b12 on 1.8.0_151-b12 +jit [linux-ppc64le]
rb3test:/tmp/jruby-9.1.14.0 # ./mvnw
Downloading https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.3.9/apache-maven-3.3.9-bin.zip
.....
[INFO] Reactor Summary:
[INFO]
[INFO] JRuby .............................................. SUCCESS [ 4.791 s]
[INFO] JRuby Core ......................................... SUCCESS [ 45.169 s]
[INFO] JRuby Lib Setup .................................... SUCCESS [ 30.720 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:41 min
[INFO] Finished at: 2017-12-06T07:46:04+01:00
[INFO] Final Memory: 83M/614M
[INFO] ---------------------------------------------------------------------
standard installed ruby from Suse repo
rb3test:~ # ruby -v
ruby 2.1.9p490 (2016-03-30 revision 54437) [powerpc64le-linux-gnu]
rb3test:~ # rpm -qa | grep ruby
ruby2.1-devel-2.1.9-18.1.ppc64le
ruby2.1-rubygem-cfa_grub2-0.5.3-2.3.1.ppc64le
libstorage-ruby-2.26.10-13.5.ppc64le
ruby2.1-rubygem-ruby-augeas-0.5.0-1.40.ppc64le
yast2-ruby-bindings-3.1.51.2-9.3.1.ppc64le
ruby2.1-rubygem-gem2rpm-0.10.1-4.1.ppc64le
ruby2.1-2.1.9-18.1.ppc64le
ruby2.1-rubygem-bundler-1.7.3-3.8.ppc64le
ruby2.1-rubygem-cheetah-0.5.0-4.1.ppc64le
ruby2.1-rubygem-fast_gettext-0.9.2-1.1.ppc64le
ruby2.1-rubygem-cfa-0.3.1-1.1.ppc64le
ruby2.1-stdlib-2.1.9-18.1.ppc64le
ruby-2.1-1.6.ppc64le
ruby2.1-rubygem-abstract_method-1.2.1-4.1.ppc64le
ruby-common-2.1-19.1.noarch
libruby2_1-2_1-2.1.9-18.1.ppc64le
ruby2.1-rubygem-ruby-dbus-0.9.3-3.6.ppc64le
Expected Behavior
rb3test:~ # /tmp/jruby-9.1.14.0/bin/jruby -r syslog -e 'puts "OK"'
OK
like by ruby
rb3test:~ # ruby -r syslog -e 'puts "OK"'
OK
Actual Behavior
rb3test:~ # /tmp/jruby-9.1.14.0/bin/jruby -d -r syslog -e 'puts "OK"'
Exception
LoadError' at org/jruby/RubyKernel.java:955 - no such file to load -- /tmp/jruby-9.1.14.0/lib/ruby/stdlib/ffi/platform/powerpc64le-linux/syslog ExceptionLoadError' at /tmp/jruby-9.1.14.0/lib/ruby/stdlib/syslog.rb:20 - Syslog not supported on this platformException `LoadError' at /tmp/jruby-9.1.14.0/lib/ruby/stdlib/syslog.rb:20 - Syslog not supported on this platform
rb3test:~ # ruby -r syslog -e 'puts "OK"'
OK
seems powerpc64le-linux is not implemented
also strange ruby show platform powerpc64le-linux-gnu
jruby show linux-ppc64le but search for powerpc64le-linux
The text was updated successfully, but these errors were encountered: