Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] SRCREVs and fixed building python modules
Date: Thu, 31 Mar 2011 12:40:00 +0200	[thread overview]
Message-ID: <cover.1301567822.git.Martin.Jansa@gmail.com> (raw)

SCM recipes should be usefull without including poky-default-revisions.inc
Building python modules fails without distutils-common-base patch, 
when trying to link against libc from host's /usr/lib

Pull URL: git://git.openembedded.org/openembedded-core-contrib
  Branch: jansa/pull
  Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=jansa/pull

Thanks,
    Martin Jansa <Martin.Jansa@gmail.com>
---


Martin Jansa (3):
  distutils-common-base.bbclass: Prepend STAGING_LIBDIR to linker
    library search path.
  gconf-dbus: add SRCREV to recipe
  xf86-video-omapfb: add SRCREV to recipe

 meta/classes/distutils-common-base.bbclass         |    2 ++
 meta/recipes-gnome/gnome/gconf-dbus_svn.bb         |    1 +
 .../xorg-driver/xf86-video-omapfb_git.bb           |    1 +
 3 files changed, 4 insertions(+), 0 deletions(-)

-- 
1.7.4.1




             reply	other threads:[~2011-03-31 10:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 10:40 Martin Jansa [this message]
2011-03-31 10:40 ` [PATCH 1/3] distutils-common-base.bbclass: Prepend STAGING_LIBDIR to linker library search path Martin Jansa
2011-03-31 14:26   ` Richard Purdie
     [not found]     ` <20110404183138.GA30816@jama.jama.net>
2011-04-18  5:54       ` Martin Jansa
2011-04-18  6:57         ` Richard Purdie
2011-04-22 17:48           ` Khem Raj
2011-04-27  7:43           ` Michael Lippautz
2011-04-27  8:47             ` Michael Lippautz
2011-03-31 10:40 ` [PATCH 2/3] gconf-dbus: add SRCREV to recipe Martin Jansa
2011-03-31 10:40 ` [PATCH 3/3] xf86-video-omapfb: " Martin Jansa
2011-03-31 10:47   ` Koen Kooi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1301567822.git.Martin.Jansa@gmail.com \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox