* it was moved to meta-ruby (totherer with imsettings which depends on libgxim)
because of ruby-native dependency, now when ruby was moved from meta-ruby to
oe-core we can move libgxim back to meta-oe (which also allows imsettings
in meta-xfce to depend only on meta-oe as well)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
It depends on xfconf which is XFCE component, no one
depends on imsettings in meta-ruby so move it close
to its dependencies.
Ideally, xfconf should be turned into PACKAGECONFIG
and this recipe then moved to meta-oe since all kind
of DE's can use it then.
For now it frees meta-ruby from unnecessary dependency on xfce layer
Change-Id: I6b5896b0db504fad49a9da5967d3493e27c627b0
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
| configure.ac:18: warning: AM_NLS is m4_require'd but not m4_defun'd
| aclocal.m4:2363: IT_PROG_INTLTOOL is expanded from...
| aclocal.m4:2545: AC_PROG_INTLTOOL is expanded from...
| configure.ac:18: the top level
| configure:12119: error: possibly undefined macro: AM_NLS
| If this token and others are legitimate, please use m4_pattern_allow.
| See the Autoconf documentation.
Signed-off-by: Bian Naimeng <biannm@cn.fujitsu.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
This effectively reverts commit
4e8853ca05 [bundler: Fix QA new Error]
The original QA error is now handled by changes to the ruby.bbclass to
properly handle build_info and extensions directories that Ruby 2.0.0
now creates while installing gems.
This revert isn't specifically required but by removing this broad
definition of FILES the hope is that other ruby recipes won't copy
this behavior which can actually lead to other QA errors/warnings,
depending on what gets installed in the build_info and extensions
directories.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
It appears that newer versions of ruby produce additional directories
which were not previously handled by the ruby bbclass, specifically
'build_info' and 'extensions'. This is currently resulting in QA
errors/warnings such as:
ERROR: QA Issue: puppet: Files/directories were installed but not shipped in any package:
/usr/lib64/ruby/gems/2.2.0/build_info
/usr/lib64/ruby/gems/2.2.0/extensions
Please set FILES such that these items are packaged. Alternatively if they are unneeded,
avoid installing them or delete them within do_install. [installed-vs-shipped]
Add these to our FILES in the bbclass such that they will packaged.
NOTE: several files may exist in the extensions directory such as
gem.build_complete and mkmf.log that we can most likely remove during
do_install. Since ruby installs these by default they have been left
in case their existence is used as some type of stampfile or similar.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
multi-line ACLOCAL_AMFLAGS isn't supported by autoreconf, otherwise
a configure error as follow will be caught.
aclocal: error: non-option arguments are not accepted: '\'.
Signed-off-by: Bian Naimeng <biannm@cn.fujitsu.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
imsettings is a delivery framework for general input-method configuration
Signed-off-by: Bian Naimeng <biannm@cn.fujitsu.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
ERROR: Nothing PROVIDES 'ruby-native' (but /home/akuster/oss/clean/meta-openembedded/meta-oe/recipes-extended/libgxim/libgxim_0.5.0.bb DEPENDS on or otherwise requires it). Close matches:
db-native
bc-native
byacc-native
ERROR: Required build target 'libgxim' has no buildable providers.
Missing or unbuildable dependency chain was: ['libgxim', 'ruby-native']
move libgxim from meta-oe to meta-ruby, it really belongs in meta-gir but it is un-maintained.
Signed-off-by: Armin Kuster <akuster808@gmail.com>
both 2.2.1 and 2.2.2 are failing on some hosts native builds with:
| linking miniruby
| load.o: In function `rb_f_load':
| load.c:(.text+0x3af): undefined reference to `RUBY_DTRACE_LOAD_ENTRY_ENABLED'
| load.c:(.text+0x428): undefined reference to `RUBY_DTRACE_LOAD_RETURN_ENABLED'
| load.c:(.text+0x452): undefined reference to `RUBY_DTRACE_LOAD_RETURN'
| load.c:(.text+0x492): undefined reference to `RUBY_DTRACE_LOAD_ENTRY'
| load.o: In function `rb_require_internal':
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Includes among other things: CVE-2015-1855: Ruby OpenSSL Hostname Verification
for more info see:
http://svn.ruby-lang.org/repos/ruby/tags/v2_2_2/ChangeLog
also, fixed runtime error.
only include "enable-wide-getaddrinfo" if IVP6 is enabled in disto feature
otherwise 'gem install rails' throws an error for the missing symbol 'getipnodebyname'.
Signed-off-by: Armin Kuster <akuster808@gmail.com>
LIC_FILES_CHKSUM changes:
BDSL: update copyright notice with "2013"
GPL: update to GPLv2
LEGAL: added license info for ccan files
dropped patches since they are now incorperated.
several security fixes included:
CVE-2014-2525
CVE-2014-0160
CVE-2014-2734
CVE-2014-8080
CVE-2014-8090
for addional information:
http://svn.ruby-lang.org/repos/ruby/tags/v2_2_1/ChangeLog
Signed-off-by: Armin Kuster <akuster808@gmail.com>
According to README, it depends on oe-core and openembedded-layer
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* disabled by default
* fixes:
ruby/1.9.3-p547-r1.0/ruby-1.9.3-p547/gc.c:43:32:fatal error: valgrind/memcheck.h: No such file or directory
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Without this dependency we will see warnings when ever we use the
ruby-native from the sysroot
...tmp/sysroots/x86_64-linux/usr/lib/ruby/yaml.rb:84:in `<top (required)>':
It seems your ruby installation is missing psych (for YAML output).
To eliminate this warning, please install libyaml and reinstall your ruby.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
In order to allow the building of gems we have created a
ruby.bbclass. The building of gems is much like the building of python
packages in that we rely on building up -native gems in order to
facilitate the cross compiling of the gems that will be built for the
target. When dependencies exist between gems they must be satisfied by
the -native gems installed in the host sysroot. This approach is
feasible since the build process is able to query installed gems
without being affected by the ARCH they were built for. At this point
I have yet to come across a situation where the assumption associated
with this approach have failed but so far focus has only been on x86
and x86-64 builds.
The recipes which inherit the ruby.bbclass can optionally define a BPV
in the case where the gemspec version doesn't always map 1:1 to the
PV. This situation has only been encountered on a few occasions so
the class has been made to default BPV to PV.
To demonstrate the ruby.bbclass in use we have included a recipe to
build the bundler gem. Bundler can be used on a running target to
install gems from rubygems.org, which can be useful in itself when you
don't have recipes available for gems but want to try installing and
running pre-built gems.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* lib/mkmf.rb (create_makefile): fix race conditions at install-ext.
target files need to depend on destination directory timestamp
files, not phony trgets.
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
remove ruby-1.9.3-fix-s390x-build.patch, it has been merged into p547
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
This patch does nothing except causing failures from the second build in
the same working directory.
Signed-off-by: Michaël Burtin <mburtin@connected-labs.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Rather than hardcoding ${datadir}/rubygems, we can let it find the gems
relative to its own location, to make it relocatable.
Signed-off-by: Christopher Larson <kergoth@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Old recipe was having do_install failures
this fixes those too
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* This change is only aesthetic (unlike indentation in Python
tasks).
* Some recipes were using tabs.
* Some were using 8 spaces.
* Some were using mix or different number of spaces.
* Make them consistently use 4 spaces everywhere.
* Yocto styleguide advises to use tabs (but the only reason to keep
tabs is the need to update a lot of recipes). Lately this advice
was also merged into the styleguide on the OE wiki.
* Using 4 spaces in both types of tasks is better because it's less
error prone when someone is not sure if e.g.
do_generate_toolchain_file() is Python or shell task and also allows
to highlight every tab used in .bb, .inc, .bbappend, .bbclass as
potentially bad (shouldn't be used for indenting of multiline
variable assignments and cannot be used for Python tasks).
* Don't indent closing quote on multiline variables
we're quite inconsistent wheater it's first character on line
under opening quote or under first non-whitespace character in
previous line.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Acked-by: Koen Kooi <koen@dominion.thruhere.net>
I sent this to oe-core but was told that it's not the right place and
was suggested to send here.
Most of the 1.9.3 patches originate from ruby-1.9.3.194-10.1.fc17.src.rpm
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
