pffiu ...You were right it's not passed to gcc. You hold one Greg thanks you ! ... I saw that the target echo: and the make echo echoes every variables in makefile.settings (fallback's one)
In makefile, there is D_item function that's called on each VARIABLES from included Makefile.settings. Theses calls are made by CPUFLAGS : it's empty whereas VARIABLES is containing MAX_REBOOT_CNT.
In visu: Added in target echo: @echo CPUFLAGS='$(CPUFLAGS)' @echo VARIABLES='$(VARIABLES)' tried and as a result got this: CPUFLAGS= VARIABLES= ARCH CROSS_COMPILE CC ... ... MAX_REBOOT_CNT .... XIP_ROM_BASE XIP_ROM_SIZE
er .. Well my makefile is corrumpt, buggy, or so ? I used LB 1.1.6 is it knowed to bug somehow like my problem ?
On the "buggy side" here's what i've thought : It could be a D_item malfunction (but i can't point which one) or a bad call in CPUFLAGS (but i'am less confident in this way)
There is the head -20 of it : ------------------------------------------ # File: via/epia/epia/fallback/Makefile # This file was generated by 'via/epia/epia/config.py via/epia/Config.lb /home/root/projet/freebios/freebios2'
# Get the value of TOP, VARIABLES, and several other variables. include Makefile.settings
# Function to create an item like -Di586 or -DCONFIG_MAX_CPUS='1' or -Ui686 D_item = $(if $(subst undefined,,$(origin $1)),-D$1$(if $($1),='$($1)',),-U$1)
# Compute the value of CPUFLAGS here during make's first pass. CPUFLAGS := $(foreach _var_,$(VARIABLES),$(call D_item,$(_var_)))
CPP:= $(CC) -no-gcc -x assembler-with-cpp -DASSEMBLY -E LIBGCC_FILE_NAME := $(shell $(CC) -print-libgcc-file-name) GCC_INC_DIR := $(shell $(CC) -print-search-dirs | sed -ne "s/install: (.*)/\1include/gp") CPPFLAGS := -I$(TOP)/src/include -I$(TOP)/src/arch/$(ARCH)/include -I$(GCC_INC_DIR) $(CPUFLAGS) ROMCCPPFLAGS := -D__ROMCC__=0 -D__ROMCC_MINOR__=38 CFLAGS := $(CPU_OPT) $(CPPFLAGS) -Os -nostdinc -nostdlib -fno-builtin -Wall HOSTCFLAGS:= -Os -Wall LINUXBIOS_PAYLOAD-$(CONFIG_COMPRESS):=linuxbios_payload.nrv2b ---------------------------------------------
What do you think about this ? I also can't help recalling that this makefile has been built by buildtarget,could it be involved ?
mathieu
Le jeu 08/04/2004 à 19:12, Greg Watson a écrit :
Check the Makefile.settings in the fallback directory and see if MAX_REBOOT_CNT is defined. If it isn't then there's some problem with the configuration. If it is, then it's not getting passed to the gcc command line.
Greg
On 08/04/2004, at 10:23 AM, Mathieu Deschamps wrote:
I'am building a new rom but now,I got stuck because of #error "MAX_REBOOT_CNT not defined" in make process of build target even though i defined this in Config.lb