[systemd-devel] [PATCH] arch: add crisv32

[Lennart Poettering]

On Thu, 03.07.14 13:36, Simon McVittie (simon.mcvittie at collabora.co.uk) wrote:

> 
> On 03/07/14 12:09, Lennart Poettering wrote:
> >           32bit ARM (yay, at least 4 ABIs to choose from, well done!)
> 
> The current status quo in Debian and its derivatives seems to be "when
> introducing a new ARM flavour, the ARM and toolchain people argue about
> its canonical name for a while". There are more possible permutations
> than those four (arm, armel, armhf, armeb), they're just the ones where
> someone has made a serious attempt to build Debian.
> 
> I don't think you can necessarily infer the Debian multiarch tuple of
> containers/chroots (if that's what you're trying to do) from the
> compiler architecture, or even the Debian multiarch tuple, of systemd.

Well, what i care for is the "primary" multilib tuple that Debian would
is using when placing libraries bewlo /usr/lib/. "primary" for I would
simply bind to the tuple that systemd itself (being the init process and
all) is compiled in.

BTW, to clarify what this is about I will now rename the tupel macro
from ARCH_TUPLE to LIB_ARCH_TUPLE or so, since this is about locations
for shared libraries, nothing else.

> Debian armel systems can still run Debian arm (old ABI) executables -
> you have to use a chroot because the userland ABIs are different, but
> the kernel can go either way. Similarly, I think armhf systems can run
> armel executables, and possibly even arm OABI too.

Sure, I am completely aware of that, that's after all what multilib
stuff is about...

> If all you need is the multiarch tuple of the ABI with which systemd
> itself was compiled, for distributions that use Debian-style multiarch
> tuples, you might be better off providing a configure option
> "--with-multiarch-tuple" or something that overrides/ignores the
> #ifdef-based logic - then Debian could compile systemd with
> 
>     --with-multiarch-tuple=$(dpkg-architecture -qDEB_HOST_MULTIARCH)
> 
> and it would be completely unambiguous.

Well, I am particularly interested in getting this into place so that
the debian tuples are used regardless on which distro we built,
i.e. even on distros that lack dpkg-architecture.

BTW, Zbigniew added an entry for ARM now, but it only covers two of the
known ABIs...

Lennart

-- 
Lennart Poettering, Red Hat