glibc issues with --enable-kernel=22.214.171.124
bruce.dubbs at gmail.com
Fri Jan 21 13:48:09 PST 2011
Matthew Burgess wrote:
>> I'm not sure about that. We are not building glibc against the host
>> kernel. We are using the most recent headers from section 6.7. By
>> specifying --enable-kernel= we are only telling the build system what
>> features to use.
> Yes, I understand that. However, when it comes to running the tests in
> chapter 6, we haven't yet rebooted into the LFS kernel yet. Therefore,
> the test results will obviously depend on whether or not the features
> they are testing for are available in the host kernel or not.
> For example, assume the host has a 126.96.36.199 kernel (our current earliest
> supported version). If we then specify --enable-kernel=2.6.30 to the
> chapter 6 Glibc build, that Glibc may contain features that are only
> available in 2.6.30 kernels and provides no fallbacks for the
> 188.8.131.52 version. At that point, running the tests or even trying to
> run any of the binaries linked against that version of Glibc could fail
> if they happen to touch those bits of Glibc that only support Linux >=
> 2.6.30. So, basically, if we bump the --enable-kernel parameter, we
> also need to bump the host system requirements.
OK, so do we use 184.108.40.206 (LFS-6.5)? Do we need to update any other
packages in the requirements or make everything from LFS-6.5 (Aug 2009)?
Right now, the minimum requirements are from LFS-6.3 (Aug 2007).
More information about the lfs-dev