[OE-core] [PATCH 1/4] glibc: Remove site_config and glibc-initial

Burton, Ross ross.burton at intel.com
Thu Dec 20 19:47:15 UTC 2018


On Thu, 20 Dec 2018 at 18:02, Mark Hatle <mark.hatle at windriver.com> wrote:
> We also still want a way that manual definitions can be setup on a global basis
> for a given architecture.  (We do want these limited for the most part, since
> maintenance is overlooked -- but we've certainly seen cases in the past where
> configure works like this:  Yes, No, Cross -- where cross defines 'No' and never
> checks.   This functions, but ends up in a significantly less optimized
> situation, and these are incredibly difficult to identify.  [Using QEMU isn't an
> option, as QEMU doesn't know -all- potential architectures...]

These are absolutely not going away, and I've even got a patch locally
that can make autoconf throw a warning if it uses a hard-coded guess
when its cross-compiling.  The output is shocking...

eg this is why our Python wasn't actually capable of doing floating
point math properly: it was using runtime tests to determine bit
order, and fell back to "don't know", and floating emulation in
software.  I fixed this upstream to just look at bit order in a
binary, so the test is faster and works in cross.

Since the early days of siteconfig though a lot has changed in
autoconf.  It can do sizeof() without running, for a start.  It's a
lot faster in general, so I really do think that the usefulness of
siteconfig is really limited, especially considering how fragile it is
if you actually use it.

Ross


More information about the Openembedded-core mailing list