From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: rpm-native problem?
Date: Fri, 20 Mar 2009 19:06:53 -0700 [thread overview]
Message-ID: <200903201907.00480.raj.khem@gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0903191522200.10548@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 7197 bytes --]
On Thursday 19 March 2009 15:30:29 Theodore A. Roth wrote:
> Hi,
>
> I just did a pull this morning and am getting this failure when parsing
> BitBake files:
>
>
>
> NOTE: Handling BitBake files: \ (0697/6606) [10 %]__builtin__:6:
> DeprecationWarning: raising a string exception is deprecated
> NOTE: No Python in STAGING_INCDIR. Forgot to build python-native ?:None
> while evaluating:
> ${@python_dir(d)}
> /home/roth/dev/OE/bitbake/lib/bb/data_smart.py:93: DeprecationWarning:
> raising a string exception is deprecated
> raise
> NOTE: No Python in STAGING_INCDIR. Forgot to build python-native ?:None
> while evaluating:
> --with-python
> --with-python-incdir=${STAGING_INCDIR}/${PYTHON_DIR}
> --with-python-libdir=${libdir}/${PYTHON_DIR} --without-apidocs
> --without-selinux --without-lua --without-dmalloc
> --without-efence ${MUTEX}
> ERROR: Error in executing:
> /home/roth/dev/OE/openembedded/recipes/rpm/rpm-native_4.4.2.3.bb
> ERROR: Exception:No Python in STAGING_INCDIR. Forgot to build
> python-native ? Message:None
> ERROR: Printing the environment of the function
> ERROR: 0002: import bb
> ERROR: 0003: from bb import __version__
> ERROR: 0004: base_after_parse(d)
> ERROR: 0005:
> ERROR: 0006: # Remove this for bitbake 1.8.12
> ERROR: 0007: try:
> ERROR: 0008: from distutils.version import LooseVersion
> ERROR: 0009: except ImportError:
> ERROR: 0010: def LooseVersion(v): print "WARNING: sanity.bbclass
> can't compare versions without python-distutils"; return 1
> /home/roth/dev/OE/bitbake/lib/bb/utils.py:191: DeprecationWarning: raising
> a string exception is deprecated
> raise
> Traceback (most recent call last):
> File "/home/roth/dev/OE/bitbake/bin/bitbake", line 143, in <module>
> main()
> File "/home/roth/dev/OE/bitbake/bin/bitbake", line 140, in main
> cooker.cook()
> File "/home/roth/dev/OE/bitbake/lib/bb/cooker.py", line 617, in cook
> self.updateCache()
> File "/home/roth/dev/OE/bitbake/lib/bb/cooker.py", line 587, in
> updateCache
> self.parse_bbfiles(filelist, masked, self.myProgressCallback)
> File "/home/roth/dev/OE/bitbake/lib/bb/cooker.py", line 717, in
> parse_bbfiles
> def parse_bbfiles(self, filelist, masked, progressCallback = None):
> File "/home/roth/dev/OE/bitbake/lib/bb/cooker.py", line 766, in
> parse_bbfiles
> raise
> File "/home/roth/dev/OE/bitbake/lib/bb/cooker.py", line 726, in
> parse_bbfiles
> fromCache, skip = self.bb_cache.loadData(f, self.configuration.data)
> File "/home/roth/dev/OE/bitbake/lib/bb/cache.py", line 168, in loadData
> bb_data, skipped = self.load_bbfile(fn, cfgData)
> File "/home/roth/dev/OE/bitbake/lib/bb/cache.py", line 413, in
> load_bbfile
> raise
> File "/home/roth/dev/OE/bitbake/lib/bb/cache.py", line 405, in
> load_bbfile
> bb_data = parse.handle(bbfile, bb_data) # read .bb data
> File "/home/roth/dev/OE/bitbake/lib/bb/parse/__init__.py", line 75, in
> handle
> return h['handle'](fn, data, include)
> File "/home/roth/dev/OE/bitbake/lib/bb/parse/parse_py/BBHandler.py",
> line 184, in handle
> finalise(fn, d)
> File "/home/roth/dev/OE/bitbake/lib/bb/parse/parse_py/BBHandler.py",
> line 92, in finalise
> build.exec_func("__anonfunc", d)
> File "/home/roth/dev/OE/bitbake/lib/bb/build.py", line 113, in exec_func
> exec_func_python(func, d)
> File "/home/roth/dev/OE/bitbake/lib/bb/build.py", line 136, in
> exec_func_python
> utils.better_exec(comp, g, tmp, bbfile)
> File "/home/roth/dev/OE/bitbake/lib/bb/utils.py", line 171, in
> better_exec
> exec code in context
> File "__anonfunc", line 76, in <module>
> File "__anonfunc", line 74, in __anonfunc
> File "<bb>", line 5, in gettext_after_parse
> File "/home/roth/dev/OE/bitbake/lib/bb/data.py", line 97, in getVar
> return d.getVar(var,exp)
> File "/home/roth/dev/OE/bitbake/lib/bb/data_smart.py", line 167, in
> getVar
> return self.expand(value,var)
> File "/home/roth/dev/OE/bitbake/lib/bb/data_smart.py", line 84, in
> expand
> s = __expand_var_regexp__.sub(var_sub, s)
> File "/home/roth/dev/OE/bitbake/lib/bb/data_smart.py", line 61, in
> var_sub
> var = self.getVar(key, 1)
> File "/home/roth/dev/OE/bitbake/lib/bb/data_smart.py", line 167, in
> getVar
> return self.expand(value,var)
> File "/home/roth/dev/OE/bitbake/lib/bb/data_smart.py", line 85, in
> expand
> s = __expand_python_regexp__.sub(python_sub, s)
> File "/home/roth/dev/OE/bitbake/lib/bb/data_smart.py", line 71, in
> python_sub
> s = eval(code)
> File "<string>", line 1, in <module>
> File "<bb>", line 6, in python_dir
> No Python in STAGING_INCDIR. Forgot to build python-native ?
>
FWIW I am seeing same error on ubuntu 8.08 box (python 2.5.2 on box) . I do not see this error on ubuntu 9.04 which has python 2.6.1 on box.
>
>
> Is this problem related to the following patch?
>
>
> Author: Marcin Juszkiewicz <hrw@openembedded.org> 2008-11-19 03:12:37
> Committer: Marcin Juszkiewicz <hrw@openembedded.org> 2009-03-19 12:22:34
> Parent: 47bb0f5ca3d62205703973398d79ed553bed8a4f (linux-msm7xxx: bump
> htcraphael SRCREV to a version that boots)
> Child: cabcbfe980d379e03589be3ed4bd0a4fc006e770 (beecrypt: get patch from
> Poky to fix building on 64bit machines)
> Branches: org.openembedded.dev, remotes/origin/org.openembedded.dev,
> ts7800
> Follows: mv-packages-to-recipes-post
> Precedes:
>
> rpm/rpm-native: Add recipe for 4.4.2.3 (from Poky)
>
> Squashed set of changes from Poky:
>
> svn r5069 - rpm/rpm-native: Add recipe for 4.4.2.3
> svn r5085 - rpm: Patch out some Makefile strangeness causing build
> failures
> svn r5093 - rpm: Enable python extensions and improve cross compiling
> patches
> svn r5103 - rpm: Tweak patches to remove popt problem
> svn r5113 - rpm: Add recommends support from suse rpm patches
> svn r5132 - rpm-native: Set varprefix to get the rpm database in a
> sane location
> svn r5152 - rpm: Handle PYTHONVER differently in EXTRA_OECONF to stop
> gettext/uclibc failures during parsing
> svn r5154 - rpm: Add missing patches
> svn r5423 - rpm: Add python module packaging
>
> OE changes:
>
> rpm-native: add Python 2.6 support
> rpm: use distutils-base to get Python version
> rpm: use sed instead of ed - it is present in our metadata
> rpm: set ARM_INSTRUCTION_SET as it fails to build for thumb
>
> | /tmp/ccYO91se.s: Assembler messages:
> | /tmp/ccYO91se.s:71: Error: selected processor does not support `swpb
> r2,r3,[r4]'
> | /tmp/ccYO91se.s:72: Error: unshifted register required -- `eor
> r2,r2,#1'
>
>
>
>
> Thanks for any help.
>
> Ted Roth
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
--
Khem Raj
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 204 bytes --]
next prev parent reply other threads:[~2009-03-21 2:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 22:30 rpm-native problem? Theodore A. Roth
2009-03-20 11:42 ` Marcin Juszkiewicz
2009-03-20 15:19 ` Theodore A. Roth
2009-03-21 2:06 ` Khem Raj [this message]
2009-03-21 2:21 ` Khem Raj
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=200903201907.00480.raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.