Building RTEMS for BeagleBone Black failed

[Russell Haley]

Hi,

I'm getting the same redefine error as my other attempts on FreeBSD.
https://pastebin.com/xfCPmaBm

I went back to the drawing board and started from the top in the
documentation using the SPARC build. The following is what I have done
so far. The base path is ~/Git (/usr/home/russellh/Git)

mkdir -p rtems/4.12 && cd rtems/4.12

git clone git://git.rtems.org/rtems-source-builder.git rsb
cd rsb
./source-builder/sb-check #check OK
cd rtems
../source-builder/sb-set-builder
--prefix=/usr/home/russellh/Git/rtems/4.12 4.12/rtems-sparc

Interestingly the re-defined values are different...

I'm heading out for a bit but will create a ticket when I get back if
so desired. I will try this on Debian later too.

Russ

On Tue, Jul 18, 2017 at 8:07 AM, Russell Haley <russ.haley at gmail.com> wrote:
> On Mon, Jul 17, 2017 at 11:39 PM, Chris Johns <chrisj at rtems.org> wrote:
>> On 18/07/2017 01:33, Russell Haley wrote:
>>> Hi, I seem to get the same error. I made the assumption that the bset
>>> for the beagle board name has changed from devel/beagle.bset to
>>> rtems-arm.bset based on the seb config directory.
>>
>> I think the beagle.bset was a special made by Ben and it was never accepted into
>> the master repo. I cannot remember what the build set contains.
>>
>> A board build set would need to reside under 'boards/beagle.bset' and while I
>> see some value in these it increases the amount of testing we need to do when
>> making changes, releasing and testing. I would be more included to accept a
>> board build set patch if there was an active maintain for each one.
>
> Okay, I remember this conversation now. I would be happy to try and
> extend Ben's work towards getting a bset in the repo, but perhaps I
> should build rtems at least once before volunteering for something.
> tee hee. I have six more days off of work (with no kids!) so I am
> trying to cram as much of this into one week as possible.
>
> Either way, the redefinition error I am getting seems to be long
> before we get to board specific configuration. It's happening in the
> compilation of /gcc-6.3.0/gcc/gencheck.c (the file in question is
> ./options.h). My C is not strong enough to take it much further.
>
> So I see the following options for me (input appreciated):
> - Try a different platform. I have a Debian Jessie image I can build on.
> - Try a different board package on FreeBSD. I will perhaps concede
> defeat and build the emulator instead.
>
> Some things I am having trouble keeping straight in my head:
> 1)Given a project setup of:
>  ~/Git/
> ->rtems/
> -->rtems-source-builder/
> -->src/
> -->b-bbb/
> -->b-erc32/
>
> Can I expect to be able to build for more than one target and have the
> output wind up in the b-bbb or b-erc32 directories? All input on my
> project layout is welcome.
>
> 2) What is the function of the --prefix? Is that supposed to point to
> my overall install path, the source path, or my output path? So given
> the previous paths, my --prefix would be ${HOME}/Git/rtems?
>
> Thanks,
>
> Russ