Re: glibc: disabling armhf ldconfig support
On Thu, Jul 05, 2012 at 12:08:06AM +0200, Aurelien Jarno wrote:
>Hi,
>
>At the end of last year the patch unsubmitted-ldconfig-cache-abi.diff
>has been added, but has not been submitted upstream despite asking a few
>times. This patch provides correct ldconfig support for systems with
>both armel and armhf libraries.
>
>The situation is now that this patch breaks MIPS N64 support due
>to a missing break in a case (easily fixable), but also that upstream
>has reused the same tag value for x32 support:
>
> Debian 2.13:
> #define FLAG_ARM_HFABI 0x0800
>
> Upstream HEAD:
> #define FLAG_X8664_LIBX32 0x0800
Sigh.
>As a consequence the armhf value will have to be changed in the future,
>which might have some side effects.
We'd have to make sure that the ldconfig cache is re-generated after
the change, to make sure things don't break.
>For now I guess the best change is simply to disable this patch for
>wheezy, which is already done in the SVN, and will land to send in the
>next upload. I'll ask debian-release to allow migration of the package
>to wheezy. I am also ready to re-enable this patch for wheezy once it
>has been merged upstream, or even when at least the tag value is merged
>upstream.
I'm in the middle of re-working the patch for upstream, but it's slow
going at the moment. I'm trying to get reviews for definitions of the
PT_ARM_ARCH_EXT segment, and that's been held up. :-(
Cheers,
--
Steve McIntyre steve.mcintyre@linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
Reply to: