All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] siteinfo: nios2-linux - remove wrong mutex info
@ 2017-10-03 19:51 Juro Bystricky
  2017-10-03 19:59 ` Marek Vasut
  0 siblings, 1 reply; 4+ messages in thread
From: Juro Bystricky @ 2017-10-03 19:51 UTC (permalink / raw)
  To: openembedded-core; +Cc: marex, jurobystricky, yau.wai.gan

This fixes broken nios2 builds that involve db recipes.

Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
---
 meta/site/nios2-linux | 1 -
 1 file changed, 1 deletion(-)

diff --git a/meta/site/nios2-linux b/meta/site/nios2-linux
index 2f4e570..5bae748 100644
--- a/meta/site/nios2-linux
+++ b/meta/site/nios2-linux
@@ -33,7 +33,6 @@ db_cv_path_sh=${db_cv_path_sh=/bin/sh}
 db_cv_path_strip=${db_cv_path_strip=/usr/bin/strip}
 db_cv_align_t=${db_cv_align_t='unsigned long long'}
 db_cv_alignp_t=${db_cv_alignp_t='unsigned long'}
-db_cv_mutex=${db_cv_mutex=ARM/gcc-assembly}
 db_cv_posixmutexes=${db_cv_posixmutexes=no}
 db_cv_uimutexes=${db_cv_uimutexes=no}
 
-- 
2.7.4



^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH] siteinfo: nios2-linux - remove wrong mutex info
  2017-10-03 19:51 [PATCH] siteinfo: nios2-linux - remove wrong mutex info Juro Bystricky
@ 2017-10-03 19:59 ` Marek Vasut
  2017-10-03 20:44   ` Bystricky, Juro
  0 siblings, 1 reply; 4+ messages in thread
From: Marek Vasut @ 2017-10-03 19:59 UTC (permalink / raw)
  To: Juro Bystricky, openembedded-core; +Cc: jurobystricky, yau.wai.gan

On 10/03/2017 09:51 PM, Juro Bystricky wrote:
> This fixes broken nios2 builds that involve db recipes.

While I understand ARM/ is wrong, why is removing the db_cv_mutex a
correct fix instead of ie. s/ARM/nios2/ ? The patch description does not
explain that.

> Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
> ---
>  meta/site/nios2-linux | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/meta/site/nios2-linux b/meta/site/nios2-linux
> index 2f4e570..5bae748 100644
> --- a/meta/site/nios2-linux
> +++ b/meta/site/nios2-linux
> @@ -33,7 +33,6 @@ db_cv_path_sh=${db_cv_path_sh=/bin/sh}
>  db_cv_path_strip=${db_cv_path_strip=/usr/bin/strip}
>  db_cv_align_t=${db_cv_align_t='unsigned long long'}
>  db_cv_alignp_t=${db_cv_alignp_t='unsigned long'}
> -db_cv_mutex=${db_cv_mutex=ARM/gcc-assembly}
>  db_cv_posixmutexes=${db_cv_posixmutexes=no}
>  db_cv_uimutexes=${db_cv_uimutexes=no}
>  
> 


-- 
Best regards,
Marek Vasut


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] siteinfo: nios2-linux - remove wrong mutex info
  2017-10-03 19:59 ` Marek Vasut
@ 2017-10-03 20:44   ` Bystricky, Juro
  2017-10-03 20:52     ` Marek Vasut
  0 siblings, 1 reply; 4+ messages in thread
From: Bystricky, Juro @ 2017-10-03 20:44 UTC (permalink / raw)
  To: Marek Vasut, openembedded-core; +Cc: jurobystricky, Gan, Yau Wai


> While I understand ARM/ is wrong, why is removing the db_cv_mutex a
> correct fix instead of ie. s/ARM/nios2/ ? The patch description does not
> explain that.

With the relatively recent commit http://git.yoctoproject.org/cgit.cgi/poky/commit/meta/recipes-support/db?id=f4e8e9242c5df095b52688b083df3c9d36e7144b
some nios2 builds (uboot, core-image-minimal, etc) were broken due to db trying to
use ARM instructions in mutexes. The reason was db "configure" used the cached entry 
from nios2-linux (which was incorrect).  So the remedy was to remove the incorrect cached entry
and let db "configure" figure out which is the proper mutex to use. 
Besides, I don't even know if nios2/gcc-assembly exists.
Also, none of other Linux info files provides this entry (db_cv_mutex).



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] siteinfo: nios2-linux - remove wrong mutex info
  2017-10-03 20:44   ` Bystricky, Juro
@ 2017-10-03 20:52     ` Marek Vasut
  0 siblings, 0 replies; 4+ messages in thread
From: Marek Vasut @ 2017-10-03 20:52 UTC (permalink / raw)
  To: Bystricky, Juro, openembedded-core; +Cc: jurobystricky, Gan, Yau Wai

On 10/03/2017 10:44 PM, Bystricky, Juro wrote:
> 
>> While I understand ARM/ is wrong, why is removing the db_cv_mutex a
>> correct fix instead of ie. s/ARM/nios2/ ? The patch description does not
>> explain that.
> 
> With the relatively recent commit http://git.yoctoproject.org/cgit.cgi/poky/commit/meta/recipes-support/db?id=f4e8e9242c5df095b52688b083df3c9d36e7144b
> some nios2 builds (uboot, core-image-minimal, etc) were broken due to db trying to
> use ARM instructions in mutexes. The reason was db "configure" used the cached entry 
> from nios2-linux (which was incorrect).  So the remedy was to remove the incorrect cached entry
> and let db "configure" figure out which is the proper mutex to use. 
> Besides, I don't even know if nios2/gcc-assembly exists.
> Also, none of other Linux info files provides this entry (db_cv_mutex).
> 

This should be in the commit message ...

-- 
Best regards,
Marek Vasut


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2017-10-03 20:52 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-10-03 19:51 [PATCH] siteinfo: nios2-linux - remove wrong mutex info Juro Bystricky
2017-10-03 19:59 ` Marek Vasut
2017-10-03 20:44   ` Bystricky, Juro
2017-10-03 20:52     ` Marek Vasut

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.