On 29 January 2014 08:36, Wookey <woo...@wookware.org> wrote: > Someone asked if this worked, and I thought 'that's trivial to test with > multiarch' so I did. > On Saucy (where there is no multiarch version skew issue between binary > versions of packages) the > dpkg --add-architecutre armhf > apt-get update > apt-get install links:armhf > part works very nicely. Everything installs as required. > > However binaries don't run - they just get killed. > > Apparently no-one has tried this for a couple of years since it was > last working...(Or is it working on other platforms? - apparently it's OK > on android)
FYI: It seems OK with OE rootfs file systems too. Just booted 64 system with Linaro OE rootfs, nfs mounted similar rootfs but for 32bit, set up symlink for /lib/ld-linux-armhf.so.3, set correct LD_LIBRARY_PATH - don't see any issues with running 32 binaries so far .. tried few executables. Works in BE variant as well. I was running 3.13-rc3 kernel. Thanks, Victor > Turns out that our arm64 kernel config has: > vm.mmap_min_addr=65536 > but armhf binaries tend to get mmapped at 0x8000 (32K). > > On armhf that value is set to > vm.mmap_min_addr=4096 > > This difference is to protect page0 even if large pages are enabled > which seems sensible enough, but has this unfortunate side-effect. > > So either we need to stop doing that (What would be the consequences of > setting 4096 by default on arm64?) or change something in the loader to > stop mapping things below 64K, which I think involves glibc hackery. > > Running 32-bit binaries is quite seriously broken until this is fixed. I > presume this currently isn't on anyone's list to fix? I'm not sure who's > list it should go on. > > part2: Once this is fixed with: > sudo sysctl -w vm.mmap_min_addr=4096 > > some binaries work (hello, bzip2) but fancier things still don't (links, > wget). They segfault after loading libs. I'm still investigating that, > but it looks like we have at least two issues.. > > So this mail is really to ask what the best fix is and thus who will > deal with it? Do I need to file a bug or a card somewhere? > > Possibly more to follow when I work out what else is wrong... > > Wookey > -- > Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM > http://wookware.org/ > > _______________________________________________ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
