Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
steps.mk
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Wed Dec 05 20:31:43 2012 +0100 (2012-12-05)
changeset 3134 863723936e24
parent 3117 2b64e1b502cd
child 3162 e51eb0a614c7
permissions -rw-r--r--
scripts/xldd: use user's sed and grep

xldd uses sed and grep as detected by ./configure. This works well if is
used on the machine that build the toolchain.

But if the user moves the toolchain to another machine where sed and grep
are not in the same directory (eg. /bin/sed vs. /usr/bin/sed), then xldd
will stop functionning.

Fix that by using ${SED} and ${GREP} if they are set in the environment.

Reported-by: Samuel Martin <s.martin49@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> 
     1 # Makefile for each steps

     2 # Copyright 2006 Yann E. MORIN <yann.morin.1998@free.fr>

     3 

     4 # ----------------------------------------------------------

     5 # This is the steps help entry

     6 

     7 help-build::

     8 	@echo  '  list-steps         - List all build steps'

     9 

    10 help-env::

    11 	@echo  '  STOP=step          - Stop the build just after this step (list with list-steps)'

    12 	@echo  '  RESTART=step       - Restart the build just before this step (list with list-steps)'

    13 

    14 # ----------------------------------------------------------

    15 # The steps list

    16 

    17 # The _for_build steps are noop for native and cross,

    18 # but are actual steps for canadian and cross-native.

    19 # Please keep the last line with a '\' and keep the following empy line:

    20 # it helps when diffing and merging.

    21 CT_STEPS := libc_check_config        \

    22             companion_libs_for_build \

    23             binutils_for_build       \

    24             companion_libs_for_host  \

    25             binutils_for_host        \

    26             cc_core_pass_1           \

    27             kernel_headers           \

    28             libc_start_files         \

    29             cc_core_pass_2           \

    30             libc                     \

    31             cc_for_build             \

    32             cc_for_host              \

    33             libc_finish              \

    34             libelf_for_target        \

    35             binutils_for_target      \

    36             debug                    \

    37             test_suite               \

    38             finish                   \

    39 

    40 # Keep an empty line above this comment, so the last

    41 # back-slash terminated line works as expected.

    42 

    43 # Make the list available to sub-processes (scripts/crosstool-NG.sh needs it)

    44 export CT_STEPS

    45 

    46 # Print the steps list

    47 PHONY += list-steps

    48 list-steps:

    49 	@echo  'Available build steps, in order:'

    50 	@for step in $(CT_STEPS); do    \

    51 	     echo "  - $${step}";       \

    52 	 done

    53 	@echo  'Use "<step>" as action to execute only that step.'

    54 	@echo  'Use "+<step>" as action to execute up to that step.'

    55 	@echo  'Use "<step>+" as action to execute from that step onward.'

    56 

    57 # ----------------------------------------------------------

    58 # This part deals with executing steps

    59 

    60 $(CT_STEPS):

    61 	$(SILENT)$(MAKE) -rf $(CT_NG) V=$(V) RESTART=$@ STOP=$@ build

    62 

    63 $(patsubst %,+%,$(CT_STEPS)):

    64 	$(SILENT)$(MAKE) -rf $(CT_NG) V=$(V) STOP=$(patsubst +%,%,$@) build

    65 

    66 $(patsubst %,%+,$(CT_STEPS)):

    67 	$(SILENT)$(MAKE) -rf $(CT_NG) V=$(V) RESTART=$(patsubst %+,%,$@) build
crosstool-ng