From: Philip Balister <philip@balister.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Build failure in samba
Date: Mon, 14 Nov 2011 20:12:35 -0500 [thread overview]
Message-ID: <4EC1BC83.2010209@balister.org> (raw)
In-Reply-To: <1321315894.26881.117.camel@ted>
Doesn't seem to help. Will look again tomorrow. Go to bed.
Philip
On 11/14/2011 07:11 PM, Richard Purdie wrote:
> On Mon, 2011-11-14 at 18:47 -0500, Philip Balister wrote:
>> Anyone have an idea about this failure building samba?
>>
>> http://pastebin.com/5PGX6MZr
>>
>> I'm going to look more tomorrow, just hoping someone sees something obvious.
>
> Maybe this might help:
>
>
> commit ce064001e628597cab9c5713f1351e03478a4aa5
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date: Wed Nov 2 14:24:37 2011 +0000
>
> samba: Force python disabled for now to avoid host contamination
>
> diff --git a/recipes-support/samba/samba_3.5.6.bb b/recipes-support/samba/samba_3.5.6.bb
> index d5945f9..a44ce02 100644
> --- a/recipes-support/samba/samba_3.5.6.bb
> +++ b/recipes-support/samba/samba_3.5.6.bb
> @@ -12,6 +12,7 @@ SRC_URI[sha256sum] = "466410868375d19a286ac3fc5d9f3c267ce359189f8e0d76e72ec10bd5
> S = "${WORKDIR}/samba-${PV}/source3"
>
> EXTRA_OECONF += "\
> + ac_cv_path_PYTHON=/not/exist \
> SMB_BUILD_CC_NEGATIVE_ENUM_VALUES=yes \
> samba_cv_CC_NEGATIVE_ENUM_VALUES=yes \
> linux_getgrouplist_ok=no \
>
> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2011-11-15 1:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 23:47 Build failure in samba Philip Balister
2011-11-15 0:11 ` Richard Purdie
2011-11-15 1:12 ` Philip Balister [this message]
2011-11-15 8:00 ` Koen Kooi
2011-11-30 21:06 ` Denis 'GNUtoo' Carikli
2011-11-30 21:39 ` 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=4EC1BC83.2010209@balister.org \
--to=philip@balister.org \
--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