Re: :-)

Re: :-)

[P]

becker@scyld.com wrote:
> Looking  forward for a response  :P
>  
> 35486 --  archive password

Hmm that looks like a new one?

Seems like a (massive) email variant of this one?
http://www.viruslist.com/eng/viruslist.html?id=3952

Pádraig.

"(-)"??

[Takashi Matsuzawa]

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

Hello.
I am seeing some of the recipes contains lines like below.

> COMPATIBLE_MACHINE = "(-)"

Sorry being novice, but what is the intended effect of this line?
I can see submit comments that this is for blacklisting but I am not sure how it works.  It simply means a '-' letter?



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

Re: "(-)"??

[Khem Raj]

On 9/20/17 8:18 PM, Takashi Matsuzawa wrote:
> Hello.
> I am seeing some of the recipes contains lines like below.
> 
>> COMPATIBLE_MACHINE = "(-)"
> 
> Sorry being novice, but what is the intended effect of this line?
> I can see submit comments that this is for blacklisting but I am not
> sure how it works.  It simply means a '-' letter?

COMAPTIBLE_MACHINE uses regexp syntax

Re: "(-)"??

[Peter Kjellerstedt]

> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-
> bounces@yoctoproject.org] On Behalf Of Khem Raj
> Sent: den 21 september 2017 07:15
> To: Takashi Matsuzawa <tmatsuzawa@xevo.com>; yocto@yoctoproject.org
> Subject: Re: [yocto] "(-)"??
> 
> On 9/20/17 8:18 PM, Takashi Matsuzawa wrote:
> > Hello.
> > I am seeing some of the recipes contains lines like below.
> >
> >> COMPATIBLE_MACHINE = "(-)"
> >
> > Sorry being novice, but what is the intended effect of this line?
> > I can see submit comments that this is for blacklisting but I am not
> > sure how it works.  It simply means a '-' letter?
> 
> COMAPTIBLE_MACHINE uses regexp syntax

Which actually makes that a pretty weird COMPATIBLE_MACHINE, 
especially if it is intended for blacklisting. Given that it would 
match any machine with a dash in it, it would match, e.g., qemux86-64
but not qemux86. It would also happen to match about half of our 
machines which happen to have dashes in their names.

A more appropriate way to blacklist machines using COMPATIBLE_MACHINE 
would be something like:

COMPATIBLE_MACHINE = "null"

or:

COMPATIBLE_MACHINE = "nothing"

I found two occurrences of "(-)" being used as COMPATIBLE_MACHINE in 
meta-openembedded for Morty and Pyro, but they have been removed for 
Rocko. If you see them anywhere else, consider changing them.

//Peter

Re: "(-)"??

[Martin Jansa]

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

null and nothing can also be matched in MACHINE names, so to make sure
people should use:

COMPATIBLE_MACHINE = "(^$)"

On Thu, Sep 21, 2017 at 8:41 AM, Peter Kjellerstedt <
peter.kjellerstedt@axis.com> wrote:

> > -----Original Message-----
> > From: yocto-bounces@yoctoproject.org [mailto:yocto-
> > bounces@yoctoproject.org] On Behalf Of Khem Raj
> > Sent: den 21 september 2017 07:15
> > To: Takashi Matsuzawa <tmatsuzawa@xevo.com>; yocto@yoctoproject.org
> > Subject: Re: [yocto] "(-)"??
> >
> > On 9/20/17 8:18 PM, Takashi Matsuzawa wrote:
> > > Hello.
> > > I am seeing some of the recipes contains lines like below.
> > >
> > >> COMPATIBLE_MACHINE = "(-)"
> > >
> > > Sorry being novice, but what is the intended effect of this line?
> > > I can see submit comments that this is for blacklisting but I am not
> > > sure how it works.  It simply means a '-' letter?
> >
> > COMAPTIBLE_MACHINE uses regexp syntax
>
> Which actually makes that a pretty weird COMPATIBLE_MACHINE,
> especially if it is intended for blacklisting. Given that it would
> match any machine with a dash in it, it would match, e.g., qemux86-64
> but not qemux86. It would also happen to match about half of our
> machines which happen to have dashes in their names.
>
> A more appropriate way to blacklist machines using COMPATIBLE_MACHINE
> would be something like:
>
> COMPATIBLE_MACHINE = "null"
>
> or:
>
> COMPATIBLE_MACHINE = "nothing"
>
> I found two occurrences of "(-)" being used as COMPATIBLE_MACHINE in
> meta-openembedded for Morty and Pyro, but they have been removed for
> Rocko. If you see them anywhere else, consider changing them.
>
> //Peter
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

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

