| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
NOTE: This procedure DOES NOT WORK. I tried to avoid some ugly patches
and build system modifications that LFS uses by doing a sysroot build.
I messed up by not configuring GNU Binutils for a sysroot setup. But
this procedure is still kind of ugly anyway, so we'll be following a new
one based on Cross Linux From Scratch - Sysroot.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
NB: The cross-compiling EGLIBC configuration is wrong -- the Linux
compatibility version (the value of '--enable-kernel') is too high for
the host system. As a result, the configure script of Binutils fails
because any binaries built against this temporary EGLIBC can't be run on
the host system.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We built the cross-compiling GCC without a Stack Smashing Protector
(SSP) by passing the option '--disable-libssp' to its configure script
because otherwise we'd get a configure error when building GCC (as
mentioned in section 5.5.1 of Linux From Scratch version 7.0 and
experienced first-hand by this author). However, EGLIBC's configure
script incorrectly detects support for SSP and prepares EGLIBC to be
linked with SSP symbols. As a result, NSCD (EGLIBC's Name Service Cache
Daemon) fails to link due to undefined references to symbol
'__stack_chk_guard'.
So, we need to pass 'libc_cv_ssp=no' to EGLIBC's configure script to
tell it explicitly that we don't have SSP support in our build of GCC.
|
| | |
|
| | |
|
| | |
|
| |
|
