TODO
author Bryan Hundven <bryanhundven@gmail.com>
Sun Jun 26 03:26:54 2011 -0700 (2011-06-26)
changeset 2515 364b06df9e3a
parent 1512 439a6b292917
child 2564 5d4e91c0343e
permissions -rw-r--r--
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>
yann@1335
     1
This is a somewhat ordered TODO list:
yann@1335
     2
yann@1335
     3
Recuring tasks:
yann@1335
     4
yann@1335
     5
- update versions for every tools...
yann@1335
     6
yann@1731
     7
- update and/or upgrade all samples
yann@1731
     8
yann@1335
     9
yann@1403
    10
Non-recurring tasks:
yann@1335
    11
yann@1731
    12
- update newlib (for enhanced bare metal)
yann@1731
    13
  - confirm existing implementation on targets other than AVR32
yann@1731
    14
  - try to make it generic, will help for uClibc++
yann@1512
    15
yann@1731
    16
- multilib
yann@1335
    17
yann@1731
    18
- Cygwin target (needs newlib)
yann@1731
    19
  - so we can build toolchains that generate code for Windows/Cygwin
yann@1731
    20
yann@1731
    21
- Cygwin host
yann@1731
    22
  - so we can build toolchains that run natively under Windows/Cygwin
yann@1731
    23
yann@1731
    24
- mingw32 target
yann@1731
    25
  - so we can build toolchains that generate code for Windows/Win32
yann@1731
    26
yann@1731
    27
- mingw32 host
yann@1731
    28
  - so we can build toolchains that run natively under Windows/Win32
yann@1731
    29
    (without requiring Cygwin)
yann@1335
    30
yann@1335
    31
- uClibc++
yann@1335
    32
  - see newlib, above
yann@1335
    33
yann@1731
    34
- uClinux
yann@1731
    35
  - check whether we can use newlib under uClinux (?)