libc/newlib: build newlib in the proper step

Currently, newlib is built in the start_file step, which is wrong, but was
needed when the baremetal integration was... well, 'unfinished'.

Now that we build the baremetal compiler from the final cc step, and a
proper core gcc in pass-1 and pass-2, we can move the newlib build to the
step do_libc, where it belongs.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

# Overall toolchain configuration: paths, jobs, etc...

# Allow unconditional usage of tristates

config MODULES

    bool

    default y

menu "Paths and misc options"

source "config/global/ct-behave.in"

source "config/global/paths.in"

source "config/global/download.in"

source "config/global/extract.in"

source "config/global/build-behave.in"

source "config/global/logging.in"

endmenu