steps.mk
author "Benoît THÉBAUDEAU" <benoit.thebaudeau@advansee.com>
Thu Jul 28 22:09:31 2011 +0200 (2011-07-28)
changeset 2573 424fa2092ace
parent 2278 e86826b8621a
child 2905 286b2937c101
child 2912 6467c949c91c
permissions -rw-r--r--
scripts/libc: do not build add-ons by default

Currently, no --enable-add-ons option is passed to libc configure when
"$(do_libc_add_ons_list ,)" is empty, which makes configure automatically search
for present add-ons. In that case, all present add-ons are built, although
no add-on was selected by the user in the config. Moreover, this can make the
configure fail if some non-standard add-ons like eglibc-localedef are present.

This behavior also leads to an inconsistency from a user point of view between
the following cases:
- LIBC_ADDONS_LIST="", LIBC_GLIBC_USE_PORTS=n and THREADS="none" in the config,
which makes "$(do_libc_add_ons_list ,)" return "", so all present add-ons
are built.
- LIBC_ADDONS_LIST="", LIBC_GLIBC_USE_PORTS=n and THREADS!="none" in the
config, which makes "$(do_libc_add_ons_list ,)" return the add-on supporting
the chosen threading implementation, e.g. "nptl", so only this add-on is
built.

This patch disables the building of all add-ons in that case.

It is still possible to build all present add-ons by adding --enable-add-ons to
LIBC_GLIBC_EXTRA_CONFIG_ARRAY.

Signed-off-by: "Benoît THÉBAUDEAU" <benoit.thebaudeau@advansee.com>
yann@136
     1
# Makefile for each steps
yann@136
     2
# Copyright 2006 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
yann@136
     3
yann@1001
     4
# ----------------------------------------------------------
yann@1001
     5
# This is the steps help entry
yann@1001
     6
yann@1001
     7
help-build::
yann@1001
     8
	@echo  '  list-steps         - List all build steps'
yann@1001
     9
yann@1015
    10
help-env::
yann@1876
    11
	@echo  '  STOP=step          - Stop the build just after this step (list with list-steps)'
yann@1876
    12
	@echo  '  RESTART=step       - Restart the build just before this step (list with list-steps)'
yann@1015
    13
yann@1001
    14
# ----------------------------------------------------------
yann@1001
    15
# The steps list
yann@1001
    16
yann@1149
    17
# Please keep the last line with a '\' and keep the following empy line:
yann@1001
    18
# it helps when diffing and merging.
yann@461
    19
CT_STEPS := libc_check_config   \
yann@466
    20
            gmp                 \
yann@466
    21
            mpfr                \
yann@1324
    22
            ppl                 \
yann@1380
    23
            cloog               \
yann@1384
    24
            mpc                 \
yann@1811
    25
            libelf              \
yann@461
    26
            binutils            \
yann@1337
    27
            elf2flt             \
yann@1854
    28
            sstrip              \
yann@461
    29
            cc_core_pass_1      \
yann@2304
    30
            kernel_headers      \
yann@461
    31
            libc_start_files    \
yann@461
    32
            cc_core_pass_2      \
yann@461
    33
            libc                \
yann@461
    34
            cc                  \
yann@461
    35
            libc_finish         \
yann@1811
    36
            libelf_target       \
yann@1034
    37
            binutils_target     \
yann@461
    38
            debug               \
mgl@1965
    39
            test_suite          \
yann@1149
    40
            finish              \
yann@461
    41
yann@1143
    42
# Make the list available to sub-processes (scripts/crosstool-NG.sh needs it)
yann@461
    43
export CT_STEPS
yann@181
    44
yann@1001
    45
# Print the steps list
yann@1001
    46
PHONY += list-steps
yann@1001
    47
list-steps:
yann@1001
    48
	@echo  'Available build steps, in order:'
yann@1001
    49
	@for step in $(CT_STEPS); do    \
yann@1001
    50
	     echo "  - $${step}";       \
yann@1001
    51
	 done
yann@1001
    52
	@echo  'Use "<step>" as action to execute only that step.'
yann@1001
    53
	@echo  'Use "+<step>" as action to execute up to that step.'
yann@1001
    54
	@echo  'Use "<step>+" as action to execute from that step onward.'
yann@1001
    55
yann@1001
    56
# ----------------------------------------------------------
yann@1001
    57
# This part deals with executing steps
yann@1001
    58
yann@181
    59
$(CT_STEPS):
yann@1010
    60
	$(SILENT)$(MAKE) -rf $(CT_NG) V=$(V) RESTART=$@ STOP=$@ build
yann@136
    61
yann@304
    62
$(patsubst %,+%,$(CT_STEPS)):
yann@1010
    63
	$(SILENT)$(MAKE) -rf $(CT_NG) V=$(V) STOP=$(patsubst +%,%,$@) build
yann@136
    64
yann@304
    65
$(patsubst %,%+,$(CT_STEPS)):
yann@1010
    66
	$(SILENT)$(MAKE) -rf $(CT_NG) V=$(V) RESTART=$(patsubst %+,%,$@) build