From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: build breakage: python-native-2.6.1
Date: Fri, 13 Nov 2009 11:29:46 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911131129020.5980@localhost> (raw)
In-Reply-To: <1258129007.5799.73.camel@dax.rpnet.com>
On Fri, 13 Nov 2009, Richard Purdie wrote:
> Can someone with this problem please run a python-native build with
> http://tim.rpsys.net/python-debug.patch applied?
>
> There should be some debug at the end of the do_compile log afterwards.
> I see:
>
> Looking in ncursesw for ['/media/build1/builds/oe/angstrom/tmp/staging/x86_64-linux/usr/lib', '/usr/local/lib', '.', '/lib64', '/usr/lib64', '/lib', '/usr/lib']
> Looking in ncurses for ['/media/build1/builds/oe/angstrom/tmp/staging/x86_64-linux/usr/lib', '/usr/local/lib', '.', '/lib64', '/usr/lib64', '/lib', '/usr/lib']
> Found /media/build1/builds/oe/angstrom/tmp/staging/x86_64-linux/usr/lib/libncurses.so
>
> and I'm guessing it finds ncursesw in /lib/lib64 for some people.
>
> I also see some other worrying entries on my system :(
do you still want this tested given the earlier posting about how
this was fixed with that readline tweak?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2009-11-13 16:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 9:45 build breakage: python-native-2.6.1 Robert P. J. Day
2009-11-13 12:15 ` Philip Balister
2009-11-13 12:34 ` Robert P. J. Day
2009-11-13 12:42 ` Philip Balister
2009-11-13 13:19 ` Petr Štetiar
2009-11-13 15:41 ` Adrian Alonso
2009-11-13 16:16 ` Robert P. J. Day
2009-11-13 16:16 ` Richard Purdie
2009-11-13 16:29 ` Robert P. J. Day [this message]
2009-11-13 16:39 ` Richard Purdie
2009-11-13 17:13 ` Mike Westerhof
2009-11-13 22:41 ` Michael 'Mickey' Lauer
2009-11-14 12:50 ` Philip Balister
2009-11-14 12:52 ` Robert P. J. Day
2009-11-14 12:59 ` Philip Balister
2009-11-14 12:59 ` Robert P. J. Day
2009-11-14 13:13 ` Philip Balister
2009-11-14 13:17 ` Robert P. J. Day
2009-11-14 13:27 ` Robert P. J. Day
2009-11-14 14:23 ` Philip Balister
2009-11-14 13:15 ` Michael 'Mickey' Lauer
2009-11-13 16:42 ` Mike Westerhof
2009-11-13 17:26 ` Adrian Alonso
2009-11-13 17:50 ` Robert P. J. Day
2010-03-12 8:05 ` build breakage: python-native-2.6.4 (was build breakage: python-native-2.6.1) Steffen Sledz
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=alpine.LFD.2.00.0911131129020.5980@localhost \
--to=rpjday@crashcourse.ca \
--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.