* where is the binary file
From: Ni Qingliang @ 2011-10-24 1:50 UTC (permalink / raw)
To: openembedded-core
Hello All:
I have installed some binary file into the /lib/xxx directory (used for
FPGA), and can find them in the 'package' dir of the package. but can't
find any in the 'packages-split' dir of it (and also not in the final
image).
Does anyone can tell me what happened?
--
Yi Qingliang
niqingliang@insigma.com.cn
http://niqingliang2003.wordpress.com
^ permalink raw reply
* Re: where is the binary file
From: Ni Qingliang @ 2011-10-24 2:31 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <1319421032.10032.22.camel@localhost.localdomain>
I have found out it!
the PN is tinbox, and I have installed the binary to '/usr/lib/tin/'
the bitbake will process '/lib/${PN}/' and '/usr/lib/${PN}', skipped my
own directory.
after change to /usr/lib/${PN}, it works!
On Mon, 2011-10-24 at 09:50 +0800, Ni Qingliang wrote:
> Hello All:
>
> I have installed some binary file into the /lib/xxx directory (used for
> FPGA), and can find them in the 'package' dir of the package. but can't
> find any in the 'packages-split' dir of it (and also not in the final
> image).
>
>
> Does anyone can tell me what happened?
>
>
>
> --
> Yi Qingliang
> niqingliang@insigma.com.cn
> http://niqingliang2003.wordpress.com
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Yi Qingliang
niqingliang@insigma.com.cn
http://niqingliang2003.wordpress.com
^ permalink raw reply
* [PATCH 0/1] qmmp: update to 0.5.2
From: Xiaofeng Yan @ 2011-10-24 3:37 UTC (permalink / raw)
To: openembedded-core
From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
Hi saul,
Use do_split_package for each grouping and name them correctly besides updating package.
The format to name plugins of qmmp:
qmmp-plugin-<group>-<library> with the Description: Qmmp <Group> plugin for %s"
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: xiaofeng/qmmp_update
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/qmmp_update
Thanks,
Xiaofeng Yan <xiaofeng.yan@windriver.com>
---
Xiaofeng Yan (1):
qmmp: update to 0.5.2
meta/recipes-qt/qt-apps/qmmp_0.5.2.bb | 60 +++++++++++++++++++++++++++++++++
1 files changed, 60 insertions(+), 0 deletions(-)
create mode 100644 meta/recipes-qt/qt-apps/qmmp_0.5.2.bb
^ permalink raw reply
* [PATCH 1/1] qmmp: update to 0.5.2
From: Xiaofeng Yan @ 2011-10-24 3:37 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <cover.1319427162.git.xiaofeng.yan@windriver.com>
From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
Use do_split_package for each grouping and name them correctly besides updating package.
The format to name plugins of qmmp:
qmmp-plugin-<group>-<library> with the Description: Qmmp <Group> plugin for %s"
Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com>
---
meta/recipes-qt/qt-apps/qmmp_0.5.2.bb | 60 +++++++++++++++++++++++++++++++++
1 files changed, 60 insertions(+), 0 deletions(-)
create mode 100644 meta/recipes-qt/qt-apps/qmmp_0.5.2.bb
diff --git a/meta/recipes-qt/qt-apps/qmmp_0.5.2.bb b/meta/recipes-qt/qt-apps/qmmp_0.5.2.bb
new file mode 100644
index 0000000..58dd825
--- /dev/null
+++ b/meta/recipes-qt/qt-apps/qmmp_0.5.2.bb
@@ -0,0 +1,60 @@
+dESCRIPTION = "Qmmp (Qt-based Multimedia Player) is an audio-player, written with help of Qt library"
+HOMEPAGE = "http://qmmp.ylsoftware.com"
+LICENSE = "GPLv2"
+LIC_FILES_CHKSUM = "file://COPYING;md5=393a5ca445f6965873eca0259a17f833"
+SECTION = "multimedia"
+
+PR = "r4"
+
+PROVIDES = "qmmp"
+DEPENDS = "qt4-x11-free taglib libmad libvorbis libogg alsa-lib"
+RDEPENDS_${PN} += "taglib alsa-lib libmad curl"
+
+SRC_URI = "http://qmmp.ylsoftware.com/files/${BPN}-${PV}.tar.bz2"
+
+SRC_URI[md5sum] = "20852f3cce3471bfc5affa9b2e947dc6"
+SRC_URI[sha256sum] = "6391dec020d2a381d7f4b7890fae6c49eadf88b3c9aef571fe3c5e96140822ec"
+
+
+PARALLEL_MAKE = ""
+
+inherit qmake2 cmake package
+
+export EXTRA_OECMAKE = "-DQT_QMAKE_EXECUTABLE=${OE_QMAKE_QMAKE} \
+ -DQT_LRELEASE_EXECUTABLE=${OE_QMAKE_LRELEASE} \
+ -DQT_MOC_EXECUTABLE=${OE_QMAKE_MOC} \
+ -DQT_UIC_EXECUTABLE=${OE_QMAKE_UIC} \
+ -DQT_RCC_EXECUTABLE=${OE_QMAKE_RCC} \
+ -DQT_LIBRARY_DIR=${OE_QMAKE_LIBDIR_QT} \
+ -DQT_HEADERS_DIR=${OE_QMAKE_INCDIR_QT} \
+ -DQT_QTCORE_INCLUDE_DIR=${OE_QMAKE_INCDIR_QT}/QtCore \
+ "
+PACKAGES_DYNAMIC = "qmmp-plugin-* "
+
+
+python populate_packages_prepend () {
+ import os
+ qmmp_libdir = bb.data.expand('${libdir}/qmmp', d)
+ gd = bb.data.expand('${D}/${libdir}/qmmp', d)
+ plug_dirs = os.listdir(gd)
+
+ for plug_dir in plug_dirs:
+ g_plug_dir = os.path.join(qmmp_libdir,plug_dir)
+ do_split_packages(d, g_plug_dir, '^lib(.*)\.so$', 'qmmp-plugin-' + plug_dir + '-%s', 'Qmmp' + plug_dir + 'plugin for %s')
+
+
+
+}
+
+FILES_${PN} = "\
+ ${bindir}/qmmp \
+ ${libdir}/lib*${SOLIBS} \
+ ${datadir}/icons/* \
+ ${datadir}/qmmp/images/* \
+ ${datadir}/applications/* \
+ "
+
+FILES_${PN}-dbg += "\
+ ${libdir}/qmmp/*/.debug/* \
+ "
+
--
1.7.0.4
^ permalink raw reply related
* Re: [PATCH 3/3 v2] distro_tracking_fields: update packages tracking fields
From: wenzong fan @ 2011-10-24 5:57 UTC (permalink / raw)
To: Saul Wold; +Cc: Patches and discussions about the oe-core layer
In-Reply-To: <4E9FD119.4030307@intel.com>
On 10/20/2011 03:43 PM, Saul Wold wrote:
> On 10/19/2011 10:59 PM, wenzong.fan@windriver.com wrote:
>> 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 abc2cbf..a7c2db5 100644
>> --- a/meta/conf/distro/include/distro_tracking_fields.inc
>> +++ b/meta/conf/distro/include/distro_tracking_fields.inc
>> @@ -5914,6 +5914,18 @@ RECIPE_LATEST_RELEASE_DATE_pn-gettext = "Jun
>> 06, 2010"
>> RECIPE_LAST_UPDATE_pn-gettext = "May 24, 2011"
>> RECIPE_MANUAL_CHECK_DATE_pn-gettext = "Sep 29, 2011"
>>
>> +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 = "June 24, 2011"
> You just updated this package, so this should be today's date
> Do you mean theis to be RECIPE_LATEST_RELEASE_DATE of June? Is that
> when the 3.1.6 tarball was released?
Oh, sorry I misunderstand the '_LAST_', June is the last update time for
previous version 3.1.5.
I'll fix that.
Thanks
Wenzong
>
>> +RECIPE_MANUAL_CHECK_DATE_pn-ccache = "October 11, 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 = "May 24, 2011"
> Same as above!
>
> Sau!
>> +RECIPE_MANUAL_CHECK_DATE_pn-chkconfig = "October 11, 2011"
>> +
>> RECIPE_STATUS_pn-pseudo = "green"
>> RECIPE_LATEST_VERSION_pn-pseudo = "1.1.1"
>> RECIPE_LAST_UPDATE_pn-pseudo = "Jun 06, 2011"
>
>
^ permalink raw reply
* Re: [review/test 3/5] python, python-native: upgrade from 2.6.6 to 2.7.2
From: Martin Jansa @ 2011-10-24 6:05 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE94E33A6EBB@orsmsx504.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 5485 bytes --]
On Sun, Oct 23, 2011 at 05:07:30PM -0700, Kamble, Nitin A wrote:
> Hi Martin,
> I tested python inside qemux86-64 and it was working fine. I could test small python scripts working as expected.
> Thanks,
> Nitin
For me it builds only after I've upgraded host's glibc version to 2.14
while using eglibc-2.14 for qemux86-64.
When I had glibc-2.13 on host and eglibc-2.14 for qemux86-64 it fails
like this:
/OE/shr-core/tmp/sysroots/x86_64-linux/usr/bin/python: /lib64/libc.so.6:
version `GLIBC_2.14' not found (required by
/OE/shr-core/tmp/work/x86_64-oe-linux/python-2.7.2-r0.0/Python-2.7.2/libpython2.7.so.1.0)
as reported here:
http://lists.linuxtogo.org/pipermail/openembedded-core/2011-October/011230.html
>
>
> > -----Original Message-----
> > From: Martin Jansa [mailto:martin.jansa@gmail.com]
> > Sent: Saturday, October 22, 2011 11:28 PM
> > To: Kamble, Nitin A
> > Cc: Patches and discussions about the oe-core layer
> > Subject: Re: [OE-core] [review/test 3/5] python, python-native: upgrade
> > from 2.6.6 to 2.7.2
> >
> > On Sat, Oct 22, 2011 at 04:54:00PM -0700, Kamble, Nitin A wrote:
> > > Hi Martin,
> > > I have kept my python work at nitin/python branch on poky contrib.
> > the 2.7.2 python is working for all arches except arm. And I am going
> > on vacation for few days, and I could not finish the python arm issue
> > arm, so if you get a chance you can look into the arm issue, if you
> > have not resolved it already then I will look into it again once I am
> > back from my vacation on 13th Nov.
> >
> > Hi Nitin,
> >
> > I've tried already and failed, but I'll try again and I guess qemux86-
> > 64 (linking to host libc and failing if it's not same version as the
> > one in
> > sysroot) is also still broken and should be taken care of too, right?
> >
> > Regards,
> >
> > > > -----Original Message-----
> > > > From: openembedded-core-bounces@lists.openembedded.org
> > > > [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf
> > > > Of Martin Jansa
> > > > Sent: Friday, October 14, 2011 2:12 AM
> > > > To: Patches and discussions about the oe-core layer
> > > > Subject: Re: [OE-core] [review/test 3/5] python, python-native:
> > > > upgrade from 2.6.6 to 2.7.2
> > > >
> > > > On Fri, Oct 14, 2011 at 10:19:39AM +0200, Martin Jansa wrote:
> > > > > On Thu, Oct 13, 2011 at 04:06:13PM -0700,
> > nitin.a.kamble@intel.com
> > > > wrote:
> > > > > > From: Nitin A Kamble <nitin.a.kamble@intel.com>
> > > > > >
> > > > >
> > > > > This patch does not apply after
> > > > > 9f9612d15acc6ee3b71f52bdb3f1ec4cb56b1a17
> > > > >
> > > > > can you rebase on top of oe-core?
> > > > >
> > > > > Also please drop
> > > > > DEFAULT_PREFERENCE = "-27"
> > > > >
> > > > > we have only one python version so I guess it's not usefull at
> > all
> > > > > anymore
> > > > >
> > > > > I'll apply it manually, test it here.. and report if those
> > modules
> > > > are
> > > > > build later..
> > > >
> > > > seems the same as with previous version..
> > > >
> > > > log.do_compile full of
> > > > /OE/shr-core/tmp/sysroots/x86_64-linux/usr/lib/libpython2.7.so:
> > file
> > > > not recognized: File format not recognized
> > > > collect2: ld returned 1 exit status
> > > >
> > > > and only built module is sqlite
> > > > OE @ ~/shr-core/tmp/work/armv4t-oe-linux-gnueabi/python-2.7.2-r0.0
> > $
> > > > ls Python-2.7.2/build/lib.linux-x86_64-2.7/
> > > > _sqlite3.so
> > > >
> > > > while with 2.6 we had a lot of modules $ ls
> > > > Python-2.6.6/build/lib.linux-x86_64-2.6/
> > > > _bisect.so _codecs_jp.so _ctypes.so _fileio.so
> > > > _json.so _random.so _testcapi.so bz2.so
> > > > datetime.so itertools.so parser.so spwd.so
> > > > unicodedata.so
> > > > _bytesio.so _codecs_kr.so _ctypes_test.so
> > _functools.so
> > > > _locale.so _socket.so _weakref.so cPickle.so
> > fcntl.so
> > > > math.so pyexpat.so strop.so zlib.so
> > > > _codecs_cn.so _codecs_tw.so _curses.so _hashlib.so
> > > > _lsprof.so _sqlite3.so array.so cStringIO.so
> > > > future_builtins.so mmap.so readline.so syslog.so
> > > > _codecs_hk.so _collections.so _curses_panel.so _heapq.so
> > > > _multibytecodec.so _ssl.so audioop.so cmath.so
> > gdbm.so
> > > > nis.so resource.so termios.so
> > > > _codecs_iso2022.so _csv.so _elementtree.so _hotshot.so
> > > > _multiprocessing.so _struct.so binascii.so crypt.so
> > grp.so
> > > > operator.so select.so time.so
> > > >
> > > > Can you please test that you have non-empty python-syslog python-
> > > > resource python-elementtree python-fcntl python-zlib?
> > > > And test build for qemuarm, because I guess that it links to -
> > native
> > > > libpython2.7 when you're building qemux86 on x86 host.
> > > >
> > > > But it seems that python runtime works now, thanks!
> > > >
> > > > Regards,
> > > > --
> > > > Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
> >
> > --
> > Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
^ permalink raw reply
* serial-console: IMAGE_FEATURE, MACHINE_FEATURE or DISTRO_FEATURE?
From: Koen Kooi @ 2011-10-24 7:27 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
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.
regards,
Koen
^ permalink raw reply
* Re: serial-console: IMAGE_FEATURE, MACHINE_FEATURE or DISTRO_FEATURE?
From: Frans Meulenbroeks @ 2011-10-24 8:27 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <F930E711-421C-439B-AAA8-EEBA0371ED86@dominion.thruhere.net>
[-- Attachment #1: Type: text/plain, Size: 1584 bytes --]
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.
> <http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core>
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.
My 2 cents.
Frans
[-- Attachment #2: Type: text/html, Size: 1973 bytes --]
^ permalink raw reply
* Re: [CONSOLIDATED PULL 26/27] abiword: convert to svn
From: Richard Purdie @ 2011-10-24 13:14 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <dfc5efb4c54797a39c2471dfba7b7cbf14fb6476.1319394187.git.sgw@linux.intel.com>
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:// ?!
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 13:15 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <6038b7e0961ca4aec70cc6de8adbc79567500e2b.1319394187.git.sgw@linux.intel.com>
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?
Cheers,
Richard
^ permalink raw reply
* Re: [CONSOLIDATED PULL 26/27] abiword: convert to svn
From: Koen Kooi @ 2011-10-24 13:18 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <1319462069.25011.0.camel@ted>
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.
regards,
Koen
^ 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
* 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 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 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 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 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 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: 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 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: [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 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: [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: 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: 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
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