Error while compiling rtems main branch for sparc

[Gedare Bloom]

Hi Saurabh,

Please try to figure out how to fix the compile-error. You can see
that the problem occurs in the #ifdef'd STRICT_ORDER_MUTEX_CODE, so
that makes sense why others have not observed the same issue. It
appears you will have to reconcile the new _Thread_Change_priority
arguments with what is being used in that block of code. If you need
more guidance please ask.

Gedare

On Mon, Jun 1, 2015 at 12:35 AM, Saurabh Gadia <gadia at usc.edu> wrote:
> I wanted to test the ENABLE_STRICT_ORDER_MUTEX=1 related sptests for "nested
> mutex" GSOC project. So please let me know what can be done.
>
> Thanks,
>
> Saurabh Gadia
>
> On Sun, May 31, 2015 at 9:33 PM, Saurabh Gadia <gadia at usc.edu> wrote:
>>
>> Hi,
>> so I am working for sparc-sis setting and master branch. And if you see
>> the code in threadimpl.h and threadchangepriority.c and coremutexsurrender.c
>> the definition of _Thread_Change_priority() is having mismatch calling. Git
>> records says that there was change to above function structure done by
>> sebastian huber. But I guess he forgot to change the definition of
>> _Thread_Change_priority() in threadimpl.h and call in coremutexsurrender.c
>>
>> Configuration command:
>> ./configure --target=sparc-rtems4.11 --enable-rtemsbsp=sis --enable-tests
>> --disable-posix ENABLE_STRICT_ORDER_MUTEX=1
>>
>> Error Log:
>>
>>                                                                       ^
>> In file included from
>> ../../cpukit/../../../sis/lib/include/rtems/score/coremuteximpl.h:24:0,
>>                  from
>> ../../../../../../rtems/c/src/../../cpukit/score/src/coremutexsurrender.c:23:
>> ../../cpukit/../../../sis/lib/include/rtems/score/threadimpl.h:394:6:
>> note: expected 'void *' but argument is of type 'int'
>>  void _Thread_Change_priority(
>>       ^
>>
>> ../../../../../../rtems/c/src/../../cpukit/score/src/coremutexsurrender.c:60:7:
>> error: too few arguments to function '_Thread_Change_priority'
>>        _Thread_Change_priority( holder, mutex->queue.priority_before, true
>> );
>>        ^
>> In file included from
>> ../../cpukit/../../../sis/lib/include/rtems/score/coremuteximpl.h:24:0,
>>                  from
>> ../../../../../../rtems/c/src/../../cpukit/score/src/coremutexsurrender.c:23:
>> ../../cpukit/../../../sis/lib/include/rtems/score/threadimpl.h:394:6:
>> note: declared here
>>  void _Thread_Change_priority(
>>       ^
>> make[6]: *** [src/libscore_a-coremutexsurrender.o] Error 1
>>
>> Thanks,
>>
>> Saurabh Gadia
>>
>> On Sun, May 31, 2015 at 8:25 PM, Nick Withers <nick.withers at anu.edu.au>
>> wrote:
>>>
>>> Does re-running bootstrap in the source dir and re-configuring sort it?
>>> --
>>> Nick Withers
>>>
>>> Embedded Systems Programmer
>>> Department of Nuclear Physics, Research School of Physics and Engineering
>>> The Australian National University (CRICOS: 00120C)
>>>
>>> On Sun, 2015-05-31 at 20:31 -0400, Joel Sherrill wrote:
>>> > More information is needed. Target architecture, bsp, configure
>>> > command.
>>> >
>>> > I have been building all bsps regularly and unless it got broken this
>>> > weekend, something else is up
>>> >
>>> >
>>> > On May 31, 2015 7:57:04 PM EDT, Saurabh Gadia <gadia at usc.edu> wrote:
>>> > >The problem is on master branch
>>> > >
>>> > >
>>> > >Thanks,
>>> > >
>>> > >
>>> > >Saurabh Gadia
>>> > >
>>> > >
>>> > >On Sun, May 31, 2015 at 4:44 PM, Saurabh Gadia <gadia at usc.edu> wrote:
>>> > >
>>> > >Logs:
>>> > >
>>> > >make[6]: Entering directory
>>> > >`/home/saurabh/dev1/kernel/b-sis/sparc-rtems4.11/c/sis/cpukit/score'
>>> > >make[6]: *** No rule to make target `src/apimutexislocked.c', needed
>>> > > by
>>> > >`src/libscore_a-apimutexislocked.o'.  Stop.
>>> > >make[6]: Leaving directory
>>> > >`/home/saurabh/dev1/kernel/b-sis/sparc-rtems4.11/c/sis/cpukit/score'
>>> > >make[5]: *** [all-recursive] Error 1
>>> > >
>>> >
>>> > > >...............................................................................................................
>>> > >
>>> > >There is no makefile but I am also not able to find apimutexislocked.c
>>> > >
>>> > >How do I proceed about this.
>>> > >
>>> > >
>>> > >
>>> > >Thanks,
>>> > >
>>> > >
>>> > >Saurabh Gadia
>>> >
>>> > --joel
>>> > _______________________________________________
>>> > devel mailing list
>>> > devel at rtems.org
>>> > http://lists.rtems.org/mailman/listinfo/devel
>>>
>>>
>>
>
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel