From: Martin Jansa <martin.jansa@gmail.com>
To: Phil Blundell <pb@pbcl.net>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFT][PATCH 0/2] Systemd 209
Date: Sat, 22 Feb 2014 21:47:10 +0100 [thread overview]
Message-ID: <20140222204710.GQ3854@jama> (raw)
In-Reply-To: <1393092730.2640.25.camel@e130.pbcl.net>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
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.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-02-22 20:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 10:18 [RFT][PATCH 0/2] Systemd 209 Khem Raj
2014-02-21 3:48 ` Saul Wold
2014-02-21 3:50 ` Khem Raj
2014-02-21 15:16 ` Martin Jansa
2014-02-21 15:21 ` Richard Purdie
2014-02-21 16:33 ` Khem Raj
2014-02-22 7:57 ` Koen Kooi
2014-02-22 8:49 ` Richard Purdie
2014-02-22 9:31 ` Khem Raj
2014-02-22 18:12 ` Phil Blundell
2014-02-22 19:52 ` Khem Raj
2014-02-23 7:36 ` Koen Kooi
2014-02-25 0:28 ` Martin Jansa
2014-02-22 20:47 ` Martin Jansa [this message]
2014-02-22 21:12 ` Khem Raj
2014-02-26 7:14 ` Khem Raj
2014-02-26 9:00 ` Saul Wold
2014-02-26 17:58 ` Khem Raj
2014-02-21 16:32 ` Khem Raj
2014-02-22 12:03 ` Martin Jansa
2014-02-22 17:29 ` [meta-oe][PATCH] polkit: make it compatible with systemd-209 Martin Jansa
2014-02-22 17:29 ` [PATCH] pulseaudio: Make " Martin Jansa
2014-02-22 18:10 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140222204710.GQ3854@jama \
--to=martin.jansa@gmail.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox