Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] site: enable pthread support for x86_64 APR builds
Date: Mon, 29 Feb 2016 20:17:47 +0000	[thread overview]
Message-ID: <1456777067.11498.180.camel@linuxfoundation.org> (raw)
In-Reply-To: <1456757580-31669-1-git-send-email-adrian.ratiu@ni.com>

On Mon, 2016-02-29 at 16:53 +0200, Ioan-Adrian Ratiu wrote:
> The apache2 package is missing key pieces of pthread support (notably
> pthread_kill) on x86_64 platforms. Fix this by setting cached
> variable
> apr_cv_pthreads_cflags=-pthread which will trickle down into apache2
> as
> well. powerpc32-linux currently sets this option.
> 
> Suggested-by: Jacob Champion <jacob.champion@ni.com>
> Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>
> ---
>  meta/site/x86_64-linux | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/site/x86_64-linux b/meta/site/x86_64-linux
> index 573a907..5b37211 100644
> --- a/meta/site/x86_64-linux
> +++ b/meta/site/x86_64-linux
> @@ -104,6 +104,7 @@
> nfsd_cv_func_statfs=${nfsd_cv_func_statfs=statfs2_bsize}
>  nfsd_cv_bsd_signals=${nfsd_cv_bsd_signals=yes}
>  
>  #apr
> +apr_cv_pthreads_cflags=${apr_cv_pthreads_cflags=-pthread}
>  apr_cv_tcp_nodelay_with_cork=${apr_cv_tcp_nodelay_with_cork=yes}

Autobuilder doesn't look happy after this change:

https://autobuilder.yoctoproject.org/main/builders/build-appliance/buil
ds/662/steps/BuildImages_1/logs/stdio

This was the only change to apr in there so its looking like the most
likely suspect...

Cheers,

Richard


  reply	other threads:[~2016-02-29 20:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 14:53 [PATCH v2] site: enable pthread support for x86_64 APR builds Ioan-Adrian Ratiu
2016-02-29 20:17 ` Richard Purdie [this message]
2016-03-01  9:16   ` Ioan-Adrian Ratiu
2016-03-18  1:01   ` 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=1456777067.11498.180.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=adrian.ratiu@ni.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