Re: "(-)"??

[Gunnar Andersson]

On Thu, 2017-09-21 at 12:43 +0200, Martin Jansa wrote:
> null and nothing can also be matched in MACHINE names, so to make sure
> people should use:
> 
> COMPATIBLE_MACHINE = "(^$)"
> 
[trimmed]
> > >
> > > COMAPTIBLE_MACHINE uses regexp syntax
> > 
> > Which actually makes that a pretty weird COMPATIBLE_MACHINE,
> > 
> > especially if it is intended for blacklisting.

Yes, I think seeking consensus on the best practice here would make a lot of
sense.  Clearly people copy each other, but there are still *so* many
variants of this out there!

Very often machine overrides are used because there's no real sane way of
adding a specific machine, to the value that is there already:

This is actually written in many places:

COMPATIBLE_MACHINE_core2-32-intel-common = "${MACHINE}"

So if I see it correctly, that's going to apply if and only if MACHINE is
core2-32-intel-common and if so, then the ${MACHINE} regexp will also expand
to "core2-32-intel-common", and then finally bitbake will match that (as a
regexp) against the same $MACHINE name again to see if it yields true
(which it always will)...  I mean it's a little crazy isn't it?

Luckily special characters are usually not used in the machine names, or the
above might have unintended consequences too.

Sometimes the pattern matching is good but most of the time we just to say
basically: IS_COMPATIBLE(mymachinename)!

There are also these variations in various layers:

COMPATIBLE_MACHINE_genericx86 = "genericx86"

and this one seems popular:

# (Always match my string, but using MACHINE override):
COMPATIBLE_MACHINE_x86-64 = "(.*)"

That's a bit more straight forward, but not much.

If it's a true regexp match as Martin indicates with the ^$ example to
exclude non-empty string - presumably then, this syntax is yet another
working alternative because an empty regexp matches, right?

COMPATIBLE_MACHINE_x86-64 = ""

Being able to append your new machine in a sane way would make sense, but
with regexps it seems the reasonable syntax would then be:

COMPATIBLE_MACHINE_append = "|core2-32-intel-common"

Is that right?  And is that syntax also being used?  I'm not sure if that
will result in a valid regexp 100% of the time, but presumably it might
work.

And what is this?  I'm not sure I understand this one...

COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"


There is legacy and compatibility to consider I understand, but just looking
at it with fresh eyes, this thing seems to beg for a more easy to understand
mechanism.

I wonder if what one might like is a kind of array (of regexps), so you can
add new machines or machine-patterns to it in a sane manner.  Admittedly it
makes it harder to reset/subtract from the value if you want to remove some
previous setting.

Perhaps in a new design I'd consider two mechanisms, one for exact matches,
which could act as a list of words - many other bitbake variables do - and
one for patterns:

COMPATIBLE_MACHINE_EXACT = "first-machine second-machine"
COMPATIBLE_MACHINE_EXACT += " third-machine"

COMPATIBLE_MACHINE_PATTERN = "(.*x86.*)"

Just my 2c, take it for what it's worth.

- Gunnar

-- 
Gunnar Andersson <gandersson@genivi.org>
Development Lead
GENIVI Alliance

:-)

[linux-net]

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

Looking  forward for  a response :P

..btw, "16327" is a password  for archive

