| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Also disable some things when cross-compiling gcc in stage1-gcc to sync
with LFS instructions: these things don't cross-compile.
WIP!!: Some python programs won't work with core-dumps.. It looks like
libffi when compiled is wrong. If you recompile it on top of the final
system (once running) it works.
A simple example of what won't work is `glance --version`.
Change-Id: I340fd4c7fd005807132d178d4ea8183770820926
|
| |
|
|
| |
Change-Id: I0e2b2c2f823e89b1bcbba6149fa6d92dce3d07cb
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit acb29d344d117133891199ea536d9c4d34c7d05e.
We have discovered that Baserock systems built with GCC 5.1 cannot
*deploy* working disk images. The images hang in SYSLINUX. We suspect
that it is a bug in SYSLINUX that is triggered by the compiler upgrade,
and upgrading SYSLINUX may well fix this issue, but we don't have time
to do this and test it in time for a 15.19 release
Change-Id: I3c661b14fb923eee37c4c0148904620362fe62e2
|
| |
|
|
| |
Change-Id: Iad8f11341a4a770c14393a50d1b0d3e26c076dbf
|
|
|
Update the GCC compiler to the 4.9.2 version. It turns out that a C++
compiler is required to build the latest GCC releases, so build one in
stages 1 and 2 as well.
The updated list of GCC configuration options that either don't work in
a cross compiler or are not needed in a temporary compiler, were based
on the latest instructions from Linux From Scratch.
The inclusion of /lib64 in the lib path for the stage 1 linker is an
attempt to turn things more robust rather than to just symlink in /lib
stuff that ends up installed in /lib64 (as it is already being done for
libgcc_s.so). Ideally, we should configure every chunk to install to
/lib, however GCC seems to not honour the `--with-libdir` configuration
flag.
With this version of GCC, it looks like a sysroot needs to be given at
configure time so that `--with-native-system-header-dir` does what it
claims to do. Unfortunately, this has the side effect of making GCC not
passing to the linker the linker sysroot flag: `-Wl,--sysroot=$SYSROOT`.
The workaround is to modify LDFLAGS to give a sysroot directly to GCC,
`--sysroot=$SYSROOT`, which will then be further passed down to the
linker.
As the newest version of GCC finds more warnings than the previous one,
`-Werror` was disabled for the coreutils, GDB and Syslinux projects.
Syslinux's Makefile had to be patched, as it is not possible to disable
`-Werror` for all targets through the NO_WERROR variable.
The hack to handle libgcc_eh being required during eglibc's build was
removed, as it doesn't seem to be the case anymore.
|
