[rtems-bsp-builder] 2018-04-24 18:06:05: Profile(s): everything

Chris Johns chrisj at rtems.org
Thu Apr 26 01:07:21 UTC 2018

On 25/04/2018 17:57, Sebastian Huber wrote:
> On 25/04/18 09:07, joel at rtems.org wrote:
>> Failures Report
>> ===============
>>     1 debug epiphany/epiphany_sim build:
>>        configure: /home/joel/rtems-work/rtems/configure --target=epiphany-\
>>        rtems5 --enable-rtemsbsp=epiphany_sim --prefix=/home/joel/rtems-\
>>        work/bsps --enable-debug
>>       error: cpukit/mghttpd/mongoose.c:674:1: internal compiler error: in
>>              epiphany_expand_prologue, at config/epiphany/epiphany.c:1830
> Ok, the clue is that this is built with networking enabled. This is not visible
> here under "configure: ...".

Are the default states considered a valid configuration or should the BSP
builder always list the options it controls? The list is:


and adding the `no-*` variant should resolve this.

> This ICE is a known problem. I always build with
> networking disabled on this platform.

How do we manage this?

1. Leave networking available as a configuration for this BSP and allow the
error? I do not like this, it is sloppy.

2. Have configure raise an error on this arch if networking is enabled?

3. Remove the option and always enable? Can this work with libbsd now the
headers have moved?

4. Remove the networking stack to a separate repo and move in the examples-v2 tests?

5. Something else?


More information about the build mailing list