On Sat, Feb 22, 2014 at 06:12:10PM +0000, Phil Blundell 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? 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. > Is this a uclibc thing?
I'm seeing lots of compile errors like this:
| arm-oe-linux-gnueabi-libtool: link: arm-oe-linux-gnueabi-ranlib
.libs/libsystemd-units.a
| libsystemd-id128.c:6:6: error: ifunc is not supported in this configuration
| void sd_id128_to_string(void)
__attribute__((ifunc("resolve_sd_id128_to_string")));
| ^
--
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
_______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
