All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Ross Burton <ross.burton@intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	Jacob Champion <jacob.champion@ni.com>
Subject: Re: [PATCH v1] site: enable pthread support for x86_64 APR builds
Date: Fri, 18 Mar 2016 15:47:10 -0700	[thread overview]
Message-ID: <CAMKF1soCxyOdWGEAxz_5FbR4pwirUGXmTCQtOdT062eD6NX2mg@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0Laq7Re6hAEmY=Dd1=UUr0+Zg9UCDO5STXoDJni+Md86+g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

On Mar 18, 2016 4:38 AM, "Burton, Ross" <ross.burton@intel.com> wrote:
>
>
> On 18 March 2016 at 00:22, Khem Raj <raj.khem@gmail.com> wrote:
>>>
>>> Which is interesting as building apr-native (so the site files don't
get used) for x86-64 gives:
>>>
>>> apr_cv_process_shared_works=yes
>>>
>>> Can we not go around disabling stuff when it actually does work?
>>
>>
>> No it really doesnt work. its running a configure time test on your
build host ( which I assume is x86_64 mostly now
>> a days) and then deciding that process shared mutexes work, which is not
correct.
>>
>> If we think that it should work on x86_64 then lets cache the value to
‘yes’ but not leave it
>> at the mercy of configure.
>
>
> That was my point: the patch was to add works=no to x86-64 target builds,
but if I run the same test on x86-64 hardware directly then the result is
works=yes.

Actually it depends on libc implementation of process shared mutexes. So
glibc for most arches should set it yes. Musl doesnt have it. So that
should be no mostly
>
> Ross

[-- Attachment #2: Type: text/html, Size: 1419 bytes --]

      reply	other threads:[~2016-03-18 22:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 13:42 [PATCH v1] site: enable pthread support for x86_64 APR builds Ioan-Adrian Ratiu
2016-02-29 13:50 ` Burton, Ross
2016-02-29 14:04   ` Ioan-Adrian Ratiu
2016-03-18  0:22   ` Khem Raj
2016-03-18 11:38     ` Burton, Ross
2016-03-18 22:47       ` Khem Raj [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=CAMKF1soCxyOdWGEAxz_5FbR4pwirUGXmTCQtOdT062eD6NX2mg@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=jacob.champion@ni.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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.