Re: [RFC] Adding TLS selection choice to metadata

[Khem Raj <raj.khem@gmail.com>]

On (30/07/09 09:35), Holger Freyther wrote:
> On Wednesday 29 July 2009 19:55:38 Khem Raj wrote:
> 
> > > To cite my patch:
> > >
> > > +# The tls/ntpl support in uclibc is work in progress. For the current
> > > +# targets we should build gcc with --enable-tls=no. In the future we
> > > +# might want to enable TLS for certain architectures and uclibc versions
> > > +# so this is why this method exists.
> > > +def get_gcc_uclibc_tls_setting(bb, d):
> > > +    return "--enable-tls=no"
> >
> > I was thinking of a case when say nptl is supported on mips
> > but someone still wants to build with linuxthreads. In your patch you
> > rely upon the target triplet to decide where to enable it and where
> > not to. 
> 
> In my patch I solely rely on the power of a turing complete language called 
> python. In this python method you can place a:
> 
>       if bb.data.getVar("TARGET_TLS", d, True)
>            return ""
> 
> and be done, in analogue to the FPU setting (hence it is right below the FPU 
> code). do you agree?

yes that will be ok. 

> 
> z.
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel