linux/poky.git/meta/recipes-devtools/ruby, branch uninative-2.8

ruby: install required files for ptest

2020-02-28T23:11:28+00:00

After update to 2.7.0, it fails to start ptest of ruby with errors: | ./test/runner.rb:11:in `require_relative': cannot load such file -- /usr/lib64/ruby/ptest/tool/test/runner (LoadError) and | test/rdoc/test_rdoc_attr.rb: cannot load such file -- rdoc/version | test/did_you_mean/spell_checking/test_key_name_check.rb: cannot load such file -- /usr/lib64/ruby/ptest/lib/did_you_mean Install the required files for the ptest. (From OE-Core rev: be161be40c88fbac8ac17776daf3bf178a2e8f5e) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie

ruby: upgrade 2.6.5 -> 2.7.0

2020-02-15T10:26:42+00:00

0003-configure.ac-check-finite-isinf-isnan-as-macros-firs.patch Removed since it is included in 2.7.0. refresh the following patch: 0002-Obey-LDFLAGS-for-the-link-of-libruby.patch add the following patch to solve build error: 0001-Modify-shebang-of-libexec-y2racc-and-libexec-racc2y.patch [error message] ERROR: ruby-2.7.0-r0 do_package_qa: QA Issue: /usr/lib/ruby/gems/2.7.0/gems/racc-1.4.16/bin/y2racc contained in package ruby requires /usr/local/bin/ruby, but no providers found in RDEPENDS_ruby? [file-rdeps] format of file COPYING is updated. LEGAL notice information is updated. (From OE-Core rev: 3cdf5da514b424a6d78ba4e1412331b6cf2b3bff) Signed-off-by: Wang Mingyu Signed-off-by: Richard Purdie

ruby: Remove __has_include and __has_include_next from preprocessed header file

2020-01-27T16:48:09+00:00

one of the build steps ruby has is that it generated rb_mjit_header.h during configure using gcc preprocessor using -dD which emits built-in defines as well, problem happens when this header is later included in subsequent compiles, where compiler errors out stating that an existing internal define is redefined | /tmp/20200123-2021083-2c601q.h:13849:9: error: "__has_include" cannot be used as a macro name | 13849 | #define __has_include __has_include | | ^~~~~~~~~~~~~ | compilation terminated due to -Wfatal-errors. Since compiler already will take care of it internally we can edit it out from this header file (From OE-Core rev: b4f0df9a0e998af746bcd84cb81ea4ba0107f989) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

dhcp/ruby/ffpmeg: Use CFLAGS, not TARGET_CFLAGS

2019-11-07T15:12:00+00:00

There isn't anything specific about the target in these cases an in general recipes should touch CFLAGS. This ensures people don't copy/paste bad example usages. In reality, behaviour is mostly unchanged. (From OE-Core rev: ae6e7dd19b6da81090a38792dfdf31b459290466) Signed-off-by: Richard Purdie

ruby:upgrade 2.6.4 -> 2.6.5

2019-11-07T15:12:00+00:00

(From OE-Core rev: 087ed197ae7c5022a1185c09fc2d38c4acd7bf18) Signed-off-by: Zang Ruochen Signed-off-by: Richard Purdie

ruby: some ptest fixes

2019-10-23T15:30:36+00:00

* the (new?) ruby expects some additional compiled libraries to run, so we need to copy them as part of ptest. Fixes errors like: # ruby ./runner.rb ./-ext-/vm/test_at_exit.rb Run options: # Running tests: [1/1] TestVM#test_at_exit = 0.06 s 1) Failure: TestVM#test_at_exit [/usr/lib/ruby/ptest/test/-ext-/vm/test_at_exit.rb:7]: 1. [1/2] Assertion for "stdout" | <["begin", "end"]> expected but was | <[]>. 2. [2/2] Assertion for "stderr" | <[]> expected but was | <["-:1:in `require': cannot load such file -- -test-/vm/at_exit (LoadError)", | "\tfrom -:1:in `

'"]>. * the 'erb' test can't find the erb binary, as we're not running this from within the build directory (From OE-Core rev: 158d5285372240f6b3502a6c715a2491e37a3118) Signed-off-by: André Draszik Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

ruby: update to v2.6.4

2019-10-23T15:30:36+00:00

Most patches had to be refreshed Note that we can now drop EXTRA_AUTORECONF += "--exclude=aclocal" from the recipe, as ruby upstream now fully supports runnning aclocal: https://github.com/ruby/ruby/pull/1793/commits/df9bf70cd2275a3ddc3108f392214fcc4a9b0859 https://github.com/ruby/ruby/commit/ec43478f34de262ebdd2922c488e265344b489c3 Also note that 'created.rid' is not being installed anymore since v2.6.0 While additional LICENSEs were added to the recipe, they should always have been mentioned in this recipe, i.e. the license checksum was updated only because: * URLs were updated * new imported components were mentioned (with no new licenses) * formatting was changed * dates were updated (From OE-Core rev: 7124051b3b2e91e81c7b8565104ae9c5bea10be1) Signed-off-by: André Draszik Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

ruby: fix non-IPv6 support

2019-10-02T09:09:48+00:00

When IPv6 support is disabled, this recipe mis-configures ruby so that it end up non-working: --enable-wide-getaddrinfo instructs ruby to re-implement the standard getaddinfo(), but IPv6 support is still automatically detected via ext/socket/extconf.rb independently of that flag. To re-implement getaddrinfo(), ruby uses the obsolete getipnodebyaddr() and getipnodebyname() functions - i.e. according to the man-page, glibc provided those only in glibc 2.1.91-95; and of course compilation fails. [1] Switch to ruby's standard --enable-ipv6= configure options to make the build work without warnings, and ruby work at runtime as well. [1] Compilation and linking actually succeed, albeit with a warning regarding implicit declaration / unresolved symbols. The error is only obvious at runtime due to the unresolved symbols... (From OE-Core rev: 6ff71dd308b1611df7a8ea811a79b7cb884c99e9) Signed-off-by: André Draszik Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

ruby: configure mis-detects isnan/isinf on musl

2019-10-02T09:09:48+00:00

The configure script does not detect isnan/isinf as macros as is the case in musl: checking for isinf... no checking for isnan... no Backport an upstream patch from 2.7.0-preview1 to address this: checking whether isinf is declared... yes checking whether isnan is declared... yes (From OE-Core rev: b1afaccdba31341cace4b8d84d118ca76098587e) Signed-off-by: André Draszik Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

ruby: drop long-merged CVE patches

2019-10-02T09:09:48+00:00

The CVE patches here address the original problem in a different way to how upstream solved it, and are superfluous. Ruby updated to Onigmo v6.1.3+669ac999761 before its v2.5.0 release, and both CVEs were fixed before Onigmo v6.1.3: https://github.com/k-takata/Onigmo/releases/tag/Onigmo-6.1.3 https://github.com/k-takata/Onigmo/commits/Onigmo-6.1.3 https://github.com/k-takata/Onigmo/commit/40945546578004bf40e6f884834bcad4054c70f7 https://github.com/k-takata/Onigmo/commit/783b7ef491e1422e4be7407ccc3e4305e5013507 Because the issues were fixed differently here and in Ruby (Onigmo), patch never complained about duplicatation during recipe updates. (From OE-Core rev: 90dbe9019c81e25923ed450df80b4401d16287b4) Signed-off-by: André Draszik Signed-off-by: Ross Burton Signed-off-by: Richard Purdie