[-- Attachment #2: Letter.zip --]
[-- Type: application/octet-stream, Size: 21870 bytes --]

±±¾©Ë÷ÁèÀñÆ·ÖÐÐÄ-ÀñÆ·¡¢°ì¹«ÓÃÆ·¡¢¼ÒÍ¥ÓÃÆ·¡¢´ÙÏúÆ·¡¢¹ã¸æÉ¡¡¢ÀñÆ·±í¡¢¹ã¸æ±Ê

[±±¾©Ë÷ÁèÀñÆ·ÖÐÐÄ]

[-- Attachment #1.1: Type: text/plain, Size: 2157 bytes --]

  

  　 
  首页   |  最新推荐          |  关于我们           |   服务流程           |  代理商加盟 |       厂商加盟           |  成功案例 | 索取目录 |     在线订购                |  联系方式                           
     
   
   
  

 
办公用品

  

 
电子产品

  
 
钟表类
  

 
雨伞

  

 
商务礼品

 

 
广告笔

 

 
烟具类

 
 
工艺品
 

 
服装类

 

 
家庭用品

 

 
促销品

 

 
印刷品

      
   
     
  
    
    
   关于我们  
  
		         北京索凌礼品中心是一家专业为公司企事业单位提供个性化礼品服务的礼品设计制作经销商，一家专业礼品网络运营及电子商务公司。诚信经营、稳步发展，是我们的立业之本。
    经营范围包括办公礼品、工艺礼品等多种规格多种档次的礼品，款式多达5000余种。可提供现货也可以为客户定制定做。礼品空间在广州、深圳、浙江等地均设有生产基地及合作单位，凭借其雄厚设计制作实力及多年成功市场运作经验，结合互联网技术的发展为广大客户提供质优价廉充分个性化的服务。我们的客户包括英特尔公司、NOKIA、Motorola、HP、中央电视台、中国石油、太平洋百货、联想等数十个国内外大中型企事业单位，优质的服务均获客户高度评价。
 
    索凌礼品中心网成立于2000年11月，是由公司创办人在吸收国外商务礼品行业精髓。依靠国内30余家礼品主要生产商、OEM工厂支持，并结合索凌科技网络资源创办的。从为企业提供专业礼品，发展成为最受广大用户喜爱的综合礼品门户站点。在继续发其核心产品与服务---商务礼品，将不断推出了全方位高质量的产品和服务，"特别企划"、   "印刷品"、"特别包装"、"网上定购"、"新品推介"、"生日礼物"、   "情人礼品"、"珍藏精品"、 "健康休闲"、等栏目，为广大客户提供了丰富的网上礼品市场，成为北京网络用户采购商务和个人礼品的最佳渠道。
  
　

　

　 		  
		   
   
    
  　 　 　 　 　 　 　 　    
    
  首页 | 下载订单                                | 付款方式                              |  礼品文化 | 合作伙伴 |     招聘信息                          | 联系方式         | 地理位置                  
    
索凌礼品网．北京索凌礼品营销中心    地址：北京市海淀区长春桥路5号新起点大厦6号311室               邮编：100089
电话 Tel:0086-10-82643511/12/13/14   传真 Fax:                       0086-10-82643514
如果您对我们的服务有任何意见或建议，请惠赐E-mail至：info@soling.net 

[-- Attachment #1.2: Type: text/html, Size: 15068 bytes --]

[-- Attachment #2: map_l01.gif --]
[-- Type: application/octet-stream, Size: 187 bytes --]

[-- Attachment #3: Ico.gif --]
[-- Type: application/octet-stream, Size: 368 bytes --]

[-- Attachment #4: Ico.gif --]
[-- Type: application/octet-stream, Size: 368 bytes --]

[-- Attachment #5: Ico.gif --]
[-- Type: application/octet-stream, Size: 368 bytes --]

[-- Attachment #6: Ico.gif --]
[-- Type: application/octet-stream, Size: 368 bytes --]

[-- Attachment #7: Ico.gif --]
[-- Type: application/octet-stream, Size: 368 bytes --]

[-- Attachment #8: Ico.gif --]
[-- Type: application/octet-stream, Size: 368 bytes --]

[-- Attachment #9: Ico.gif --]
[-- Type: application/octet-stream, Size: 368 bytes --]

[-- Attachment #10: Ico.gif --]
[-- Type: application/octet-stream, Size: 368 bytes --]

[-- Attachment #11: Ico.gif --]
[-- Type: application/octet-stream, Size: 368 bytes --]

[-- Attachment #12: Ico.gif --]
[-- Type: application/octet-stream, Size: 368 bytes --]

[-- Attachment #13: Ico.gif --]
[-- Type: application/octet-stream, Size: 368 bytes --]

[-- Attachment #14: Ico.gif --]
[-- Type: application/octet-stream, Size: 368 bytes --]

[-- Attachment #15: map_l07.gif --]
[-- Type: application/octet-stream, Size: 104 bytes --]

[-- Attachment #16: title_back.gif --]
[-- Type: application/octet-stream, Size: 65 bytes --]