devel Digest, Vol 90, Issue 37 --> RTEMS 5.0 error occurred in 'make' while --enable- tests
Joel Sherrill
joel at rtems.org
Tue May 7 15:27:21 UTC 2019
Based on the contents of bsps/arm/tms570/config, the valid BSP variants are:
tms570ls3137_hdk
tms570ls3137_hdk_intram
tms570ls3137_hdk_intram-testsuite
tms570ls3137_hdk_sdram
tms570ls3137_hdk-testsuite
tms570ls3137_hdk_with_loader
tms570ls3137_hdk_with_loader-testsuite
Your configure didn't include _hdk on the BSP name.
On Tue, May 7, 2019 at 9:18 AM Aby Tom <abythayil at gmail.com> wrote:
> Dear Joel,
> thanks for the quick response.
>
> my command was:
>
> $HOME/dev/kernel/rtems/configure --prefix=$HOME/dev/rtems/5
> --target=arm-rtems5 --enable-rtemsbsp=tms570lc4357 --enable-maintainer-mode
> --enable-tests
>
> Thanks and Regards,
> Aby
> On Tue, May 7, 2019, 3:59 PM <devel-request at rtems.org> wrote:
>
>> Send devel mailing list submissions to
>> devel at rtems.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://lists.rtems.org/mailman/listinfo/devel
>> or, via email, send a message with subject or body 'help' to
>> devel-request at rtems.org
>>
>> You can reach the person managing the list at
>> devel-owner at rtems.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of devel digest..."
>>
>>
>> Today's Topics:
>>
>> 1. RTEMS 5.0 error occurred in 'make' while --enable- tests are
>> done (Aby Tom)
>> 2. Re: RTEMS 5.0 error occurred in 'make' while --enable- tests
>> are done (Joel Sherrill)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Tue, 7 May 2019 15:44:38 +0200
>> From: Aby Tom <abythayil at gmail.com>
>> To: devel at rtems.org
>> Subject: RTEMS 5.0 error occurred in 'make' while --enable- tests are
>> done
>> Message-ID:
>> <CADH5PD1CL8A2CRQruERf2rp1iPJyBHk-NHuYCWT8D8qUoR=
>> TOQ at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hello everyone,
>>
>> I am new to RTEMS, and was trying to build a new bsp for RTEMS 5 for
>> tms570
>> family of boards.
>>
>> While doing the make, i come across this error.
>>
>> I had done --enable-tests in the previous command.
>>
>> Can anyone help me with this? Output from terminal is shown below.
>>
>> (.... represent some omitted output results)
>>
>> .....
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/nfs.c:
>> In
>> function 'nfs_fsunmount_me':
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/nfs.c:1928:7:
>> warning: variable 'status' set but not used [-Wunused-but-set-variable]
>> int status;
>> .....
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:
>> In function 'rpcUdpServerCreate':
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:567:11:
>> error: 'llock' undeclared (first use in this function); did you mean
>> 'clock'?
>> MU_LOCK( llock );
>>
>> .....
>>
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:204:54:
>> note: in definition of macro 'MU_LOCK'
>> #define MU_LOCK(mutex) rtems_recursive_mutex_lock(&(mutex))
>>
>>
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:567:11:
>> note: each undeclared identifier is reported only once for each function
>> it
>> appears in
>> MU_LOCK( llock );
>>
>> .....
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:
>> In function 'rpcUdpXactCreate':
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:667:11:
>> error: 'hlock' undeclared (first use in this function); did you mean
>> 'clock'?
>> MU_LOCK(hlock);
>> ^
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:204:54:
>> note: in definition of macro 'MU_LOCK'
>> #define MU_LOCK(mutex) rtems_recursive_mutex_lock(&(mutex))
>> ^~~~~
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:
>> In function 'rpcUdpXactDestroy':
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:711:11:
>> error: 'hlock' undeclared (first use in this function); did you mean
>> 'clock'?
>> MU_LOCK(hlock);
>> ^
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:204:54:
>> note: in definition of macro 'MU_LOCK'
>> #define MU_LOCK(mutex) rtems_recursive_mutex_lock(&(mutex))
>> ^~~~~
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:
>> In function 'rpcUdpRcv':
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:813:19:
>> warning: variable 'status' set but not used [-Wunused-but-set-variable]
>> rtems_status_code status;
>> ^~~~~~
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:
>> In function 'rpcUdpInit':
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:938:15:
>> error: 'hlock' undeclared (first use in this function); did you mean
>> 'clock'?
>> MU_CREAT( &hlock );
>> ^
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:208:54:
>> note: in definition of macro 'MU_CREAT'
>> #define MU_CREAT(pmutex) rtems_recursive_mutex_init((pmutex), "RPCl")
>> ^~~~~~
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:939:15:
>> error: 'llock' undeclared (first use in this function); did you mean
>> 'hlock'?
>> MU_CREAT( &llock );
>> ^
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:208:54:
>> note: in definition of macro 'MU_CREAT'
>> #define MU_CREAT(pmutex) rtems_recursive_mutex_init((pmutex), "RPCl")
>> ^~~~~~
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:924:19:
>> warning: variable 'wkup' set but not used [-Wunused-but-set-variable]
>> struct sockwakeup wkup;
>> ^~~~
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:922:19:
>> warning: variable 'status' set but not used [-Wunused-but-set-variable]
>> rtems_status_code status;
>> ^~~~~~
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:921:7:
>> warning: variable 's' set but not used [-Wunused-but-set-variable]
>> int s;
>> ^
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:
>> In function 'rpcio_daemon':
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:1173:12:
>> error: 'hlock' undeclared (first use in this function); did you mean
>> 'clock'?
>> MU_LOCK(hlock);
>> ^
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:204:54:
>> note: in definition of macro 'MU_LOCK'
>> #define MU_LOCK(mutex) rtems_recursive_mutex_lock(&(mutex))
>> ^~~~~
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:1149:19:
>> warning: variable 'status' set but not used [-Wunused-but-set-variable]
>> rtems_status_code status;
>> ^~~~~~
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:
>> In function 'rpcUdpXactPoolCreate':
>>
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:1508:19:
>> warning: variable 'status' set but not used [-Wunused-but-set-variable]
>> rtems_status_code status;
>> ^~~~~~
>> Makefile:11245: recipe for target 'libfs/src/nfsclient/src/rpcio.o' failed
>> make[4]: *** [libfs/src/nfsclient/src/rpcio.o] Error 1
>> make[4]: Leaving directory
>> Makefile:1221: recipe for target 'cpukit' failed
>> make[3]: *** [cpukit] Error 2
>> make[3]: Leaving directory
>> Makefile:715: recipe for target 'all-recursive' failed
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory
>> Makefile:289: recipe for target 'all-recursive' failed
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory
>> Makefile:410: recipe for target 'all-recursive' failed
>> make: *** [all-recursive] Error 1
>>
>>
>> Thank you.
>> Regards,
>> Aby
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://lists.rtems.org/pipermail/devel/attachments/20190507/0933795b/attachment-0001.html
>> >
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Tue, 7 May 2019 08:58:44 -0500
>> From: Joel Sherrill <joel at rtems.org>
>> To: Aby Tom <abythayil at gmail.com>
>> Cc: "rtems-devel at rtems.org" <devel at rtems.org>
>> Subject: Re: RTEMS 5.0 error occurred in 'make' while --enable- tests
>> are done
>> Message-ID:
>> <CAF9ehCUPi0yKAO=
>> KFGWMAFX6cHB02cHjep3ukfkV36qzNcZOrQ at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> This BSP builds for me off the master. There are multiple variants within
>> this
>> BSP family and various configurations you could have used. Could you
>> share your configure command?
>>
>> Mine was:
>>
>> ../rtems/configure --target=arm-rtems5
>> --enable-rtemsbsp=tms570ls3137_hdk_sdram
>> --prefix=/home/joel/rtems-work/tools/5/bsp-install --enable-networking
>> --enable-posix --disable-smp --disable-multiprocessing
>> --disable-rtems-debug --disable-profiling --enable-tests --enable-cxx
>> --enable-maintainer-mode
>>
>>
>> Thanks.
>>
>> --joel
>>
>> On Tue, May 7, 2019 at 8:44 AM Aby Tom <abythayil at gmail.com> wrote:
>>
>> > Hello everyone,
>> >
>> > I am new to RTEMS, and was trying to build a new bsp for RTEMS 5 for
>> > tms570 family of boards.
>> >
>> > While doing the make, i come across this error.
>> >
>> > I had done --enable-tests in the previous command.
>> >
>> > Can anyone help me with this? Output from terminal is shown below.
>> >
>> > (.... represent some omitted output results)
>> >
>> > .....
>> >
>> > /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/nfs.c:
>> > In function 'nfs_fsunmount_me':
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/nfs.c:1928:7:
>> > warning: variable 'status' set but not used [-Wunused-but-set-variable]
>> > int status;
>> > .....
>> >
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:
>> > In function 'rpcUdpServerCreate':
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:567:11:
>> > error: 'llock' undeclared (first use in this function); did you mean
>> > 'clock'?
>> > MU_LOCK( llock );
>> >
>> > .....
>> >
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:204:54:
>> > note: in definition of macro 'MU_LOCK'
>> > #define MU_LOCK(mutex) rtems_recursive_mutex_lock(&(mutex))
>> >
>> >
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:567:11:
>> > note: each undeclared identifier is reported only once for each
>> function it
>> > appears in
>> > MU_LOCK( llock );
>> >
>> > .....
>> >
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:
>> > In function 'rpcUdpXactCreate':
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:667:11:
>> > error: 'hlock' undeclared (first use in this function); did you mean
>> > 'clock'?
>> > MU_LOCK(hlock);
>> > ^
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:204:54:
>> > note: in definition of macro 'MU_LOCK'
>> > #define MU_LOCK(mutex) rtems_recursive_mutex_lock(&(mutex))
>> > ^~~~~
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:
>> > In function 'rpcUdpXactDestroy':
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:711:11:
>> > error: 'hlock' undeclared (first use in this function); did you mean
>> > 'clock'?
>> > MU_LOCK(hlock);
>> > ^
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:204:54:
>> > note: in definition of macro 'MU_LOCK'
>> > #define MU_LOCK(mutex) rtems_recursive_mutex_lock(&(mutex))
>> > ^~~~~
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:
>> > In function 'rpcUdpRcv':
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:813:19:
>> > warning: variable 'status' set but not used [-Wunused-but-set-variable]
>> > rtems_status_code status;
>> > ^~~~~~
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:
>> > In function 'rpcUdpInit':
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:938:15:
>> > error: 'hlock' undeclared (first use in this function); did you mean
>> > 'clock'?
>> > MU_CREAT( &hlock );
>> > ^
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:208:54:
>> > note: in definition of macro 'MU_CREAT'
>> > #define MU_CREAT(pmutex) rtems_recursive_mutex_init((pmutex), "RPCl")
>> > ^~~~~~
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:939:15:
>> > error: 'llock' undeclared (first use in this function); did you mean
>> > 'hlock'?
>> > MU_CREAT( &llock );
>> > ^
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:208:54:
>> > note: in definition of macro 'MU_CREAT'
>> > #define MU_CREAT(pmutex) rtems_recursive_mutex_init((pmutex), "RPCl")
>> > ^~~~~~
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:924:19:
>> > warning: variable 'wkup' set but not used [-Wunused-but-set-variable]
>> > struct sockwakeup wkup;
>> > ^~~~
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:922:19:
>> > warning: variable 'status' set but not used [-Wunused-but-set-variable]
>> > rtems_status_code status;
>> > ^~~~~~
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:921:7:
>> > warning: variable 's' set but not used [-Wunused-but-set-variable]
>> > int s;
>> > ^
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:
>> > In function 'rpcio_daemon':
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:1173:12:
>> > error: 'hlock' undeclared (first use in this function); did you mean
>> > 'clock'?
>> > MU_LOCK(hlock);
>> > ^
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:204:54:
>> > note: in definition of macro 'MU_LOCK'
>> > #define MU_LOCK(mutex) rtems_recursive_mutex_lock(&(mutex))
>> > ^~~~~
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:1149:19:
>> > warning: variable 'status' set but not used [-Wunused-but-set-variable]
>> > rtems_status_code status;
>> > ^~~~~~
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:
>> > In function 'rpcUdpXactPoolCreate':
>> >
>> /home/dev/kernel/rtems/c/src/../../cpukit/libfs/src/nfsclient/src/rpcio.c:1508:19:
>> > warning: variable 'status' set but not used [-Wunused-but-set-variable]
>> > rtems_status_code status;
>> > ^~~~~~
>> > Makefile:11245: recipe for target 'libfs/src/nfsclient/src/rpcio.o'
>> failed
>> > make[4]: *** [libfs/src/nfsclient/src/rpcio.o] Error 1
>> > make[4]: Leaving directory
>> > Makefile:1221: recipe for target 'cpukit' failed
>> > make[3]: *** [cpukit] Error 2
>> > make[3]: Leaving directory
>> > Makefile:715: recipe for target 'all-recursive' failed
>> > make[2]: *** [all-recursive] Error 1
>> > make[2]: Leaving directory
>> > Makefile:289: recipe for target 'all-recursive' failed
>> > make[1]: *** [all-recursive] Error 1
>> > make[1]: Leaving directory
>> > Makefile:410: recipe for target 'all-recursive' failed
>> > make: *** [all-recursive] Error 1
>> >
>> >
>> > Thank you.
>> > Regards,
>> > Aby
>> > _______________________________________________
>> > devel mailing list
>> > devel at rtems.org
>> > http://lists.rtems.org/mailman/listinfo/devel
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://lists.rtems.org/pipermail/devel/attachments/20190507/15d73ec9/attachment.html
>> >
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>>
>> ------------------------------
>>
>> End of devel Digest, Vol 90, Issue 37
>> *************************************
>>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190507/2b869a9d/attachment-0001.html>
More information about the devel
mailing list