Op 22 feb. 2014, om 20:52 heeft Khem Raj <raj.k...@gmail.com> het volgende 
geschreven:

> 
> On Feb 22, 2014, at 10:12 AM, Phil Blundell <p...@pbcl.net> wrote:
> 
>> On Sat, 2014-02-22 at 01:31 -0800, Khem Raj wrote:
>>> builds might work but they won’t run and yes so far IFUNC support is needed 
>>> so it won’t work on non-x86
>>> architectures. One common runtime problem I am seeing is logind not being 
>>> able to talk to dbus
>>> across all architectures. I have pushed my latest rework to pull branch
>> 
>> What is the problem with ifunc on non-x86?  
> 
> they are not enabled across all architectures, well specifically, its not 
> enabled on arm and seems also ppc is missing it.
> 
>> As far as I know the
>> compiler, assembler, linker and ld.so for all reasonable architectures
>> support that nowadays (though prelink support is a bit patchy).  GCC
>> didn't have ifuncs enabled for some architectures until quite recently
>> but if that was the problem then you'd see compile-time failures.  So,
>> if it compiles then I can't think of any reason why it oughtn't to run.
> 
> systemd is using ifuncs to patch up the library migration it has done in 209
> so it only shows up when we enable compat lib support in systemd, and if we 
> patch the apps to forward port to systemd 209 then we don’t need to enable 
> compat lib support and
> it could be left alone.

Or we can cherry-pick 
http://cgit.freedesktop.org/systemd/systemd/commit/?id=03e37dd767e52908f30783d9b4c09fb6a4e865c7
 :)

> 
> if we want to enable compat libs/ifunc then we can think of adding 
> --enable-gnu-indirect-function
> to gcc configure but then it may not work on all architectures that we are 
> interested in.
> 
> 
>> Is this a uclibc thing?
> 
> no
> 
>> 
>> p.
>> 
>> 
> 

_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to