On 03/23/2010 10:45 PM, Khem Raj wrote:
It seems to me the correct course of action is to use nativesdk in
BBCLASSEXTEND and rename the dependencies on other recipes, yes?
you should rename the dependencies on zlib-sdk to zlib-nativesdk
wherever they exist.
Khem: Thanks for the confirmation.
On Tue, Mar 23, 2010 at 8:06 PM, Scott Garman wrote:
> Hi all,
>
> I noticed in my attempt to convert zlib to use BBCLASSEXTEND that
> sdk.bbclass has been deprecated, and that the new way is to use
> nativesdk.bbclass. This is confirmed by the fact that the Poky recipe for
> zlib uses:
>
> BBCLAS
Hi all,
I noticed in my attempt to convert zlib to use BBCLASSEXTEND that
sdk.bbclass has been deprecated, and that the new way is to use
nativesdk.bbclass. This is confirmed by the fact that the Poky recipe
for zlib uses:
BBCLASSEXTEND = "native nativesdk"
However, if I use this in the OE
Hi,
resulted two things:
1. bitbake -c package_update_index opie-image
ERROR: Task do_package_update_index does not exist for target opie-image
2. I just found that:
although "bitbake some-pkg" will produce some-pkg-mine.ipk correctly,
some-pkg was still in some-image instead of some-pkg-mine af
-image, but some-pkg was still bitbaked and was in
>> some-image, not some-pkg-mine!
>> 6. rm -rf oe/overlay/tmp
>> 7. bitbake some-image, this time some-pkg-mine is in some-image, finally.
>>
>> Any info are very appreciated. :)
>
> may be try
> bitbake -c p
On Tue, Mar 23, 2010 at 3:34 PM, Thomas Zimmermann wrote:
> * imagemagick-6.3.5-10 doesn't configure with autoconf > 2.63
> * problem: without removing imagemagick-native_6.3.5-10 the old version is
> build
>
> Signed-off-by: Thomas Zimmermann
> ---
> recipes/imagemagick/imagemagick_6.4.4-1.bb
* imagemagick-6.3.5-10 doesn't configure with autoconf > 2.63
* problem: without removing imagemagick-native_6.3.5-10 the old version is build
Signed-off-by: Thomas Zimmermann
---
recipes/imagemagick/imagemagick_6.4.4-1.bb | 11 +--
1 files changed, 5 insertions(+), 6 deletions(-)
dif
On Tue, Mar 23, 2010 at 1:45 PM, Khem Raj wrote:
> On (23/03/10 10:47), Martin Jansa wrote:
> > On Mon, Mar 22, 2010 at 03:26:53PM -0700, Chris Larson wrote:
> > > Greetings all,
> > >
> > > Thoughts? Questions? Concerns? I've been wondering if this is really
> > > worthwhile, but I think it is.
Applied, thanks, nicely spotted, and sorry about that :)
On Tue, Mar 23, 2010 at 1:51 PM, Antonio Ospite wrote:
> In commit 89b7e433719f43f1c36c76cb8856d559014e99bc metadata_scm.bbclass
> functions were factored out from base.bbclass, but the new file was not
> included.
>
> This prevented METADA
Makes perl modules rebuild on perl version change, since binary compatibility
could be broken with that (although perl itself tries to maintain it within
patchlevel range, like 5.8.7 -> 5.8.8).
This is conditional on PACKAGE_ARCH, since there is nothing to rebuild for
pure perl modules (and those
In commit 89b7e433719f43f1c36c76cb8856d559014e99bc metadata_scm.bbclass
functions were factored out from base.bbclass, but the new file was not
included.
This prevented METADATA_SCM, METADATA_REVISION, METADATA_BRANCH to be
set; for instance this caused oestats-client stop working.
Signed-off-by:
mine is in some-image, finally.
>
> Any info are very appreciated. :)
may be try
bitbake -c package_update_index some-image
>
> Thank you!
> jiason
> 20100323
>
>
> > My steps:
> > 3. bitbake some-pkg, according to the log,
> > oe/overlay/recipes
On (23/03/10 10:47), Martin Jansa wrote:
> On Mon, Mar 22, 2010 at 03:26:53PM -0700, Chris Larson wrote:
> > Greetings all,
> >
> > Thoughts? Questions? Concerns? I've been wondering if this is really
> > worthwhile, but I think it is. I think there is value in keeping old
> > versions around, b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23-03-10 19:36, Graeme Gregory wrote:
> On Tue, Mar 23, 2010 at 07:01:23PM +0100, Marcin Juszkiewicz wrote:
>>
>> During last days I spent a bit of time on e2fsprogs* and util-linux-ng
>> recipes. They are cleaner now but there is still some work t
On Mon, Mar 22, 2010 at 11:07 PM, Sergey Lapin wrote:
> Hi, all!
>
> For some of my images I need to have normal syslogd/klogd instead
> of ones provided by busybox. I don;t want to have special version of
> busybox for these images,
> but it RRECOMMENDS busybox-syslog which contains config files
On Tue, Mar 23, 2010 at 07:01:23PM +0100, Marcin Juszkiewicz wrote:
>
> During last days I spent a bit of time on e2fsprogs* and util-linux-ng
> recipes. They are cleaner now but there is still some work to do.
>
> We have many recipes which depends on 'e2fsprogs-libs' when they want
> 'libblki
В сообщении от Вторник 23 марта 2010 21:01:34 автор Roman I Khimov написал:
> P.S. As for descriptions, I've thought that having them in recipes is
> enough, but I could add those in commit messages if there is a need for
> it.
P.P.S. As for the number of patches I'm posting to list, usually it'
Hello.
On Tue, 2010-03-23 at 19:15, Stefan Schmidt wrote:
>
> On Tue, 2010-03-23 at 18:51, Marcin Juszkiewicz wrote:
> >
> > I would like to give write access for Roman I Khimov. His patches are good
> > (new recipes could get descriptions in commit log anyway) and he touched
> > ugly
> > bea
Hello.
On Tue, 2010-03-23 at 18:51, Marcin Juszkiewicz wrote:
>
> I would like to give write access for Roman I Khimov. His patches are good
> (new recipes could get descriptions in commit log anyway) and he touched ugly
> beast (Perl I mean) and survived.
+1 from my side. All patches I have s
Acked-by: Philip Balister
On 03/23/2010 01:48 PM, Marcin Juszkiewicz wrote:
From: Marcin Juszkiewicz
Signed-off-by: Marcin Juszkiewicz
---
.../xorg-xserver/xserver-xorg-conf/bug20/xorg.conf | 29
recipes/xorg-xserver/xserver-xorg-conf_0.1.bb |2 +-
2 files c
В сообщении от Вторник 23 марта 2010 20:51:32 автор Marcin Juszkiewicz
написал:
> I would like to give write access for Roman I Khimov. His patches are good
> (new recipes could get descriptions in commit log anyway) and he touched
> ugly beast (Perl I mean) and survived.
Hey, I've already got o
During last days I spent a bit of time on e2fsprogs* and util-linux-ng
recipes. They are cleaner now but there is still some work to do.
We have many recipes which depends on 'e2fsprogs-libs' when they want
'libblkid' or 'libuuid' which are provided by 'e2fsprogs-libs' and
'util-linux-ng' reci
I would like to give write access for Roman I Khimov. His patches are good
(new recipes could get descriptions in commit log anyway) and he touched ugly
beast (Perl I mean) and survived.
Regards,
--
JID: h...@jabber.org
Website: http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.lin
From: Marcin Juszkiewicz
Signed-off-by: Marcin Juszkiewicz
---
.../xorg-xserver/xserver-xorg-conf/bug20/xorg.conf | 29
recipes/xorg-xserver/xserver-xorg-conf_0.1.bb |2 +-
2 files changed, 30 insertions(+), 1 deletions(-)
create mode 100644 recipes/xorg-xserver
On Tue, Mar 23, 2010 at 09:07:01AM -0700, Chris Larson wrote:
> Fair enough, there are valid concerns here, though I think some exist with
> or without the bbversions mechanism to a certain extent. If a minor version
> is buildable that isn't patched with the security patch, remove it from the
> B
On Tue, Mar 23, 2010 at 8:57 AM, Martin Jansa wrote:
> On Tue, Mar 23, 2010 at 08:41:14AM -0700, Chris Larson wrote:
> > I also agreed that it's nicer to duplicate a tiny amount of metadata than
> to
> > have a giant file full of overrides, but with BBVERSIONS, you could keep
> > every minor versi
On Tue, Mar 23, 2010 at 08:41:14AM -0700, Chris Larson wrote:
> I also agreed that it's nicer to duplicate a tiny amount of metadata than to
> have a giant file full of overrides, but with BBVERSIONS, you could keep
> every minor version of a given major version around. Keep one recipe per
> major
On Tue, Mar 23, 2010 at 2:47 AM, Martin Jansa wrote:
> On Mon, Mar 22, 2010 at 03:26:53PM -0700, Chris Larson wrote:
> > Greetings all,
> >
> > Thoughts? Questions? Concerns? I've been wondering if this is really
> > worthwhile, but I think it is. I think there is value in keeping old
> > versio
Just created a proper github project for my nano experimentations, and
pushed the current incarnation (slightly messier than it needs to be, since
I'm still experimenting with different ways of structuring it).
http://github.com/kergoth/Nano-OE/tree/master/recipes/nano/.
On Mon, Mar 22, 2010 at 3:
On Tue, Mar 23, 2010 at 2:50 AM, Holger Hans Peter Freyther <
holger...@freyther.de > wrote:
> On Tuesday 23 March 2010 10:32:59 Frans Meulenbroeks wrote:
> > Chris, while this is a nice idea it conflicts with having checksums in
> > the recipe, as that makes the recipes unique.
> > Unless of cour
Dnia wtorek, 23 marca 2010 o 16:17:50 Sebastian Spaeth napisał(a):
> Dear all,
>
> you might be interested in having a look at it:
>
> http://opkg-repo.org
Please take a look at contrib/feed-browser/ which is available at
http://www.angstrom-distribution.org/repo/ address. Everything was in PH
> For future: "git pull --rebase" please to not create merge commits.
Right. Point taken. Actually the merge was not wrong or horrible in the
end, I was just scared by the very bg diffstat I was seeing. Still, I
should have rebased before pushing. My apologies.
spaetz
___
Dear all,
you might be interested in having a look at it:
http://opkg-repo.org
which might become SHR's one stop place for finding and
rating packages. It's auto-updated daily from the Packages files,
showing you package information, versions, and a download link.
E.g. http://opkg-repo.org/opkg
On Tue, Mar 23, 2010 at 2:32 AM, Frans Meulenbroeks <
fransmeulenbro...@gmail.com> wrote:
> Chris, while this is a nice idea it conflicts with having checksums in
> the recipe, as that makes the recipes unique.
> Unless of course there is (or we create) a way to have multiple
> checksums in a reci
RDEPENDS on python, wants python-native at build time.
Signed-off-by: Roman I Khimov
---
recipes/lowpan-tools/lowpan-tools_git.bb |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/recipes/lowpan-tools/lowpan-tools_git.bb
b/recipes/lowpan-tools/lowpan-tools_git.bb
inde
Signed-off-by: Roman I Khimov
---
recipes/rpm/rpm-4.4.2.3.inc |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/recipes/rpm/rpm-4.4.2.3.inc b/recipes/rpm/rpm-4.4.2.3.inc
index 22e9734..f1f4d65 100644
--- a/recipes/rpm/rpm-4.4.2.3.inc
+++ b/recipes/rpm/rpm-4.4.2.3.inc
@@
Signed-off-by: Roman I Khimov
---
recipes/sphyrna/sphyrna-python_svn.bb |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/recipes/sphyrna/sphyrna-python_svn.bb
b/recipes/sphyrna/sphyrna-python_svn.bb
index 1e3c412..5b4ee8a 100644
--- a/recipes/sphyrna/sphyrna-python_svn.b
python-native needed for python-dir proper working and then fetchmailconf
really wants to have some python in runtime.
Signed-off-by: Roman I Khimov
---
recipes/fetchmail/fetchmail_6.3.14.bb |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/recipes/fetchmail/fetchmail
В сообщении от Суббота 20 марта 2010 00:05:35 автор Roman I Khimov написал:
> I think I need some ACK's for dusty old Perl versions removal and then
> Richard's Perl staging update could be merged better on top of that (CC'ing
> Richard) and than I'll update 5.10.1 to new staging and push the serie
Dnia wtorek, 23 marca 2010 o 13:52:58 Sebastian Spaeth napisał(a):
> Uhh, I just accidentally pushed a merge
> a501f95529d16fad725b58c241047bde63825cbf, I did not know I have in my
> tree. Not even know what the ancestors of that merge were, would it be
> possible for someone with git knowledge to
Uhh, I just accidentally pushed a merge
a501f95529d16fad725b58c241047bde63825cbf, I did not know I have in my
tree. Not even know what the ancestors of that merge were, would it be
possible for someone with git knowledge to revert that merge?
That would be great, thanks
Sebastian
P.S. I'll look i
On Tue, 23 Mar 2010, Frans Meulenbroeks wrote:
> Then again I feel it is in most cases better to move forward. E.g. for
> your nano example: why would people want to build say nano 1.0.2 if
> there is also a working 1.0.6 recipe (or even a 2.2.3 one or whatever
> version it is at). I feel it is be
Converted most of python site-packages references to PYTHON_SITEPACKAGES_DIR.
Signed-off-by: Roman I Khimov
---
classes/distutils-common-base.bbclass |8
classes/distutils.bbclass | 12 ++--
recipes/avahi/avahi.inc |
Allows to inherit that in packages containing Python extensions but still
tightly
control packaging of those extensions. Mainly for the cases where you want
those python modules/extensions/parts to be packaged separately from the main
package in order not to introduce python dependency where you d
On Tuesday 23 March 2010 11:02:14 Petr Štetiar wrote:
> Holger Hans Peter Freyther [2010-03-23 10:33:40]:
>
> Neat! I just wonder how to check linux kernel(s) and embedded stuff not
> used in FBSD. The kernel is quite mission impossible because of the patch
> hell...
Yeah glibc, udev, linux is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi at all,
It's not long ago that I use OE and some things do not know very well.. :D
For example, can someone explain me how (and where) can use
COMPATIBLE_MACHINE?
thanks a lot for all response! :D
hachreak
-BEGIN PGP
Martyn Welch wrote:
> Busybox provides a script for managing the RTC, this is not provided by
> anything else and will be required for busybox-less builds. Add it to
> util-linux-ng for now
This clearly needs to be a part of the proposed "busybox-alt" recipe,
not util-linux-ng.
Martyn
--
Martyn
Marcin Juszkiewicz wrote:
> Dnia poniedziałek, 22 marca 2010 o 10:35:06 Martyn Welch napisał(a):
>
>> This adds an alternatives link for /bin/sh to the bash package. When
>> installed this will make bash overide the busybox provided shell for
>> "/bin/sh". This may or may not be desirable, but i
Marcin Juszkiewicz wrote:
> Dnia poniedziałek, 22 marca 2010 o 17:08:20 Martyn Welch napisał(a):
>
>
>> This patch provides a mechanism to replace busybox by defining a busybox
>> package which actually just requires a set of other packages.
>>
>> To get it to be used rather than the standar
Holger Hans Peter Freyther [2010-03-23 10:33:40]:
> Hi,
Hi,
> here is a rather simple howto:
>
> $ bitbake -s > available
> $ export PYTHONPATH=/bitbake/lib
> $ /OE/contrib/oeaudit/oeaudit.py -f
> This will call wget, tar to get the audifile and place it in the local dir
> $ /OE/contrib/oeaudi
2010/3/23 Holger Hans Peter Freyther :
> On Tuesday 23 March 2010 10:32:59 Frans Meulenbroeks wrote:
>> Chris, while this is a nice idea it conflicts with having checksums in
>> the recipe, as that makes the recipes unique.
>> Unless of course there is (or we create) a way to have multiple
>> check
On Tuesday 23 March 2010 10:32:59 Frans Meulenbroeks wrote:
> Chris, while this is a nice idea it conflicts with having checksums in
> the recipe, as that makes the recipes unique.
> Unless of course there is (or we create) a way to have multiple
> checksums in a recipe and pick the one that is for
On Mon, Mar 22, 2010 at 03:26:53PM -0700, Chris Larson wrote:
> Greetings all,
>
> Thoughts? Questions? Concerns? I've been wondering if this is really
> worthwhile, but I think it is. I think there is value in keeping old
> versions around, but this allows us to avoid cluttering up the reposito
ine.bb was bitbaked
correctly.
5. bitbake some-image, but some-pkg was still bitbaked and was in
some-image, not some-pkg-mine!
6. rm -rf oe/overlay/tmp
7. bitbake some-image, this time some-pkg-mine is in some-image, finally.
Any info are very appreciated. :)
Thank you!
jiason
20100323
>
each time?
Any info are very appreciated. :)
Thank you!
jiason
20100323
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Hi,
here is a rather simple howto:
$ bitbake -s > available
$ export PYTHONPATH=/bitbake/lib
$ /OE/contrib/oeaudit/oeaudit.py -f
This will call wget, tar to get the audifile and place it in the local dir
$ /OE/contrib/oeaudit/oeaudit.py -a auditfile -p available
Now you get a nice list of issues.
Chris, while this is a nice idea it conflicts with having checksums in
the recipe, as that makes the recipes unique.
Unless of course there is (or we create) a way to have multiple
checksums in a recipe and pick the one that is for the version we are
building.
Then again I feel it is in most cases
it is ok now. I understood that -b option must be pass for a specific recipe
but for a package by its name not with its version or release.
Thank you for the time and consideration...
___
Openembedded-devel mailing list
Openembedded-devel@lists.openemb
58 matches
Mail list logo
