4.11 BLOCKER - Multiple BSPs fail to build - cache changes?

[Gedare Bloom]

Wouldn't it be better to fix the or1k function declarations unless
there is going to be or1k-specific implementation provided?

On Fri, Apr 24, 2015 at 1:07 PM, Hesham ALMatary
<heshamelmatary at gmail.com> wrote:
> Hi,
>
> I believe this commit is the one which broke it [1], I'm going to
> discard the usage of the shared cache_manager.c file and provide or1k
> with private stubs.
>
> [1] https://github.com/RTEMS/rtems/commit/26c142e5ad4a63ad42baa17159c1821afe473a00
>
> On Fri, Apr 24, 2015 at 5:16 PM, Joel Sherrill
> <joel.sherrill at oarcorp.com> wrote:
>> Hi
>>
>> Multiple BSPs failed to build in my overnight sweep.  All
>> bfin and or1k BSPs plus 18 m68k failed with this:
>>
>> ../../../../../../../rtems/c/src/lib/libcpu/m68k/../shared/src/cache_manager.c:340:1:
>> error: static declaration of '_CPU_cache_invalidate_instruction_range'
>> follows non-static declaration
>>  _CPU_cache_invalidate_instruction_range(
>>  ^
>> In file included from
>> ../../../../../../../rtems/c/src/lib/libcpu/m68k/shared/cache/cache_.h:37:0,
>>                  from
>> ../../../../../../../rtems/c/src/lib/libcpu/m68k/../shared/src/cache_manager.c:39:
>> ../../../../.././mcf5329/lib/include/libcpu/cache.h:30:6: note: previous
>> declaration of '_CPU_cache_invalidate_instruction_range' was here
>>  void _CPU_cache_invalidate_instruction_range(const void *i_addr, size_t
>> n_bytes);
>>       ^
>>
>> bfin/bf537Stamp, or1k/or1k_generic, and m68k/mvme136 should
>> be sufficient to reproduce and fix the problem.
>>
>> --
>> Joel Sherrill, Ph.D.             Director of Research & Development
>> joel.sherrill at OARcorp.com        On-Line Applications Research
>> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>> Support Available                (256) 722-9985
>>
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>
>
>
> --
> Hesham
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel