[ECOS] New problem with building eCos--see output

[ECOS] New problem with building eCos--see output

[Gregg C Levine]

Hello from Gregg C Levine
It seems I am forever having problems with eCos. This time during the
building of Red Boot, the build process gets interrupted when it needs
to decide if the board in question will have any flash memory. (It
will, I don't know how much.) That step stops it from continuing from
building any form of Red Boot. Prior to the inclusion of the ECM file
for building a redboot.bin binary, it worked and I could get a
redboot.elf file built. I've put the output from the whole process
below my signature. The usual rules apply.
-------------------
Gregg C Levine hansolofalcon@worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )
----------
sh -c "export PATH=/opt/ecos/gnutools/i386-elf/bin:$PATH; unset
GDBTK_LIBRARY; unset GCC_EXEC_PREFIX; export
ECOS_REPOSITORY=/opt/ecos/ecos-2.0/packages; make --directory
/usr/src/ecoswork/pc386/test1_build"

make: Entering directory `/usr/src/ecoswork/pc386/test1_build'
make -r -C hal/i386/arch/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make -r -C hal/i386/generic/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/generic/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/generic/v2_0'
make -r -C hal/i386/pc/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pc/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pc/v2_0'
make -r -C hal/i386/pcmb/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pcmb/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pcmb/v2_0'
make -r -C io/pci/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/io/pci/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/io/pci/v2_0'
make -r -C devs/eth/intel/i82559/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/intel/i82559/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/intel/i82559/v2_0'
make -r -C devs/eth/i386/pc/i82559/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/i386/pc/i82559/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/i386/pc/i82559/v2_0'
make -r -C hal/common/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/common/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/common/v2_0'
make -r -C infra/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/infra/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/infra/v2_0'
make -r -C redboot/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/redboot/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/redboot/v2_0'
make -r -C isoinfra/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/isoinfra/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/isoinfra/v2_0'
make -r -C language/c/libc/string/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/language/c/libc/string/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/language/c/libc/string/v2_0'
make -r -C net/ns/dns/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/net/ns/dns/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/net/ns/dns/v2_0'
make -r -C services/crc/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/services/crc/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/services/crc/v2_0'
make -r -C services/compress/zlib/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/services/compress/zlib/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/services/compress/zlib/v2_0'
make -r -C io/flash/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/io/flash/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/io/flash/v2_0'
make -r -C io/eth/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/io/eth/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/io/eth/v2_0'
headers finished
make -r -C hal/i386/arch/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make -r -C hal/i386/generic/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/generic/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/generic/v2_0'
make -r -C hal/i386/pc/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pc/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pc/v2_0'
make -r -C hal/i386/pcmb/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pcmb/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pcmb/v2_0'
make -r -C io/pci/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/io/pci/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/io/pci/v2_0'
make -r -C devs/eth/intel/i82559/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/intel/i82559/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/intel/i82559/v2_0'
make -r -C devs/eth/i386/pc/i82559/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/i386/pc/i82559/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/i386/pc/i82559/v2_0'
make -r -C hal/common/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/common/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/common/v2_0'
make -r -C infra/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/infra/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/infra/v2_0'
make -r -C redboot/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/redboot/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/redboot/v2_0'
make -r -C isoinfra/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/isoinfra/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/isoinfra/v2_0'
make -r -C language/c/libc/string/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/language/c/libc/string/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/language/c/libc/string/v2_0'
make -r -C net/ns/dns/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/net/ns/dns/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/net/ns/dns/v2_0'
make -r -C services/crc/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/services/crc/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/services/crc/v2_0'
make -r -C services/compress/zlib/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/services/compress/zlib/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/services/compress/zlib/v2_0'
make -r -C io/flash/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/io/flash/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/io/flash/v2_0'
make -r -C io/eth/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/io/eth/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/io/eth/v2_0'
make -r -C hal/common/v2_0
/usr/src/ecoswork/pc386/test1_install/lib/extras.o
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/common/v2_0'
make[1]: `/usr/src/ecoswork/pc386/test1_install/lib/extras.o' is up to
date.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/common/v2_0'
make -r -C hal/i386/arch/v2_0
/usr/src/ecoswork/pc386/test1_install/lib/vectors.o
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make[1]: `/usr/src/ecoswork/pc386/test1_install/lib/vectors.o' is up
to date.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make -r -C hal/i386/arch/v2_0
/usr/src/ecoswork/pc386/test1_install/lib/target.ld
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make[1]: `/usr/src/ecoswork/pc386/test1_install/lib/target.ld' is up
to date.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make -r -C redboot/v2_0
/usr/src/ecoswork/pc386/test1_install/bin/redboot.elf
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/redboot/v2_0'
i386-elf-gcc -c  -I/usr/src/ecoswork/pc386/test1_install/include
-I/opt/ecos/ecos-2.0/packages/redboot/v2_0
-I/opt/ecos/ecos-2.0/packages/redboot/v2_0/src
-I/opt/ecos/ecos-2.0/packages/redboot/v2_0/tests -I. -Wall
-Wpointer-arith -Wstrict-prototypes -Winline -Wundef
-Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections
-fno-rtti -fno-exceptions -fvtable-gc -finit-priority -o
/usr/src/ecoswork/pc386/test1_install/lib/version.o
/opt/ecos/ecos-2.0/packages/redboot/v2_0/src/version.c
i386-elf-gcc -g -nostdlib -Wl,--gc-sections -Wl,-static
-L/usr/src/ecoswork/pc386/test1_install/lib -Ttarget.ld -o
/usr/src/ecoswork/pc386/test1_install/bin/redboot.elf
/usr/src/ecoswork/pc386/test1_install/lib/version.o
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/redboot/v2_0'
/usr/src/ecoswork/pc386/test1_install/lib/libtarget.a(redboot_main.o):
In function `bist':
make: Leaving directory `/usr/src/ecoswork/pc386/test1_build'
/opt/ecos/ecos-2.0/packages/redboot/v2_0/src/main.c:626: undefined
reference to `_flash_info'

collect2: ld returned 1 exit status
make[1]: *** [/usr/src/ecoswork/pc386/test1_install/bin/redboot.elf]
Error 1
make: *** [build] Error 2

sh -c "export PATH=/opt/ecos/gnutools/i386-elf/bin:$PATH; unset
GDBTK_LIBRARY; unset GCC_EXEC_PREFIX; export
ECOS_REPOSITORY=/opt/ecos/ecos-2.0/packages; make --directory
/usr/src/ecoswork/pc386/test1_build"

make: Entering directory `/usr/src/ecoswork/pc386/test1_build'
make -r -C hal/i386/arch/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make -r -C hal/i386/generic/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/generic/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/generic/v2_0'
make -r -C hal/i386/pc/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pc/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pc/v2_0'
make -r -C hal/i386/pcmb/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pcmb/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pcmb/v2_0'
make -r -C io/pci/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/io/pci/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/io/pci/v2_0'
make -r -C devs/eth/intel/i82559/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/intel/i82559/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/intel/i82559/v2_0'
make -r -C devs/eth/i386/pc/i82559/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/i386/pc/i82559/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/i386/pc/i82559/v2_0'
make -r -C hal/common/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/common/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/common/v2_0'
make -r -C infra/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/infra/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/infra/v2_0'
make -r -C redboot/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/redboot/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/redboot/v2_0'
make -r -C isoinfra/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/isoinfra/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/isoinfra/v2_0'
make -r -C language/c/libc/string/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/language/c/libc/string/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/language/c/libc/string/v2_0'
make -r -C net/ns/dns/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/net/ns/dns/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/net/ns/dns/v2_0'
make -r -C services/crc/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/services/crc/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/services/crc/v2_0'
make -r -C services/compress/zlib/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/services/compress/zlib/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/services/compress/zlib/v2_0'
make -r -C io/flash/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/io/flash/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/io/flash/v2_0'
make -r -C io/eth/v2_0 headers
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/io/eth/v2_0'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/io/eth/v2_0'
headers finished
make -r -C hal/i386/arch/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make -r -C hal/i386/generic/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/generic/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/generic/v2_0'
make -r -C hal/i386/pc/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pc/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pc/v2_0'
make -r -C hal/i386/pcmb/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pcmb/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/pcmb/v2_0'
make -r -C io/pci/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/io/pci/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/io/pci/v2_0'
make -r -C devs/eth/intel/i82559/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/intel/i82559/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/intel/i82559/v2_0'
make -r -C devs/eth/i386/pc/i82559/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/i386/pc/i82559/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/devs/eth/i386/pc/i82559/v2_0'
make -r -C hal/common/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/common/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/common/v2_0'
make -r -C infra/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/infra/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/infra/v2_0'
make -r -C redboot/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/redboot/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/redboot/v2_0'
make -r -C isoinfra/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/isoinfra/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/isoinfra/v2_0'
make -r -C language/c/libc/string/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/language/c/libc/string/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/language/c/libc/string/v2_0'
make -r -C net/ns/dns/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/net/ns/dns/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/net/ns/dns/v2_0'
make -r -C services/crc/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/services/crc/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/services/crc/v2_0'
make -r -C services/compress/zlib/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/services/compress/zlib/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/services/compress/zlib/v2_0'
make -r -C io/flash/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/io/flash/v2_0'
i386-elf-gcc -c  -I/usr/src/ecoswork/pc386/test1_install/include
-I/opt/ecos/ecos-2.0/packages/io/flash/v2_0
-I/opt/ecos/ecos-2.0/packages/io/flash/v2_0/src
-I/opt/ecos/ecos-2.0/packages/io/flash/v2_0/tests -I.
-I/opt/ecos/ecos-2.0/packages/io/flash/v2_0/src/ -Wall -Wpointer-arith
-Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -g -O2
-ffunction-sections -fdata-sections -fno-rtti -fno-exceptions
-fvtable-gc -finit-priority -Wp,-MD,src/flash.tmp -o
src/io_flash_flash.o
/opt/ecos/ecos-2.0/packages/io/flash/v2_0/src/flash.c
i386-elf-ar rcs /usr/src/ecoswork/pc386/test1_install/lib/libtarget.a
src/io_flash_flash.o
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/io/flash/v2_0'
make -r -C io/eth/v2_0 build
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/io/eth/v2_0'
make[1]: Nothing to be done for `build'.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/io/eth/v2_0'
make -r -C hal/common/v2_0
/usr/src/ecoswork/pc386/test1_install/lib/extras.o
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/common/v2_0'
make[1]: `/usr/src/ecoswork/pc386/test1_install/lib/extras.o' is up to
date.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/common/v2_0'
make -r -C hal/i386/arch/v2_0
/usr/src/ecoswork/pc386/test1_install/lib/vectors.o
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make[1]: `/usr/src/ecoswork/pc386/test1_install/lib/vectors.o' is up
to date.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make -r -C hal/i386/arch/v2_0
/usr/src/ecoswork/pc386/test1_install/lib/target.ld
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make[1]: `/usr/src/ecoswork/pc386/test1_install/lib/target.ld' is up
to date.
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/hal/i386/arch/v2_0'
make -r -C redboot/v2_0
/usr/src/ecoswork/pc386/test1_install/bin/redboot.elf
make[1]: Entering directory
`/usr/src/ecoswork/pc386/test1_build/redboot/v2_0'
i386-elf-gcc -c  -I/usr/src/ecoswork/pc386/test1_install/include
-I/opt/ecos/ecos-2.0/packages/redboot/v2_0
-I/opt/ecos/ecos-2.0/packages/redboot/v2_0/src
-I/opt/ecos/ecos-2.0/packages/redboot/v2_0/tests -I. -Wall
-Wpointer-arith -Wstrict-prototypes -Winline -Wundef
-Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections
-fno-rtti -fno-exceptions -fvtable-gc -finit-priority -o
/usr/src/ecoswork/pc386/test1_install/lib/version.o
/opt/ecos/ecos-2.0/packages/redboot/v2_0/src/version.c
i386-elf-gcc -g -nostdlib -Wl,--gc-sections -Wl,-static
-L/usr/src/ecoswork/pc386/test1_install/lib -Ttarget.ld -o
/usr/src/ecoswork/pc386/test1_install/bin/redboot.elf
/usr/src/ecoswork/pc386/test1_install/lib/version.o
/usr/src/ecoswork/pc386/test1_install/lib/libtarget.a(redboot_main.o):
In function `bist':
/opt/ecos/ecos-2.0/packages/redboot/v2_0/src/main.c:626: undefined
reference to `_flash_info'
make[1]: Leaving directory
`/usr/src/ecoswork/pc386/test1_build/redboot/v2_0'
collect2: ld returned 1 exit status
make: Leaving directory `/usr/src/ecoswork/pc386/test1_build'
make[1]: *** [/usr/src/ecoswork/pc386/test1_install/bin/redboot.elf]
Error 1

make: *** [build] Error 2





--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] New problem with building eCos--see output

[Gary Thomas]

On Mon, 2003-11-10 at 20:32, Gregg C Levine wrote:
> Hello from Gregg C Levine
> It seems I am forever having problems with eCos. This time during the
> building of Red Boot, the build process gets interrupted when it needs
> to decide if the board in question will have any flash memory. (It
> will, I don't know how much.) That step stops it from continuing from
> building any form of Red Boot. Prior to the inclusion of the ECM file
> for building a redboot.bin binary, it worked and I could get a
> redboot.elf file built. I've put the output from the whole process
> below my signature. The usual rules apply.

What platform is this for?  How did you configure it?

What I can see from the dump you sent is that somehow you've enabled
the FLASH sub-system, but there are no FLASH drivers present.  This
is not supposed to happen, so I'd like to know the steps you took
to get here.

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] New problem with building eCos--see output

[Gregg C Levine]

Hello (again) from Gregg C Levine
This is for an ordinary x86 based computer setup, something along the
lines of the unit that I used to build the binaries on. It's the I386
template.
-------------------
Gregg C Levine hansolofalcon@worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com [mailto:ecos-discuss-
> owner@sources.redhat.com] On Behalf Of Gary Thomas
> Sent: Tuesday, November 11, 2003 7:44 AM
> To: Gregg C Levine
> Cc: ecos-discuss@sources.redhat.com
> Subject: Re: [ECOS] New problem with building eCos--see output
> 
> On Mon, 2003-11-10 at 20:32, Gregg C Levine wrote:
> > Hello from Gregg C Levine
> > It seems I am forever having problems with eCos. This time during
the
> > building of Red Boot, the build process gets interrupted when it
needs
> > to decide if the board in question will have any flash memory. (It
> > will, I don't know how much.) That step stops it from continuing
from
> > building any form of Red Boot. Prior to the inclusion of the ECM
file
> > for building a redboot.bin binary, it worked and I could get a
> > redboot.elf file built. I've put the output from the whole process
> > below my signature. The usual rules apply.
> 
> What platform is this for?  How did you configure it?
> 
> What I can see from the dump you sent is that somehow you've enabled
> the FLASH sub-system, but there are no FLASH drivers present.  This
> is not supposed to happen, so I'd like to know the steps you took
> to get here.
> 
> --
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates
> 
> 
> --
> Before posting, please read the FAQ:
http://sources.redhat.com/fom/ecos
> and search the list archive:
http://sources.redhat.com/ml/ecos-discuss



--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] New problem with building eCos--see output

[Gary Thomas]

On Tue, 2003-11-11 at 09:57, Gregg C Levine wrote:
> Hello (again) from Gregg C Levine
> This is for an ordinary x86 based computer setup, something along the
> lines of the unit that I used to build the binaries on. It's the I386
> template.

Sorry, but a hand-waving response doesn't help much.

  Exactly what steps did you follow?  
  Did you use ecosconfig or the ConfigTool?
  How did you configure eCos, including any options that you set, etc?

Without this level of detail, I'm afraid we'd only be guessing.

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] New problem with building eCos--see output

[Gregg C Levine]

Hello (again) from Gregg C Levine
I don't follow you. 
But, all I did was select the I386 template from the pull down menus,
using the regular configuration tool, select red boot, from that.
Build that one, and got the red boot ELF image. Imported the ECM file
that I was originally instructed to import to create the red boot BIN
image. And then followed the usual steps. Since the board itself, is
currently the Bochs unit, I haven't selected a physical one, and can't
actually decide if there will be flash memory involved, or not. Now
those are the steps I chose. All of them.
-------------------
Gregg C Levine hansolofalcon@worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com [mailto:ecos-discuss-
> owner@sources.redhat.com] On Behalf Of Gary Thomas
> Sent: Tuesday, November 11, 2003 12:02 PM
> To: Gregg C Levine
> Cc: ecos-discuss@sources.redhat.com
> Subject: RE: [ECOS] New problem with building eCos--see output
> 
> On Tue, 2003-11-11 at 09:57, Gregg C Levine wrote:
> > Hello (again) from Gregg C Levine
> > This is for an ordinary x86 based computer setup, something along
the
> > lines of the unit that I used to build the binaries on. It's the
I386
> > template.
> 
> Sorry, but a hand-waving response doesn't help much.
> 
>   Exactly what steps did you follow?
>   Did you use ecosconfig or the ConfigTool?
>   How did you configure eCos, including any options that you set,
etc?
> 
> Without this level of detail, I'm afraid we'd only be guessing.
> 
> --
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates
> 
> 
> --
> Before posting, please read the FAQ:
http://sources.redhat.com/fom/ecos
> and search the list archive:
http://sources.redhat.com/ml/ecos-discuss


--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] New problem with building eCos--see output

[Gary Thomas]

On Tue, 2003-11-11 at 10:17, Gregg C Levine wrote:
> Hello (again) from Gregg C Levine
> I don't follow you. 
> But, all I did was select the I386 template from the pull down menus,
> using the regular configuration tool, select red boot, from that.
> Build that one, and got the red boot ELF image. Imported the ECM file
> that I was originally instructed to import to create the red boot BIN
> image. And then followed the usual steps. Since the board itself, is
> currently the Bochs unit, I haven't selected a physical one, and can't
> actually decide if there will be flash memory involved, or not. Now
> those are the steps I chose. All of them.

Which .ecm file?

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] New problem with building eCos--see output

[Gregg C Levine]

Hello (again) from Gregg C Levine
Okay, it was the redboot_XXX.ecm file. Any clews?
-------------------
Gregg C Levine hansolofalcon@worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com [mailto:ecos-discuss-
> owner@sources.redhat.com] On Behalf Of Gary Thomas
> Sent: Tuesday, November 11, 2003 12:20 PM
> To: Gregg C Levine
> Cc: ecos-discuss@sources.redhat.com
> Subject: RE: [ECOS] New problem with building eCos--see output
> 
> On Tue, 2003-11-11 at 10:17, Gregg C Levine wrote:
> > Hello (again) from Gregg C Levine
> > I don't follow you.
> > But, all I did was select the I386 template from the pull down
menus,
> > using the regular configuration tool, select red boot, from that.
> > Build that one, and got the red boot ELF image. Imported the ECM
file
> > that I was originally instructed to import to create the red boot
BIN
> > image. And then followed the usual steps. Since the board itself,
is
> > currently the Bochs unit, I haven't selected a physical one, and
can't
> > actually decide if there will be flash memory involved, or not.
Now
> > those are the steps I chose. All of them.
> 
> Which .ecm file?
> 
> --
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates
> 
> 
> --
> Before posting, please read the FAQ:
http://sources.redhat.com/fom/ecos
> and search the list archive:
http://sources.redhat.com/ml/ecos-discuss


--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] New problem with building eCos--see output

[Gary Thomas]

On Tue, 2003-11-11 at 10:34, Gregg C Levine wrote:
> Hello (again) from Gregg C Levine
> Okay, it was the redboot_XXX.ecm file. Any clews?

Again, obtuse answers don't help, since there are 160 files named
like that in the repository.  I need to know exactly which .ecm
file you included.

[gthomas@hermes packages]$ find hal -name "*redboot*ecm" | wc
    160     160    7865

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] New problem with building eCos--see output

[Gregg C Levine]

Hello (again) from Gregg C Levine
I'm not being deliberately obtuse. I simply searched through the
packages directories, until I found the one named red boot, and went
to v2_0, and then to misc. That's where the file named redboot_XXX.ecm
is located, that I used. I vaguely remember being steered in that
direction by Andrew, with regards to this same problem, some months
earlier. And yes, I do know that there is a large quantity of such
package entries.
-------------------
Gregg C Levine hansolofalcon@worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



-----Original Message-----
From: Gary Thomas [mailto:gary@mlbassoc.com] 
Sent: Tuesday, November 11, 2003 12:38 PM
To: Gregg C Levine
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] New problem with building eCos--see output

On Tue, 2003-11-11 at 10:34, Gregg C Levine wrote:
> Hello (again) from Gregg C Levine
> Okay, it was the redboot_XXX.ecm file. Any clews?

Again, obtuse answers don't help, since there are 160 files named
like that in the repository.  I need to know exactly which .ecm
file you included.

[gthomas@hermes packages]$ find hal -name "*redboot*ecm" | wc
    160     160    7865

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] New problem with building eCos--see output

[Gary Thomas]

On Tue, 2003-11-11 at 11:00, Gregg C Levine wrote:
> Hello (again) from Gregg C Levine
> I'm not being deliberately obtuse. I simply searched through the
> packages directories, until I found the one named red boot, and went
> to v2_0, and then to misc. That's where the file named redboot_XXX.ecm
> is located, that I used. I vaguely remember being steered in that
> direction by Andrew, with regards to this same problem, some months
> earlier. And yes, I do know that there is a large quantity of such
> package entries.

I just tried looking for such a file, with no luck:
  [gthomas@hermes packages]$ find hal -name "*redboot*XXX*" 
  ... nothing listed
Since you don't remember, and since there seems to be no such file
in the repository, perhaps you should start over.

Please try to duplicate your problem, step by step.  Start with a
new configuration, then add/import/whatever one step at a time until
things break.  Then maybe we can figure out what's wrong.

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] New problem with building eCos--see output

[Roland Caßebohm]

On Dienstag, 11. November 2003 19:06, Gary Thomas wrote:
> On Tue, 2003-11-11 at 11:00, Gregg C Levine wrote:
> > Hello (again) from Gregg C Levine
> > I'm not being deliberately obtuse. I simply searched through the
> > packages directories, until I found the one named red boot, and went
> > to v2_0, and then to misc. That's where the file named redboot_XXX.ecm
> > is located, that I used. I vaguely remember being steered in that
> > direction by Andrew, with regards to this same problem, some months
> > earlier. And yes, I do know that there is a large quantity of such
> > package entries.
>
> I just tried looking for such a file, with no luck:
>   [gthomas@hermes packages]$ find hal -name "*redboot*XXX*"
>   ... nothing listed

I have found it: packages/redboot/current/misc/redboot_XXX.ecm

Better use: packages/hal/i386/pc/current/misc/redboot_FLOPPY.ecm

Best regards,
Roland
-- 

___________________________________________________

VS Vision Systems GmbH, Industrial Image Processing
Dipl.-Ing. Roland Caßebohm
Aspelohe 27A, D-22848 Norderstedt, Germany
http://www.visionsystems.de
___________________________________________________


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] New problem with building eCos--see output

[Gary Thomas]

On Wed, 2003-11-12 at 01:56, Roland Caßebohm wrote:
> On Dienstag, 11. November 2003 19:06, Gary Thomas wrote:
> > On Tue, 2003-11-11 at 11:00, Gregg C Levine wrote:
> > > Hello (again) from Gregg C Levine
> > > I'm not being deliberately obtuse. I simply searched through the
> > > packages directories, until I found the one named red boot, and went
> > > to v2_0, and then to misc. That's where the file named redboot_XXX.ecm
> > > is located, that I used. I vaguely remember being steered in that
> > > direction by Andrew, with regards to this same problem, some months
> > > earlier. And yes, I do know that there is a large quantity of such
> > > package entries.
> >
> > I just tried looking for such a file, with no luck:
> >   [gthomas@hermes packages]$ find hal -name "*redboot*XXX*"
> >   ... nothing listed
> 
> I have found it: packages/redboot/current/misc/redboot_XXX.ecm
> 
> Better use: packages/hal/i386/pc/current/misc/redboot_FLOPPY.ecm

This file is not suitable for configuring a particular RedBoot.  In
fact, I'm not even sure why it's in the repository.  (I think Jesper
did it as a short cut).

In general, to configure RedBoot for a particular environment, I do:
  % ecosconfig new <target> redboot
  % ecosconfig import <startup_type>.ecm
// Then, if I want/need FLASH support
  % ecosconfig add flash
// Similarly, if I want/need networking
  % ecosconfig add eth_drivers
  % ecosconfig tree

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] New problem with building eCos--see output

[Gregg C Levine]

Hello (from) Gregg C Levine
That did it. Thanks Roland. I owe you something, or other, the next
time your visiting this country.

That being said Gary, do you have a specific objection against that
ECM file? I seem to recall something being stated about it. And having
found it, it discusses using the command line tool. Any particular
reason? I prefer the gui one.
-------------------
Gregg C Levine hansolofalcon@worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



> -----Original Message-----
> From: Roland Caßebohm [mailto:roland.cassebohm@visionsystems.de]
> Sent: Wednesday, November 12, 2003 3:57 AM
> To: Gary Thomas; Gregg C Levine
> Cc: ecos-discuss@sources.redhat.com
> Subject: Re: [ECOS] New problem with building eCos--see output
> 
> On Dienstag, 11. November 2003 19:06, Gary Thomas wrote:
> > On Tue, 2003-11-11 at 11:00, Gregg C Levine wrote:
> > > Hello (again) from Gregg C Levine
> > > I'm not being deliberately obtuse. I simply searched through the
> > > packages directories, until I found the one named red boot, and
went
> > > to v2_0, and then to misc. That's where the file named
redboot_XXX.ecm
> > > is located, that I used. I vaguely remember being steered in
that
> > > direction by Andrew, with regards to this same problem, some
months
> > > earlier. And yes, I do know that there is a large quantity of
such
> > > package entries.
> >
> > I just tried looking for such a file, with no luck:
> >   [gthomas@hermes packages]$ find hal -name "*redboot*XXX*"
> >   ... nothing listed
> 
> I have found it: packages/redboot/current/misc/redboot_XXX.ecm
> 
> Better use: packages/hal/i386/pc/current/misc/redboot_FLOPPY.ecm
> 
> Best regards,
> Roland
> --
> 
> ___________________________________________________
> 
> VS Vision Systems GmbH, Industrial Image Processing
> Dipl.-Ing. Roland Caßebohm
> Aspelohe 27A, D-22848 Norderstedt, Germany
> http://www.visionsystems.de
> ___________________________________________________


--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] New problem with building eCos--see output

[Gary Thomas]

On Wed, 2003-11-12 at 13:21, Gregg C Levine wrote:
> Hello (from) Gregg C Levine
> That did it. Thanks Roland. I owe you something, or other, the next
> time your visiting this country.
> 
> That being said Gary, do you have a specific objection against that
> ECM file? I seem to recall something being stated about it. And having
> found it, it discusses using the command line tool. Any particular
> reason? I prefer the gui one.

First of all, you should only use a .ecm file which suits your needs.
If you are trying to build RedBoot for some PC based platform, then
only use one of the files in hal/i386/pc/...  The .ecm files are just
shorthand anyway, but you need to use them carefully.

I can see no reason to ever use the redboot_XXX.ecm file and I'm going
to remove it since I think it can only cause confusion (as it apparently
already has).

As for ecosconfig (command line) vs. ConfigTool (GUI) - this is one of
those "religious" questions - there is no *right* answer, only 
viewpoints.  I personally prefer the CLI version, but they are 100%
equivalent.  Use whichever one you wish.

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss