diff options
author | Bryan Hundven <bryanhundven@gmail.com> | 2011-06-26 10:26:54 (GMT) |
---|---|---|
committer | Bryan Hundven <bryanhundven@gmail.com> | 2011-06-26 10:26:54 (GMT) |
commit | 6940a6c0ebe2b70804e9830128b65dc12fb2e48e (patch) | |
tree | 2ca7bf9d3f6bce32f2f52b8b2e4959fc59f08e05 /patches/gcc/3.4.6 | |
parent | fe5da0936ba5c98ea8d5e9dae566d2dcaf3e48a3 (diff) |
glibc: Refactor startfiles/headers into do_libc_backend()
Refactor the contents of 'do_libc_start_files()' and 'do_libc()' into a
parameterized 'do_libc_backend()'. 'do_libc_start_files()' and 'do_libc()'
call 'do_libc_backend()' with either 'libc_mode=startfiles' or
'libc_mode=final' (respectively) so that the startfiles/headers and
the final libc builds are configured and built with the same options.
One example of where this is needed is when building a mips toolchain.
Previously, if you were building an n32 toolchain, you wouldn't have
noticed an issue, because if '-mabi' is not in CFLAGS, n32 is the
default:
http://sourceware.org/git/?p=glibc-ports.git;a=blob;f=sysdeps/mips/preconfigure;hb=HEAD
But when trying to build an o32 or n64 toolchain the build would
have failed. This is because (e)glibc expects "-mabi={o32,n32,n64}" to be
in CFLAGS, but was not previously provided in 'do_libc_start_files()'.
The build failure would happen in the shared-core gcc when it tries to
configure an n64 or o32 gcc with an n32 libc.
A simpler solution would have been to just add TARGET_CFLAGS to configure
in 'do_libc_start_files()', but this way makes configure and make
consistent for both steps.
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
Diffstat (limited to 'patches/gcc/3.4.6')
0 files changed, 0 insertions, 0 deletions