* Issue with RDEPENDS in module.bbclass for initramfs
From: Anders Darander @ 2011-10-25 6:35 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
We have recently started investigating to make an even smaller build of
our local distro & machine. This smaller build should be run exclusively
from an initramfs, thus we have a need to reduće the size of the rootfs
as much as possible. (Especially as we'd still like some "bigger"
tools/pieces in the initramfs).
However, our first attempt to create a small image turned our to be
larger than expected. After a first investigation, it turns out that our
external kernel modules have an RDEPENDS on kernel-image (this is from
module.bbclass). As we're creating an initramfs-based rootfs, this is
obviously not desired... Locally removeing that RDEPENDS reduces the
image as expected...
I understand that in the general distro case, there is a need to be able
to express a dependency on a certain kernel version. However, I really
don't think that bringing in the kernel-image is a good idea, not an
general embedded platforms at least. (On the x86 this is usually not a
problem, as you almost always have the kernel as a part of the rootfs
anyway).
Could we come up with another way of expressing this dependency? That
would definitely be valuable for the small-ish embedded systems.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
^ permalink raw reply
* Issue with RDEPENDS in module.bbclass for initramfs
From: Anders Darander @ 2011-10-25 6:09 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
We have recently started investigating to make an even smaller build of
our local distro & machine. This smaller build should be run exclusively
from an initramfs, thus we have a need to reduće the size of the rootfs
as much as possible. (Especially as we'd still like some "bigger"
tools/pieces in the initramfs).
However, our first attempt to create a small image turned our to be
larger than expected. After a first investigation, it turns out that our
external kernel modules have an RDEPENDS on kernel-image (this is from
module.bbclass). As we're creating an initramfs-based rootfs, this is
obviously not desired... Locally removeing that RDEPENDS reduces the
image as expected...
I understand that in the general distro case, there is a need to be able
to express a dependency on a certain kernel version. However, I really
don't think that bringing in the kernel-image is a good idea, not an
general embedded platforms at least. (On the x86 this is usually not a
problem, as you almost always have the kernel as a part of the rootfs
anyway).
Could we come up with another way of expressing this dependency? That
would definitely be valuable for the small-ish embedded systems.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
^ permalink raw reply
* [PATCH 1/1] distro_tracking_fields: update packages tracking fields
From: wenzong.fan @ 2011-10-25 2:49 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <cover.1319510805.git.wenzong.fan@windriver.com>
From: Wenzong Fan <wenzong.fan@windriver.com>
Update packages tracking fields including ccache, chkconfig.
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
---
.../conf/distro/include/distro_tracking_fields.inc | 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/meta/conf/distro/include/distro_tracking_fields.inc b/meta/conf/distro/include/distro_tracking_fields.inc
index 1f3540e..f053f87 100644
--- a/meta/conf/distro/include/distro_tracking_fields.inc
+++ b/meta/conf/distro/include/distro_tracking_fields.inc
@@ -5976,6 +5976,18 @@ RECIPE_MANUAL_CHECK_DATE_pn-libsdl = "Jul 28, 2011"
RECIPE_MAINTAINER_pn-libsdl = "Kai Kang <kai.kang@windriver.com>"
DISTRO_PN_ALIAS_pn-libsdl = "Fedora=SDL Opensuse=SDL"
+RECIPE_STATUS_pn-ccache = "green"
+RECIPE_MAINTAINER_pn-ccache = "Wenzong Fan <wenzong.fan@windriver.com>"
+RECIPE_LATEST_VERSION_pn-ccache = "3.1.6"
+RECIPE_LAST_UPDATE_pn-ccache = "October 19, 2011"
+RECIPE_MANUAL_CHECK_DATE_pn-ccache = "October 25, 2011"
+
+RECIPE_STATUS_pn-chkconfig = "green"
+RECIPE_MAINTAINER_pn-chkconfig = "Wenzong Fan <wenzong.fan@windriver.com>"
+RECIPE_LATEST_VERSION_pn-chkconfig = "1.3.55"
+RECIPE_LAST_UPDATE_pn-chkconfig = "October 19, 2011"
+RECIPE_MANUAL_CHECK_DATE_pn-chkconfig = "October 25, 2011"
+
DISTRO_PN_ALIAS_pn-lame = "Debian=lame Ubuntu=lame"
DISTRO_PN_ALIAS_pn-libiconv = "Fedora=mingw-libiconv Opensuse=cross-mingw-libiconv"
DISTRO_PN_ALIAS_pn-qt4-native = "Fedora=qt4 Debian=qt4-dev-tools"
--
1.7.0.4
^ permalink raw reply related
* [PATCH 0/1] distro_tracking_fields: update packages tracking fields
From: wenzong.fan @ 2011-10-25 2:49 UTC (permalink / raw)
To: openembedded-core
From: Wenzong Fan <wenzong.fan@windriver.com>
Update distro tracking fields for ccache, chkconfig.
The following changes since commit 53ee27a1c5b589cba874f674c428e1a36557cc3b:
Joshua Lock (1):
doc: update manual for checksum changes
are available in the git repository at:
git://git.pokylinux.org/poky-contrib wenzong/distro_tracking_fields_update
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=wenzong/distro_tracking_fields_update
Wenzong Fan (1):
distro_tracking_fields: update packages tracking fields
.../conf/distro/include/distro_tracking_fields.inc | 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)
^ permalink raw reply
* [PATCH] Give coreutils a chance to build the df utility
From: Julian Pidancet @ 2011-10-25 1:18 UTC (permalink / raw)
To: openembedded-core; +Cc: Julian Pidancet
The coreutils configure script is unable determine how to get free
space from the Operating System when cross-compiling. This patch
gives it some extra help by setting the fu_cv_sys_stat_statfs2_bsize
variable to yes before invoking the configure script.
Signed-off-by: Julian Pidancet <julian.pidancet@gmail.com>
---
meta/recipes-core/coreutils/coreutils_8.14.bb | 6 +++++-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-core/coreutils/coreutils_8.14.bb b/meta/recipes-core/coreutils/coreutils_8.14.bb
index f3b7af7..3c75ddf 100644
--- a/meta/recipes-core/coreutils/coreutils_8.14.bb
+++ b/meta/recipes-core/coreutils/coreutils_8.14.bb
@@ -27,7 +27,7 @@ bindir_progs = "base64 basename chcon cksum comm csplit cut dir dircolors dirnam
join link logname md5sum mkfifo mktemp nice nl nohup nproc od paste pathchk \
pinky pr printenv printf ptx readlink runcon seq sha1sum sha224sum sha256sum \
sha384sum sha512sum shred shuf sort split stat stdbuf sum tac tail tee test timeout\
- tr truncate tsort tty unexpand uniq unlink uptime users vdir wc who whoami yes"
+ tr truncate tsort tty unexpand uniq unlink uptime users vdir wc who whoami yes df"
# hostname gets a special treatment and is not included in this
base_bindir_progs = "cat chgrp chmod chown cp date dd echo false kill ln ls mkdir \
@@ -35,6 +35,10 @@ base_bindir_progs = "cat chgrp chmod chown cp date dd echo false kill ln ls mkdi
sbindir_progs= "chroot"
+do_configure_prepend () {
+ export fu_cv_sys_stat_statfs2_bsize=yes
+}
+
do_install_append() {
for i in ${bindir_progs}; do mv ${D}${bindir}/$i ${D}${bindir}/$i.${PN}; done
--
Julian Pidancet
^ permalink raw reply related
* [PATCH] Introduce biarch DISTRO_FEATURE
From: Julian Pidancet @ 2011-10-25 1:18 UTC (permalink / raw)
To: openembedded-core; +Cc: Julian Pidancet
This patch introduces a distro feature which enables gcc to produce
both 32bit and 64bit code, and enables binutils to operate on both
32bit and 64bit binaries. It differs from multilib toolchains in
that it does not require to compile a version of the libc for each
architecture variant. However, the code produced for the secondary
architecture will not be linkable against the libc.
This patch only works with x86 and x86_64 architectures, but can
probably be extended to support other architectures as well.
One use-case would be when one wants to compile a system which runs
32bit userspace applications with a 64bit kernel without having to
deal with two separate libc.
Signed-off-by: Julian Pidancet <julian.pidancet@gmail.com>
---
meta/recipes-devtools/binutils/binutils-cross.inc | 3 ++-
meta/recipes-devtools/binutils/binutils.inc | 3 ++-
meta/recipes-devtools/gcc/gcc-common.inc | 5 +++++
meta/recipes-devtools/gcc/gcc-configure-common.inc | 3 ++-
4 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-devtools/binutils/binutils-cross.inc b/meta/recipes-devtools/binutils/binutils-cross.inc
index 982224f..3f76c59 100644
--- a/meta/recipes-devtools/binutils/binutils-cross.inc
+++ b/meta/recipes-devtools/binutils/binutils-cross.inc
@@ -10,7 +10,8 @@ EXTRA_OECONF = "--with-sysroot=${STAGING_DIR_TARGET} \
--disable-werror \
--disable-nls \
--enable-poison-system-directories \
- ${@base_contains('DISTRO_FEATURES', 'ld-is-gold', '--enable-gold=default', '', d)}"
+ ${@base_contains('DISTRO_FEATURES', 'ld-is-gold', '--enable-gold=default', '', d)} \
+ ${@base_contains('DISTRO_FEATURES', 'biarch', '--enable-64-bit-bfd', '', d)}"
do_install () {
oe_runmake 'DESTDIR=${D}' install
diff --git a/meta/recipes-devtools/binutils/binutils.inc b/meta/recipes-devtools/binutils/binutils.inc
index 58fee85..fe16b18 100644
--- a/meta/recipes-devtools/binutils/binutils.inc
+++ b/meta/recipes-devtools/binutils/binutils.inc
@@ -49,7 +49,8 @@ B = "${S}/build.${HOST_SYS}.${TARGET_SYS}"
EXTRA_OECONF = "--program-prefix=${TARGET_PREFIX} \
--enable-install-libbfd \
- --enable-shared"
+ --enable-shared \
+ ${@base_contains('DISTRO_FEATURES', 'biarch', '--enable-64-bit-bfd', '', d)}"
EXTRA_OECONF_virtclass-native = "--enable-target=all --enable-64-bit-bfd --enable-install-libbfd"
diff --git a/meta/recipes-devtools/gcc/gcc-common.inc b/meta/recipes-devtools/gcc/gcc-common.inc
index f83f4da..fdbb77b 100644
--- a/meta/recipes-devtools/gcc/gcc-common.inc
+++ b/meta/recipes-devtools/gcc/gcc-common.inc
@@ -21,6 +21,11 @@ def get_gcc_mips_plt_setting(bb, d):
return "--with-mips-plt"
return ""
+def get_gcc_x86_biarch_setting(bb, d):
+ if bb.data.getVar('TARGET_ARCH', d, 1) in [ 'i586', 'i686', 'x86_64' ] and 'biarch' in bb.data.getVar('DISTRO_FEATURES',d,1).split() :
+ return "--enable-targets=all"
+ return ""
+
# We really need HOST_SYS here for some packages and TARGET_SYS for others.
# For now, libgcc is most important so we fix for that - RP.
SHLIBSDIR = "${STAGING_DIR_TARGET}/shlibs"
diff --git a/meta/recipes-devtools/gcc/gcc-configure-common.inc b/meta/recipes-devtools/gcc/gcc-configure-common.inc
index 2ddc3d7..55a0626 100644
--- a/meta/recipes-devtools/gcc/gcc-configure-common.inc
+++ b/meta/recipes-devtools/gcc/gcc-configure-common.inc
@@ -42,7 +42,8 @@ EXTRA_OECONF = "${@['--enable-clocale=generic', ''][bb.data.getVar('USE_NLS', d,
${EXTRA_OECONF_BASE} \
${EXTRA_OECONF_FPU} \
${EXTRA_OECONF_PATHS} \
- ${@get_gcc_mips_plt_setting(bb, d)}"
+ ${@get_gcc_mips_plt_setting(bb, d)} \
+ ${@get_gcc_x86_biarch_setting(bb, d)}"
# Build uclibc compilers without cxa_atexit support
EXTRA_OECONF_append_linux = " --enable-__cxa_atexit"
--
Julian Pidancet
^ permalink raw reply related
* Re: Dependency problem in mysql ?
From: Eric Bénard @ 2011-10-24 20:29 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <20111024202541.GA14251@mail.adw-basketball.de>
Le 24/10/2011 22:25, Henning Heinold a écrit :
> On Mon, Oct 24, 2011 at 10:18:11PM +0200, Eric Bénard wrote:
>> Hi,
>>
>> while testing a build from scratch of a configuration which was
>> working, I increased BB_NUMBER_THREADS to "8" and PARALLEL_MAKE to
>> "-j6" and started to get problems with mysql (log at the end of this
>> mail).
>>
>> Reducing BB_NUMBER_THREADS to 4 "solved" the problem.
>>
>> Any idea what dependency could be missing in mysql ?
>>
>> Thanks,
>> Eric
>
> None,
>
> you just hit a parallel make error inside mysql I think.
>
Thanks, I also reduced PARALLEL_MAKE to j4 which seems to confirm this.
I think I also met the same kind of problem with directfb.
Eric
^ permalink raw reply
* Re: Dependency problem in mysql ?
From: Henning Heinold @ 2011-10-24 20:25 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <4EA5C803.1030205@eukrea.com>
On Mon, Oct 24, 2011 at 10:18:11PM +0200, Eric Bénard wrote:
> Hi,
>
> while testing a build from scratch of a configuration which was
> working, I increased BB_NUMBER_THREADS to "8" and PARALLEL_MAKE to
> "-j6" and started to get problems with mysql (log at the end of this
> mail).
>
> Reducing BB_NUMBER_THREADS to 4 "solved" the problem.
>
> Any idea what dependency could be missing in mysql ?
>
> Thanks,
> Eric
None,
you just hit a parallel make error inside mysql I think.
Bye Henning
^ permalink raw reply
* Dependency problem in mysql ?
From: Eric Bénard @ 2011-10-24 20:18 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
Hi,
while testing a build from scratch of a configuration which was working, I
increased BB_NUMBER_THREADS to "8" and PARALLEL_MAKE to "-j6" and started to
get problems with mysql (log at the end of this mail).
Reducing BB_NUMBER_THREADS to 4 "solved" the problem.
Any idea what dependency could be missing in mysql ?
Thanks,
Eric
OE Build Configuration:
BB_VERSION = "1.13.3"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "eukrea-cpuimx35"
DISTRO = "angstrom"
DISTRO_VERSION = "v2011.10-core"
TUNE_FEATURES = "armv6 vfp arm1136jfs"
TARGET_FPU = "vfp"
meta-angstrom = "master:8c6a777b3411140b0147171189148152a5f8ed58"
meta-oe
meta-efl
meta-gpe
meta-gnome
meta-xfce = "master:2631ed9f4c987192749960bc7a2209b5f5bbfa78"
meta-eukrea
meta-eukrea-cpuimx35 = "master:5aa07bdfc3fe8961c8165317698a805ee92dfe9d"
meta = "master:e25fad9b8eef59bf7ca11ae141739d0bc2235655"
Then bitbake linux 3 x images (including one integrating qtdemo)
leaded 3 consecutive times to :
| arm-angstrom-linux-gnueabi-g++ -march=armv6 -mthumb-interwork
-mfloat-abi=softfp -mtune=arm1136jf-s -mthumb-interwork -mno-thumb
--sysroot=/home/ebenard/OECORE/tmp/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/eukrea-cpuimx35
-DDEFAULT_BASEDIR=\"/usr\" -DMYSQL_DATADIR="\"/var/mysql\""
-DDEFAULT_CHARSET_HOME="\"/usr\"" -DSHAREDIR="\"/usr/share/mysql\""
-DDEFAULT_HOME_ENV=MYSQL_HOME -DDEFAULT_GROUP_SUFFIX_ENV=MYSQL_GROUP_SUFFIX
-DDEFAULT_SYSCONFDIR="\"/etc/mysql\"" -DHAVE_CONFIG_H -I. -I../include
-I../include -I../include -I. -O2 -pipe -g -feliminate-unused-debug-types
-fpermissive -fvisibility-inlines-hidden -fvisibility-inlines-hidden
-fno-implicit-templates -fno-exceptions -fno-rtti -c -o my_new.o my_new.cc
| In file included from mysys_priv.h:16:0,
| from my_new.cc:21:
| ../include/my_global.h:1516:15: fatal error: new: No such file or directory
| compilation terminated.
| make[1]: *** [my_new.o] Error 1
| make[1]: Leaving directory
`/home/ebenard/OECORE/tmp/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv6-vfp-angstrom-linux-gnueabi/mysql5-5.1.40-r5/mysql-5.1.40/mysys'
| make: *** [all-recursive] Error 1
| + die 'oe_runmake failed'
| + bbfatal 'oe_runmake failed'
| + echo 'ERROR: oe_runmake failed'
| ERROR: oe_runmake failed
| + exit 1
NOTE: package mysql5-5.1.40-r5: task do_compile: Failed
ERROR: Task 1566
(/home/ebenard/OECORE/tmp/setup-scripts/sources/meta-openembedded/meta-oe/recipes-support/mysql/mysql5_5.1.40.bb,
do_compile) failed with exit code '1'
^ permalink raw reply
* Re: serial-console: IMAGE_FEATURE, MACHINE_FEATURE or DISTRO_FEATURE?
From: Chris Larson @ 2011-10-24 17:59 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <CACW_hTYqjsZzB2WRJ=EED4KGwqcGb2UVtKpKjZGNf-urO35G-w@mail.gmail.com>
On Mon, Oct 24, 2011 at 1:27 AM, Frans Meulenbroeks
<fransmeulenbroeks@gmail.com> wrote:
> 2011/10/24 Koen Kooi <koen@dominion.thruhere.net>
>>
>> Hi,
>>
>> Otavio is cleaning up systemd in meta-oe to work with his initramfs setup
>> and we stumbled onto a challenge that we'd like some more feedback on.
>>
>> The old sysvinit recipes always hardcode a serial getty into inittab,
>> systemd installs a getty@<port>.service file instead. Otavio doesn't need
>> (or want) a getty on serial in his setup, but I need (and want) it on all my
>> setups. So we agreed that it needs to be a feature :)
>>
>> I nitially suggested MACHINE_FEATURE, which Otavio implemented here:
>> http://patchwork.openembedded.org/patch/13713/
>>
>> , but I'm having second thoughs about it and am leaning toward an
>> IMAGE_FEATURE instead. Since this involves *_FEATURE and we want systemd to
>> move into oe-core eventually I'm moving the discussion from OE-devel to
>> OE-core. Not much discussion has been going on, so I hope we'll get some
>> more feedback here. I'll try to buttonhole some more OE developers at ELC
>> and report back as well.
>>
>
>
> Technically it is probably both.
> I've seen embedded systems without a console. That seems to indicate a
> machine feature.
> Then again even if you have a console you might not want to enable it (e.g.
> in order not to give the customer root access or even info wrt printk etc).
> That seems to indicate a machine feature.
> Probably the answer is inbetween: A machine feature HAS_CONSOLE or something
> like that and an image feature CONSOLE_ENABLED.
That sounds analogous to
MACHINE_FEATURES+DISTRO_FEATURES==COMBINED_FEATURES, but by image
rather than distro?
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
^ permalink raw reply
* Re: [PATCH 1/1] gst-plugins-good: correctly handle gconf schema
From: Richard Purdie @ 2011-10-24 16:18 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <64effb846c8f9b1e6fe57a7e213d24d046439b99.1319135920.git.josh@linux.intel.com>
On Thu, 2011-10-20 at 11:40 -0700, Joshua Lock wrote:
> Add the shipped gconf schema to the gconfelements package and inherit the gconf
> class so that schema processing is handled via post* scripts.
>
> Signed-off-by: Joshua Lock <josh@linux.intel.com>
> ---
> .../gstreamer/gst-plugins-good_0.10.30.bb | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
Merged to master, thanks.
Richard
^ permalink raw reply
* Re: [CONSOLIDATED PULL 11/27] pulseaudio-0.9.23: inherit perlnative to work around build on host without XML/Parser.pm
From: Martin Jansa @ 2011-10-24 14:24 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <1319465707.25011.21.camel@ted>
[-- Attachment #1: Type: text/plain, Size: 1629 bytes --]
On Mon, Oct 24, 2011 at 03:15:07PM +0100, Richard Purdie wrote:
> On Mon, 2011-10-24 at 15:19 +0200, Koen Kooi wrote:
> > Op 24 okt. 2011, om 15:15 heeft Richard Purdie het volgende geschreven:
> >
> > > On Sun, 2011-10-23 at 11:26 -0700, Saul Wold wrote:
> > >> From: Martin Jansa <Martin.Jansa@gmail.com>
> > >>
> > >> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > >> ---
> > >> .../pulseaudio/pulseaudio_0.9.23.bb | 2 +-
> > >> 1 files changed, 1 insertions(+), 1 deletions(-)
> > >>
> > >> diff --git a/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb b/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
> > >> index 33f5e15..4ac2418 100644
> > >> --- a/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
> > >> +++ b/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
> > >> @@ -4,7 +4,7 @@ PR = "r5"
> > >>
> > >> DEPENDS += "gdbm speex"
> > >>
> > >> -inherit gettext
> > >> +inherit gettext perlnative
> > >
> > > This doesn't look right. If we need xmlparser, we should state that in
> > > DEPENDS. If that is added to DEPENDS, I'm not sure we still need the
> > > inherit of perlnative?
> >
> > If you need xmlparser during the build you almost always need the
> > perlnative wrapper as well :(
>
> I was under the impression that we'd fixed most of those issues :/. It
> could well be a valid dependency in this case so I'll take the patch
> with the added DEPENDS.
Those were imho transitive deps from intltool, that's why this is a bit
different.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
^ permalink raw reply
* Re: [CONSOLIDATED PULL 20/27] libtool: Upgrade from 2.4 -> 2.4.2
From: Richard Purdie @ 2011-10-24 14:24 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <C0347AB9-9B51-4127-AEB7-AA1F0BE53BD6@dominion.thruhere.net>
On Mon, 2011-10-24 at 16:18 +0200, Koen Kooi wrote:
> Op 24 okt. 2011, om 16:10 heeft Richard Purdie het volgende geschreven:
>
> > On Mon, 2011-10-24 at 15:37 +0200, Koen Kooi wrote:
> >> Op 24 okt. 2011, om 15:34 heeft Richard Purdie het volgende geschreven:
> >>
> >>> On Sun, 2011-10-23 at 11:26 -0700, Saul Wold wrote:
> >>>> From: Khem Raj <raj.khem@gmail.com>
> >>>>
> >>>> Adjust prefix.patch and delete resolve-sysroot.patch
> >>>> since its already applied upstream
> >>>>
> >>>> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> >>>> ---
> >>>> .../libtool/{libtool.inc => libtool-2.4.2.inc} | 26 +++++++++---
> >>>> meta/recipes-devtools/libtool/libtool-2.4.inc | 13 ------
> >>>> ...libtool-cross_2.4.bb => libtool-cross_2.4.2.bb} | 2 +-
> >>>> ...btool-native_2.4.bb => libtool-native_2.4.2.bb} | 2 +-
> >>>> ...nativesdk_2.4.bb => libtool-nativesdk_2.4.2.bb} | 2 +-
> >>>> meta/recipes-devtools/libtool/libtool/prefix.patch | 46 ++++++++++----------
> >>>> .../libtool/libtool/resolve-sysroot.patch | 42 ------------------
> >>>> .../libtool/{libtool_2.4.bb => libtool_2.4.2.bb} | 2 +-
> >>>> 8 files changed, 47 insertions(+), 88 deletions(-)
> >>>> rename meta/recipes-devtools/libtool/{libtool.inc => libtool-2.4.2.inc} (57%)
> >>>> delete mode 100644 meta/recipes-devtools/libtool/libtool-2.4.inc
> >>>> rename meta/recipes-devtools/libtool/{libtool-cross_2.4.bb => libtool-cross_2.4.2.bb} (98%)
> >>>> rename meta/recipes-devtools/libtool/{libtool-native_2.4.bb => libtool-native_2.4.2.bb} (96%)
> >>>> rename meta/recipes-devtools/libtool/{libtool-nativesdk_2.4.bb => libtool-nativesdk_2.4.2.bb} (97%)
> >>>> delete mode 100644 meta/recipes-devtools/libtool/libtool/resolve-sysroot.patch
> >>>> rename meta/recipes-devtools/libtool/{libtool_2.4.bb => libtool_2.4.2.bb} (94%)
> >>>>
> >>>> diff --git a/meta/recipes-devtools/libtool/libtool.inc b/meta/recipes-devtools/libtool/libtool-2.4.2.inc
> >>>> similarity index 57%
> >>>> rename from meta/recipes-devtools/libtool/libtool.inc
> >>>> rename to meta/recipes-devtools/libtool/libtool-2.4.2.inc
> >>>> index ef9095b..1f652ef 100644
> >>>> --- a/meta/recipes-devtools/libtool/libtool.inc
> >>>> +++ b/meta/recipes-devtools/libtool/libtool-2.4.2.inc
> >>>> @@ -1,4 +1,3 @@
> >>>> -SUMMARY = "Generic library support script"
> >>>
> >>> Why drop the SUMMARY field?
> >>
> >> What's the difference between SUMMARY and DESCRIPTION? And what happens if both are set?
> >
> > SUMMARY is a one line 74? character summary of the package, DESCRIPTION
> > is a multiple line stream of text containing a more verbose description.
> > What happens to the data is package backend specific, I know RPM has
> > uses for both. There was definitely discussion about this on the mailing
> > list at the time, I'm not sure what if anything made it into the manuals
> > but if its not there it should be added.
>
>
> It seems to get OR'd:
>
> meta/classes/package_deb.bbclass: summary = bb.data.getVar('SUMMARY', localdata, True) or bb.data.getVar('DESCRIPTION', localdata, True) or "."
> package_deb.bbclass: description = bb.data.getVar('DESCRIPTION', localdata, True) or "."
>
> meta/classes/package_ipk.bbclass: summary = bb.data.getVar('SUMMARY', localdata, True) or bb.data.getVar('DESCRIPTION', localdata, True) or "."
> package_ipk.bbclass: description = bb.data.getVar('DESCRIPTION', localdata, True) or "."
>
> meta/classes/package_rpm.bbclass: srcsummary = (bb.data.getVar('SUMMARY', d, True) or bb.data.getVar('DESCRIPTION', d, True) or ".")
> package_rpm.bbclass: srcdescription = bb.data.getVar('DESCRIPTION', d, True) or "."
So the summary is SUMMARY if set, or DESCRIPTION if set else "."
The description is DESCRIPTION if set else "."
which was done to fall back to the case where recipes just set
DESCRIPTION.
Cheers,
Richard
^ permalink raw reply
* Re: [CONSOLIDATED PULL 11/27] pulseaudio-0.9.23: inherit perlnative to work around build on host without XML/Parser.pm
From: Richard Purdie @ 2011-10-24 14:19 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <20111024132405.GB3602@jama.jama.net>
On Mon, 2011-10-24 at 15:24 +0200, Martin Jansa wrote:
> On Mon, Oct 24, 2011 at 02:15:57PM +0100, Richard Purdie wrote:
> > On Sun, 2011-10-23 at 11:26 -0700, Saul Wold wrote:
> > > From: Martin Jansa <Martin.Jansa@gmail.com>
> > >
> > > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > > ---
> > > .../pulseaudio/pulseaudio_0.9.23.bb | 2 +-
> > > 1 files changed, 1 insertions(+), 1 deletions(-)
> > >
> > > diff --git a/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb b/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
> > > index 33f5e15..4ac2418 100644
> > > --- a/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
> > > +++ b/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
> > > @@ -4,7 +4,7 @@ PR = "r5"
> > >
> > > DEPENDS += "gdbm speex"
> > >
> > > -inherit gettext
> > > +inherit gettext perlnative
> >
> > This doesn't look right. If we need xmlparser, we should state that in
> > DEPENDS. If that is added to DEPENDS, I'm not sure we still need the
> > inherit of perlnative?
>
> Yes I've forgot to put it in DEPENDS, khem sent version where he is
> adding this inherit and DEPENDs..
>
> but both are needed and only work arounds because build is calling perl
> (not env perl) and perlnative helps to put perl from perl-native before
> perl from host in PATH.
>
> Reported here:
> http://lists.linuxtogo.org/pipermail/openembedded-core/2011-October/011323.html
>
> And I've sent this as work around before I'll fill oe-core bug report or
> someone updates it to 1.1 and maybe fix it too.
I've taken Khem's version of this so that should help address this
problem.
Cheers,
Richard
^ permalink raw reply
* Re: [CONSOLIDATED PULL 20/27] libtool: Upgrade from 2.4 -> 2.4.2
From: Koen Kooi @ 2011-10-24 14:18 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <1319465445.25011.18.camel@ted>
Op 24 okt. 2011, om 16:10 heeft Richard Purdie het volgende geschreven:
> On Mon, 2011-10-24 at 15:37 +0200, Koen Kooi wrote:
>> Op 24 okt. 2011, om 15:34 heeft Richard Purdie het volgende geschreven:
>>
>>> On Sun, 2011-10-23 at 11:26 -0700, Saul Wold wrote:
>>>> From: Khem Raj <raj.khem@gmail.com>
>>>>
>>>> Adjust prefix.patch and delete resolve-sysroot.patch
>>>> since its already applied upstream
>>>>
>>>> Signed-off-by: Khem Raj <raj.khem@gmail.com>
>>>> ---
>>>> .../libtool/{libtool.inc => libtool-2.4.2.inc} | 26 +++++++++---
>>>> meta/recipes-devtools/libtool/libtool-2.4.inc | 13 ------
>>>> ...libtool-cross_2.4.bb => libtool-cross_2.4.2.bb} | 2 +-
>>>> ...btool-native_2.4.bb => libtool-native_2.4.2.bb} | 2 +-
>>>> ...nativesdk_2.4.bb => libtool-nativesdk_2.4.2.bb} | 2 +-
>>>> meta/recipes-devtools/libtool/libtool/prefix.patch | 46 ++++++++++----------
>>>> .../libtool/libtool/resolve-sysroot.patch | 42 ------------------
>>>> .../libtool/{libtool_2.4.bb => libtool_2.4.2.bb} | 2 +-
>>>> 8 files changed, 47 insertions(+), 88 deletions(-)
>>>> rename meta/recipes-devtools/libtool/{libtool.inc => libtool-2.4.2.inc} (57%)
>>>> delete mode 100644 meta/recipes-devtools/libtool/libtool-2.4.inc
>>>> rename meta/recipes-devtools/libtool/{libtool-cross_2.4.bb => libtool-cross_2.4.2.bb} (98%)
>>>> rename meta/recipes-devtools/libtool/{libtool-native_2.4.bb => libtool-native_2.4.2.bb} (96%)
>>>> rename meta/recipes-devtools/libtool/{libtool-nativesdk_2.4.bb => libtool-nativesdk_2.4.2.bb} (97%)
>>>> delete mode 100644 meta/recipes-devtools/libtool/libtool/resolve-sysroot.patch
>>>> rename meta/recipes-devtools/libtool/{libtool_2.4.bb => libtool_2.4.2.bb} (94%)
>>>>
>>>> diff --git a/meta/recipes-devtools/libtool/libtool.inc b/meta/recipes-devtools/libtool/libtool-2.4.2.inc
>>>> similarity index 57%
>>>> rename from meta/recipes-devtools/libtool/libtool.inc
>>>> rename to meta/recipes-devtools/libtool/libtool-2.4.2.inc
>>>> index ef9095b..1f652ef 100644
>>>> --- a/meta/recipes-devtools/libtool/libtool.inc
>>>> +++ b/meta/recipes-devtools/libtool/libtool-2.4.2.inc
>>>> @@ -1,4 +1,3 @@
>>>> -SUMMARY = "Generic library support script"
>>>
>>> Why drop the SUMMARY field?
>>
>> What's the difference between SUMMARY and DESCRIPTION? And what happens if both are set?
>
> SUMMARY is a one line 74? character summary of the package, DESCRIPTION
> is a multiple line stream of text containing a more verbose description.
> What happens to the data is package backend specific, I know RPM has
> uses for both. There was definitely discussion about this on the mailing
> list at the time, I'm not sure what if anything made it into the manuals
> but if its not there it should be added.
It seems to get OR'd:
meta/classes/package_deb.bbclass: summary = bb.data.getVar('SUMMARY', localdata, True) or bb.data.getVar('DESCRIPTION', localdata, True) or "."
package_deb.bbclass: description = bb.data.getVar('DESCRIPTION', localdata, True) or "."
meta/classes/package_ipk.bbclass: summary = bb.data.getVar('SUMMARY', localdata, True) or bb.data.getVar('DESCRIPTION', localdata, True) or "."
package_ipk.bbclass: description = bb.data.getVar('DESCRIPTION', localdata, True) or "."
meta/classes/package_rpm.bbclass: srcsummary = (bb.data.getVar('SUMMARY', d, True) or bb.data.getVar('DESCRIPTION', d, True) or ".")
package_rpm.bbclass: srcdescription = bb.data.getVar('DESCRIPTION', d, True) or "."
regards,
Koen
^ permalink raw reply
* Re: [PATCH 2/2] pulseaudio: inherit perlnative
From: Richard Purdie @ 2011-10-24 14:17 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <1319380267-29794-2-git-send-email-raj.khem@gmail.com>
On Sun, 2011-10-23 at 07:31 -0700, Khem Raj wrote:
> manpage generatition uses xmltoman utility
> which inturn uses xml-parser. So we add
> libxml-parser-perl-native to DEPENDS and also
> inherit perlnative so it does not use the one
> from build host
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> .../pulseaudio/pulseaudio_0.9.23.bb | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
Merged to master, thanks.
Richard
^ permalink raw reply
* Re: [CONSOLIDATED PULL 11/27] pulseaudio-0.9.23: inherit perlnative to work around build on host without XML/Parser.pm
From: Richard Purdie @ 2011-10-24 14:15 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <91421698-3BCA-4B52-8C7C-AD842A2E62FB@dominion.thruhere.net>
On Mon, 2011-10-24 at 15:19 +0200, Koen Kooi wrote:
> Op 24 okt. 2011, om 15:15 heeft Richard Purdie het volgende geschreven:
>
> > On Sun, 2011-10-23 at 11:26 -0700, Saul Wold wrote:
> >> From: Martin Jansa <Martin.Jansa@gmail.com>
> >>
> >> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> >> ---
> >> .../pulseaudio/pulseaudio_0.9.23.bb | 2 +-
> >> 1 files changed, 1 insertions(+), 1 deletions(-)
> >>
> >> diff --git a/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb b/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
> >> index 33f5e15..4ac2418 100644
> >> --- a/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
> >> +++ b/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
> >> @@ -4,7 +4,7 @@ PR = "r5"
> >>
> >> DEPENDS += "gdbm speex"
> >>
> >> -inherit gettext
> >> +inherit gettext perlnative
> >
> > This doesn't look right. If we need xmlparser, we should state that in
> > DEPENDS. If that is added to DEPENDS, I'm not sure we still need the
> > inherit of perlnative?
>
> If you need xmlparser during the build you almost always need the
> perlnative wrapper as well :(
I was under the impression that we'd fixed most of those issues :/. It
could well be a valid dependency in this case so I'll take the patch
with the added DEPENDS.
Cheers,
Richard
^ permalink raw reply
* Re: [CONSOLIDATED PULL 20/27] libtool: Upgrade from 2.4 -> 2.4.2
From: Richard Purdie @ 2011-10-24 14:10 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <3D2F5FE5-B1DC-44C4-8A5A-E81C41F00125@dominion.thruhere.net>
On Mon, 2011-10-24 at 15:37 +0200, Koen Kooi wrote:
> Op 24 okt. 2011, om 15:34 heeft Richard Purdie het volgende geschreven:
>
> > On Sun, 2011-10-23 at 11:26 -0700, Saul Wold wrote:
> >> From: Khem Raj <raj.khem@gmail.com>
> >>
> >> Adjust prefix.patch and delete resolve-sysroot.patch
> >> since its already applied upstream
> >>
> >> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> >> ---
> >> .../libtool/{libtool.inc => libtool-2.4.2.inc} | 26 +++++++++---
> >> meta/recipes-devtools/libtool/libtool-2.4.inc | 13 ------
> >> ...libtool-cross_2.4.bb => libtool-cross_2.4.2.bb} | 2 +-
> >> ...btool-native_2.4.bb => libtool-native_2.4.2.bb} | 2 +-
> >> ...nativesdk_2.4.bb => libtool-nativesdk_2.4.2.bb} | 2 +-
> >> meta/recipes-devtools/libtool/libtool/prefix.patch | 46 ++++++++++----------
> >> .../libtool/libtool/resolve-sysroot.patch | 42 ------------------
> >> .../libtool/{libtool_2.4.bb => libtool_2.4.2.bb} | 2 +-
> >> 8 files changed, 47 insertions(+), 88 deletions(-)
> >> rename meta/recipes-devtools/libtool/{libtool.inc => libtool-2.4.2.inc} (57%)
> >> delete mode 100644 meta/recipes-devtools/libtool/libtool-2.4.inc
> >> rename meta/recipes-devtools/libtool/{libtool-cross_2.4.bb => libtool-cross_2.4.2.bb} (98%)
> >> rename meta/recipes-devtools/libtool/{libtool-native_2.4.bb => libtool-native_2.4.2.bb} (96%)
> >> rename meta/recipes-devtools/libtool/{libtool-nativesdk_2.4.bb => libtool-nativesdk_2.4.2.bb} (97%)
> >> delete mode 100644 meta/recipes-devtools/libtool/libtool/resolve-sysroot.patch
> >> rename meta/recipes-devtools/libtool/{libtool_2.4.bb => libtool_2.4.2.bb} (94%)
> >>
> >> diff --git a/meta/recipes-devtools/libtool/libtool.inc b/meta/recipes-devtools/libtool/libtool-2.4.2.inc
> >> similarity index 57%
> >> rename from meta/recipes-devtools/libtool/libtool.inc
> >> rename to meta/recipes-devtools/libtool/libtool-2.4.2.inc
> >> index ef9095b..1f652ef 100644
> >> --- a/meta/recipes-devtools/libtool/libtool.inc
> >> +++ b/meta/recipes-devtools/libtool/libtool-2.4.2.inc
> >> @@ -1,4 +1,3 @@
> >> -SUMMARY = "Generic library support script"
> >
> > Why drop the SUMMARY field?
>
> What's the difference between SUMMARY and DESCRIPTION? And what happens if both are set?
SUMMARY is a one line 74? character summary of the package, DESCRIPTION
is a multiple line stream of text containing a more verbose description.
What happens to the data is package backend specific, I know RPM has
uses for both. There was definitely discussion about this on the mailing
list at the time, I'm not sure what if anything made it into the manuals
but if its not there it should be added.
Cheers,
Richard
^ permalink raw reply
* Re: [CONSOLIDATED PULL 00/27] Various Updates and fixes
From: Richard Purdie @ 2011-10-24 13:59 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <cover.1319394187.git.sgw@linux.intel.com>
On Sun, 2011-10-23 at 11:26 -0700, Saul Wold wrote:
> This pull requests adds some new recipes for supporting building
> oe-core with oe-core, also various patches and updates.
I've taken a chunk of this but there were some issues.
> I also included the MACHINE_KERNEL_PR change from Dmitry per my
> reading of the TSC Notes.
That isn't what I understood from the TSC meeting and this patch isn't
getting merged.
> Cliff Brake (1):
> squashfs-tools: add recipe
>
>Khem Raj (7):
> tcmode-default.inc: Add TRANSLATED_TARGET_ARCH suffix to
> binutils-cross-canadian
> binutils-cross-canadian: Point sysroot to correct location
> gcc-configure-sdk: Point sysroot to correct location
> xserver-xorg: Add mesa-dri to depends instead of virtual/libgl
> gcc-4.6: Backport fix for PR32219
> coreutils: Upgrade recipe 8.12 -> 8.14
>
>Martin Jansa (5):
> apr: add native support
> neon: add native support
> apr-util: add native support
> subversion-1.6.15: add native support too
> default-providers: switch virtual/libgl from mesa-xlib to mesa-dri
>
> Nitin A Kamble (2):
> tcl: upgrade from 8.5.9 to 8.5.10
> perl: upgrade from 5.12.3 to 5.14.2
>
> Otavio Salvador (4):
> bootimg.bbclass: add support to disable HDD image building
> useradd.bbclass: check if a group already exists manually
> base-passwd: move initial criation of group and passwd to preinst
> dbus: use useradd class to allow use in read-only filesystems
>
> Saul Wold (2):
> texi2html: Added recipe from OE
> oprofile: Update to 0.9.7 and convert cvs->git
The above were merged.
>Saul Wold (3):
> wget: Add recipe from OE
> abiword: convert to svn
> perl: remove debug set -x; pwd
I squashed the perl fix into the perl commit, I've commented on the
other two.
>Dmitry Eremin-Solenikov (1):
> kernel.bbclass: respect MACHINE_KERNEL_PR
>
>Khem Raj (1):
> libtool: Upgrade from 2.4 -> 2.4.2
>
>Martin Jansa (2):
> pulseaudio-0.9.23: inherit perlnative to work around build on host
> without XML/Parser.pm
> subversion: add 1.7.0 with native support and negative D_P for now
I've also given feedback on these. I'm holding off subversion 1.7 until
we can come up with a good plan for handling it, it likely needs bitbake
fetcher support.
Cheers,
Richard
^ permalink raw reply
* Re: [CONSOLIDATED PULL 20/27] libtool: Upgrade from 2.4 -> 2.4.2
From: Koen Kooi @ 2011-10-24 13:37 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <1319463290.25011.10.camel@ted>
Op 24 okt. 2011, om 15:34 heeft Richard Purdie het volgende geschreven:
> On Sun, 2011-10-23 at 11:26 -0700, Saul Wold wrote:
>> From: Khem Raj <raj.khem@gmail.com>
>>
>> Adjust prefix.patch and delete resolve-sysroot.patch
>> since its already applied upstream
>>
>> Signed-off-by: Khem Raj <raj.khem@gmail.com>
>> ---
>> .../libtool/{libtool.inc => libtool-2.4.2.inc} | 26 +++++++++---
>> meta/recipes-devtools/libtool/libtool-2.4.inc | 13 ------
>> ...libtool-cross_2.4.bb => libtool-cross_2.4.2.bb} | 2 +-
>> ...btool-native_2.4.bb => libtool-native_2.4.2.bb} | 2 +-
>> ...nativesdk_2.4.bb => libtool-nativesdk_2.4.2.bb} | 2 +-
>> meta/recipes-devtools/libtool/libtool/prefix.patch | 46 ++++++++++----------
>> .../libtool/libtool/resolve-sysroot.patch | 42 ------------------
>> .../libtool/{libtool_2.4.bb => libtool_2.4.2.bb} | 2 +-
>> 8 files changed, 47 insertions(+), 88 deletions(-)
>> rename meta/recipes-devtools/libtool/{libtool.inc => libtool-2.4.2.inc} (57%)
>> delete mode 100644 meta/recipes-devtools/libtool/libtool-2.4.inc
>> rename meta/recipes-devtools/libtool/{libtool-cross_2.4.bb => libtool-cross_2.4.2.bb} (98%)
>> rename meta/recipes-devtools/libtool/{libtool-native_2.4.bb => libtool-native_2.4.2.bb} (96%)
>> rename meta/recipes-devtools/libtool/{libtool-nativesdk_2.4.bb => libtool-nativesdk_2.4.2.bb} (97%)
>> delete mode 100644 meta/recipes-devtools/libtool/libtool/resolve-sysroot.patch
>> rename meta/recipes-devtools/libtool/{libtool_2.4.bb => libtool_2.4.2.bb} (94%)
>>
>> diff --git a/meta/recipes-devtools/libtool/libtool.inc b/meta/recipes-devtools/libtool/libtool-2.4.2.inc
>> similarity index 57%
>> rename from meta/recipes-devtools/libtool/libtool.inc
>> rename to meta/recipes-devtools/libtool/libtool-2.4.2.inc
>> index ef9095b..1f652ef 100644
>> --- a/meta/recipes-devtools/libtool/libtool.inc
>> +++ b/meta/recipes-devtools/libtool/libtool-2.4.2.inc
>> @@ -1,4 +1,3 @@
>> -SUMMARY = "Generic library support script"
>
> Why drop the SUMMARY field?
What's the difference between SUMMARY and DESCRIPTION? And what happens if both are set?
regards,
Koen
^ permalink raw reply
* Re: [CONSOLIDATED PULL 20/27] libtool: Upgrade from 2.4 -> 2.4.2
From: Richard Purdie @ 2011-10-24 13:34 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <d546fdc94cb627040c657facc23f00406967c838.1319394187.git.sgw@linux.intel.com>
On Sun, 2011-10-23 at 11:26 -0700, Saul Wold wrote:
> From: Khem Raj <raj.khem@gmail.com>
>
> Adjust prefix.patch and delete resolve-sysroot.patch
> since its already applied upstream
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> .../libtool/{libtool.inc => libtool-2.4.2.inc} | 26 +++++++++---
> meta/recipes-devtools/libtool/libtool-2.4.inc | 13 ------
> ...libtool-cross_2.4.bb => libtool-cross_2.4.2.bb} | 2 +-
> ...btool-native_2.4.bb => libtool-native_2.4.2.bb} | 2 +-
> ...nativesdk_2.4.bb => libtool-nativesdk_2.4.2.bb} | 2 +-
> meta/recipes-devtools/libtool/libtool/prefix.patch | 46 ++++++++++----------
> .../libtool/libtool/resolve-sysroot.patch | 42 ------------------
> .../libtool/{libtool_2.4.bb => libtool_2.4.2.bb} | 2 +-
> 8 files changed, 47 insertions(+), 88 deletions(-)
> rename meta/recipes-devtools/libtool/{libtool.inc => libtool-2.4.2.inc} (57%)
> delete mode 100644 meta/recipes-devtools/libtool/libtool-2.4.inc
> rename meta/recipes-devtools/libtool/{libtool-cross_2.4.bb => libtool-cross_2.4.2.bb} (98%)
> rename meta/recipes-devtools/libtool/{libtool-native_2.4.bb => libtool-native_2.4.2.bb} (96%)
> rename meta/recipes-devtools/libtool/{libtool-nativesdk_2.4.bb => libtool-nativesdk_2.4.2.bb} (97%)
> delete mode 100644 meta/recipes-devtools/libtool/libtool/resolve-sysroot.patch
> rename meta/recipes-devtools/libtool/{libtool_2.4.bb => libtool_2.4.2.bb} (94%)
>
> diff --git a/meta/recipes-devtools/libtool/libtool.inc b/meta/recipes-devtools/libtool/libtool-2.4.2.inc
> similarity index 57%
> rename from meta/recipes-devtools/libtool/libtool.inc
> rename to meta/recipes-devtools/libtool/libtool-2.4.2.inc
> index ef9095b..1f652ef 100644
> --- a/meta/recipes-devtools/libtool/libtool.inc
> +++ b/meta/recipes-devtools/libtool/libtool-2.4.2.inc
> @@ -1,4 +1,3 @@
> -SUMMARY = "Generic library support script"
Why drop the SUMMARY field?
> DESCRIPTION = "This is GNU libtool, a generic library support script. \
> Libtool hides the complexity of generating special library types \
> (such as shared libraries) behind a consistent interface."
> @@ -8,21 +7,36 @@ LICENSE = "GPLv2 & LGPLv2.1"
> LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
> file://libltdl/COPYING.LIB;md5=e3eda01d9815f8d24aae2dbd89b68b06"
>
> +INC_PR = "r0"
> +
> SRC_URI = "${GNU_MIRROR}/libtool/libtool-${PV}.tar.gz \
> file://trailingslash.patch \
> file://prefix-manpage-fix.patch \
> file://rename-with-sysroot.patch \
> - file://resolve-sysroot.patch \
> file://use-sysroot-in-libpath.patch \
> file://fix-final-rpath.patch \
> file://avoid_absolute_paths_for_general_utils.patch \
> - file://fix-rpath.patch "
> + file://fix-rpath.patch \
> + "
> +
> +SRC_URI[md5sum] = "d2f3b7d4627e69e13514a40e72a24d50"
> +SRC_URI[sha256sum] = "b38de44862a987293cd3d8dfae1c409d514b6c4e794ebc93648febf9afc38918"
>
> do_compile_prepend () {
> - # Sometimes this file doesn't get rebuilt, force the issue
> - rm -f ${S}/libltdl/config/ltmain.sh
> - make libltdl/config/ltmain.sh
> + # Sometimes this file doesn't get rebuilt, force the issue
> + rm -f ${S}/libltdl/config/ltmain.sh
> + make libltdl/config/ltmain.sh
> }
Unintended indentation changes?
> inherit autotools
> EXTRA_AUTORECONF = "--exclude=libtoolize"
> +
> +DEPENDS = "libtool-native"
> +
> +PACKAGES =+ "libltdl libltdl-dev libltdl-dbg"
> +FILES_${PN} += "${datadir}/aclocal*"
> +FILES_libltdl = "${libdir}/libltdl.so.*"
> +FILES_libltdl-dev = "${libdir}/libltdl.* ${includedir}/ltdl.h"
> +FILES_libltdl-dbg = "${libdir}/.debug/"
> +
> +EXTRA_OECONF = "--with-sysroot"
> diff --git a/meta/recipes-devtools/libtool/libtool-2.4.inc b/meta/recipes-devtools/libtool/libtool-2.4.inc
> deleted file mode 100644
> index e3d17b7..0000000
> --- a/meta/recipes-devtools/libtool/libtool-2.4.inc
> +++ /dev/null
> @@ -1,13 +0,0 @@
> -require libtool.inc
> -DEPENDS = "libtool-native"
> -
> -PACKAGES =+ "libltdl libltdl-dev libltdl-dbg"
> -FILES_${PN} += "${datadir}/aclocal*"
> -FILES_libltdl = "${libdir}/libltdl.so.*"
> -FILES_libltdl-dev = "${libdir}/libltdl.* ${includedir}/ltdl.h"
> -FILES_libltdl-dbg = "${libdir}/.debug/"
> -
> -SRC_URI[md5sum] = "b32b04148ecdd7344abc6fe8bd1bb021"
> -SRC_URI[sha256sum] = "13df57ab63a94e196c5d6e95d64e53262834fe780d5e82c28f177f9f71ddf62e"
> -
> -EXTRA_OECONF = "--with-sysroot"
> \ No newline at end of file
> diff --git a/meta/recipes-devtools/libtool/libtool-cross_2.4.bb b/meta/recipes-devtools/libtool/libtool-cross_2.4.2.bb
> similarity index 98%
> rename from meta/recipes-devtools/libtool/libtool-cross_2.4.bb
> rename to meta/recipes-devtools/libtool/libtool-cross_2.4.2.bb
> index 6d512b1..b7fe851 100644
> --- a/meta/recipes-devtools/libtool/libtool-cross_2.4.bb
> +++ b/meta/recipes-devtools/libtool/libtool-cross_2.4.2.bb
> @@ -1,6 +1,6 @@
> require libtool-${PV}.inc
>
> -PR = "r4"
> +PR = "${INC_PR}.0"
> PACKAGES = ""
> SRC_URI += "file://prefix.patch"
No mention of conversion to INC_PR in the commit message. I'm not sure
this is worth doing at this point considering the need to find a better
way to automate PR bumping.
Cheers,
Richard
^ permalink raw reply
* Re: [CONSOLIDATED PULL 26/27] abiword: convert to svn
From: Saul Wold @ 2011-10-24 13:31 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer; +Cc: Koen Kooi
In-Reply-To: <884DC19F-D167-41B9-B5E6-62A959BE99CB@dominion.thruhere.net>
On 10/24/2011 03:18 PM, Koen Kooi wrote:
>
> Op 24 okt. 2011, om 15:14 heeft Richard Purdie het volgende geschreven:
>
>> On Sun, 2011-10-23 at 11:27 -0700, Saul Wold wrote:
>>> Signed-off-by: Saul Wold<sgw@linux.intel.com>
>>> ---
>>> meta-demoapps/recipes-gnome/abiword/abiword.inc | 4 ++--
>>> meta-demoapps/recipes-gnome/abiword/abiword_cvs.bb | 10 ----------
>>> meta-demoapps/recipes-gnome/abiword/abiword_svn.bb | 10 ++++++++++
>>> 3 files changed, 12 insertions(+), 12 deletions(-)
>>> delete mode 100644 meta-demoapps/recipes-gnome/abiword/abiword_cvs.bb
>>> create mode 100644 meta-demoapps/recipes-gnome/abiword/abiword_svn.bb
>>>
>>> diff --git a/meta-demoapps/recipes-gnome/abiword/abiword.inc b/meta-demoapps/recipes-gnome/abiword/abiword.inc
>>> index b1b0f67..2b34a7a 100644
>>> --- a/meta-demoapps/recipes-gnome/abiword/abiword.inc
>>> +++ b/meta-demoapps/recipes-gnome/abiword/abiword.inc
>>> @@ -13,8 +13,8 @@ RRECOMMENDS_${PN} = "glibc-gconv-ibm850 glibc-gconv-cp1252 \
>>> RELURI = "http://www.abiword.org/downloads/abiword/${PV}/source/abiword-${PV}.tar.gz"
>>> RELSRC = "${WORKDIR}/abiword-${PV}/abi"
>>>
>>> -CVSURI = "cvs://anoncvs:anoncvs@anoncvs.abisource.com/cvsroot;module=abi"
>>> -CVSSRC = "${WORKDIR}/abi"
>>> +SVNURI = "cvs://svn.abisource.com/abiword/trunk;module=abiword;proto=http"
>>> +SVNSRC = "${WORKDIR}/abi"
>>>
>> Er, its still using cvs:// ?!
>
> The whole abiword section is outdated, it has 2.5.2 which was released on 21-Aug-2007, latest is 2.8.6 released on 13-Jun-2010. I have an uncommited update in meta-oe to update abiword to 2.8.6, need to clean that up.
>
I will defer my patch for what Koen has pending then for meta-oe,
probably the better place for it anyways, it should be removed from the
meta-demoapps.
Sau!
> regards,
>
> Koen
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
^ permalink raw reply
* Re: [CONSOLIDATED PULL 23/27] wget: Add recipe from OE
From: Richard Purdie @ 2011-10-24 13:25 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <2c5ad68e4c5f715c91760839f482deff44fa9f06.1319394187.git.sgw@linux.intel.com>
> diff --git a/meta/recipes-extended/wget/wget.inc b/meta/recipes-extended/wget/wget.inc
> new file mode 100644
> index 0000000..c0d9ba9
> --- /dev/null
> +++ b/meta/recipes-extended/wget/wget.inc
> @@ -0,0 +1,40 @@
> +DESCRIPTION = "A console URL download utility featuring HTTP, FTP, and more."
> +SECTION = "console/network"
> +DEPENDS = ""
> +DEPENDS_shr = "gnutls"
Hmm. See below.
> +LICENSE = "GPL"
Which GPL?
> +LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
> +
> +
> +INC_PR = "r9"
> +
> +S = "${WORKDIR}/wget-${PV}"
> +
> +inherit autotools gettext
> +
> +# Disable checking for SSL since that searches the system paths
> +EXTRA_OECONF = "--enable-ipv6 --without-ssl"
> +
> +# Enable SSL it's usefull
> +EXTRA_OECONF_shr = "--enable-ipv6 --with-ssl=gnutls"
> +# The unslung kernel does not support ipv6
> +EXTRA_OECONF_unslung = "--without-ssl"
> +# SlugOS kernels do not support ipv6. Can be loaded as a module.
> +EXTRA_OECONF_slugos = "--without-ssl"
So we go to interesting lengths here to customise this under a variety
of conditions...
> +inherit autotools update-alternatives
> +
> +EXTRA_OECONF = "--with-libc"
... and then we overwrite half of it here. This needs cleaning up before
it can merge. We could convert it to make these config items
PACKAGECONFIG if people need to customise this.
>+do_configure() {
>+ autotools_do_configure
>+}
This looks rather pointless?
Cheers,
Richard
^ permalink raw reply
* Re: [CONSOLIDATED PULL 11/27] pulseaudio-0.9.23: inherit perlnative to work around build on host without XML/Parser.pm
From: Martin Jansa @ 2011-10-24 13:24 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <1319462157.25011.1.camel@ted>
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
On Mon, Oct 24, 2011 at 02:15:57PM +0100, Richard Purdie wrote:
> On Sun, 2011-10-23 at 11:26 -0700, Saul Wold wrote:
> > From: Martin Jansa <Martin.Jansa@gmail.com>
> >
> > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > ---
> > .../pulseaudio/pulseaudio_0.9.23.bb | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb b/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
> > index 33f5e15..4ac2418 100644
> > --- a/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
> > +++ b/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
> > @@ -4,7 +4,7 @@ PR = "r5"
> >
> > DEPENDS += "gdbm speex"
> >
> > -inherit gettext
> > +inherit gettext perlnative
>
> This doesn't look right. If we need xmlparser, we should state that in
> DEPENDS. If that is added to DEPENDS, I'm not sure we still need the
> inherit of perlnative?
Yes I've forgot to put it in DEPENDS, khem sent version where he is
adding this inherit and DEPENDs..
but both are needed and only work arounds because build is calling perl
(not env perl) and perlnative helps to put perl from perl-native before
perl from host in PATH.
Reported here:
http://lists.linuxtogo.org/pipermail/openembedded-core/2011-October/011323.html
And I've sent this as work around before I'll fill oe-core bug report or
someone updates it to 1.1 and maybe fix it too.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
^ permalink raw reply
* Re: [CONSOLIDATED PULL 11/27] pulseaudio-0.9.23: inherit perlnative to work around build on host without XML/Parser.pm
From: Koen Kooi @ 2011-10-24 13:19 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <1319462157.25011.1.camel@ted>
Op 24 okt. 2011, om 15:15 heeft Richard Purdie het volgende geschreven:
> On Sun, 2011-10-23 at 11:26 -0700, Saul Wold wrote:
>> From: Martin Jansa <Martin.Jansa@gmail.com>
>>
>> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
>> ---
>> .../pulseaudio/pulseaudio_0.9.23.bb | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb b/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
>> index 33f5e15..4ac2418 100644
>> --- a/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
>> +++ b/meta/recipes-multimedia/pulseaudio/pulseaudio_0.9.23.bb
>> @@ -4,7 +4,7 @@ PR = "r5"
>>
>> DEPENDS += "gdbm speex"
>>
>> -inherit gettext
>> +inherit gettext perlnative
>
> This doesn't look right. If we need xmlparser, we should state that in
> DEPENDS. If that is added to DEPENDS, I'm not sure we still need the
> inherit of perlnative?
If you need xmlparser during the build you almost always need the perlnative wrapper as well :(
regards,
Koen
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox