BSP requests.

[Alan Cudmore]

Chris,
It looks like _libelf_config.h has the defines for an ARM host on FreeBSD,
but for linux it includes "native-elf-format.h". It looks like this file is
produced with the native-elf-format binary, which produces this output:
pi at raspberrypi ~/rtems-tools.git/rtemstoolkit/elftoolchain/common $
./native-elf-format
/* Generated by native-elf-format on Tue Feb 10 03:33:38 UTC 2015 */
#define ELFTC_CLASS ELFCLASS32
#define ELFTC_ARCH unknown
#define ELFTC_BYTEORDER ELFDATA2LSB
pi at raspberrypi ~/rtems-tools.git/rtemstoolkit/elftoolchain/common $


So the #define ELFTC_ARCH unknown statement causes the compile error.

I can dig into this later, it's not a big deal, I just want to make my RPI
2 serve as a development host for my RPI 1 :)

As for the Linux on RPI 2, I think they are using the same Raspbian distro,
so this probably happens on the RPI 1 as well.

Thanks,
Alan


On Mon, Feb 9, 2015 at 10:24 PM, Chris Johns <chrisj at rtems.org> wrote:

> On 10/02/2015 2:16 pm, Alan Cudmore wrote:
>
>> Thanks for getting the BSPs in.
>>
>> I wanted to try to compare the old and new build systems on the
>> raspberry Pi 2, but I'm still working on getting the tools to build.
>> Chris may have a clue about this:
>> The compiler build finishes ( much faster than the RPI 1 ) but the rtems
>> tools build fails. This can be reproduced with just the rtems tools repo
>> without trying a complete RSB toolchain build.
>> I suspect that something is not getting defined for the ARM host in the
>> configure step:
>> pi at raspberrypi ~/rtems-tools.git $ ./waf build
>> Waf: Entering directory `/home/pi/rtems-tools.git/build'
>> [  1/142] libelf_convert.c:
>> rtemstoolkit/elftoolchain/libelf/libelf_convert.m4 ->
>> build/rtemstoolkit/libelf_convert.c
>> [  3/142] libelf_fsize.c:
>> rtemstoolkit/elftoolchain/libelf/libelf_fsize.m4 ->
>> build/rtemstoolkit/libelf_fsize.c
>> [  3/142] libelf_msize.c:
>> rtemstoolkit/elftoolchain/libelf/libelf_msize.m4 ->
>> build/rtemstoolkit/libelf_msize.c
>> [  4/142] native-elf-format:
>> rtemstoolkit/elftoolchain/common/native-elf-format ->
>> build/rtemstoolkit/elftoolchain/common/native-elf-format.h
>> [  5/142] c: rtemstoolkit/elftoolchain/libelf/elf.c ->
>> build/rtemstoolkit/elftoolchain/libelf/elf.c.5.o
>> [  6/142] c: rtemstoolkit/elftoolchain/libelf/elf_begin.c ->
>> build/rtemstoolkit/elftoolchain/libelf/elf_begin.c.5.o
>> [  7/142] c: rtemstoolkit/elftoolchain/libelf/elf_cntl.c ->
>> build/rtemstoolkit/elftoolchain/libelf/elf_cntl.c.5.o
>> [  8/142] c: rtemstoolkit/elftoolchain/libelf/elf_end.c ->
>> build/rtemstoolkit/elftoolchain/libelf/elf_end.c.5.o
>> ../rtemstoolkit/elftoolchain/libelf/elf.c:34:18: error: ‘unknown’
>> undeclared here (not in a function)
>>
>
> This looks to me like the elftoolchain we have does not know how to handle
> the ARM you are on. Have a look at _libelf_config.h.
>
> Are you able to have a look at this for me ?
>
> I do not have a Rpi2 yet.
>
> Thanks
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20150209/bf7998c3/attachment-0002.html>