From: "David Nyström" <david.nystrom@enea.com>
To: <yocto@yoctoproject.org>
Subject: Re: libpam libprelude issues.
Date: Mon, 23 Sep 2013 15:51:47 +0200 [thread overview]
Message-ID: <52404773.5040202@enea.com> (raw)
In-Reply-To: <52403DFF.1060608@enea.com>
http://lists.openembedded.org/pipermail/openembedded-devel/2012-March/083804.html
This bug seems a bit ripe :), patch sent with --disable-prelude on
the oe-core mailinglist.
Br,
David
On 09/23/2013 03:11 PM, David Nyström wrote:
> On 09/23/2013 03:03 PM, David Nyström wrote:
>> Hi,
>>
>> I'm on:
>>
>> Build Configuration:
>> BB_VERSION = "1.19.1"
>> BUILD_SYS = "x86_64-linux"
>> NATIVELSBSTRING = "Ubuntu-13.10"
>> TARGET_SYS = "x86_64-poky-linux"
>> MACHINE = "qemux86-64"
>> DISTRO = "poky"
>> DISTRO_VERSION = "1.4+snapshot-20130923"
>> TUNE_FEATURES = "m64"
>> TARGET_FPU = ""
>> meta
>> meta-yocto
>> meta-yocto-bsp = "master:bf6b0d95db3863a2cfbccb154c0c7ad5b3bbf0b0"
>>
>> Have had these problems for a while, but noone else seems to notice it.
>> See attachment for compiler error and configure mistakenly detecting
>> libprelude, its installed on my build machine.
>>
>> Works fine if I EXTRA_OECONF += "--without-libprelude".
>>
>> What do you think ?, should I send that patch ?
>> I guess the real bug lies somewhere in the autodetection of libprelude
>> from my build machine, right ?
>>
>> Br,
>> David
>
> Oh, forgot to mention that I'm on Ubuntu 13.10.
> And I meant EXTRA_OECONF += "--disable-prelude"
>
> Br,
> David
prev parent reply other threads:[~2013-09-23 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 13:03 libpam libprelude issues David Nyström
2013-09-23 13:11 ` David Nyström
2013-09-23 13:51 ` David Nyström [this message]
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=52404773.5040202@enea.com \
--to=david.nystrom@enea.com \
--cc=yocto@yoctoproject.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.