<div dir="ltr"><div><h3 class="gmail-iw">
</h3><h3 class="gmail-western" style="font-weight:normal">Hi Cyril Hrubis,</h3>
</div><div>Thanks for your prompt reply.<br></div><div> <br>I have some doubt please clarify <br></div>I am getting following errors while building LTP with YOCTO(2.3)<br><div>{{{<br><p style="margin-bottom:0in;line-height:100%"> ltp-20170116-r0
do_compile: NOTE: ltp: compiling from external source tree
/home/sathishc/kapil/build/https:/<a href="http://github.com/linux-test-project/ltp.git">github.com/linux-test-project/ltp.git</a><br>
ERROR:
ltp-20170116-r0 do_compile: oe_runmake failed<br>
ERROR:
ltp-20170116-r0 do_compile: Function failed: do_compile (log file is
located at
/home/sathishc/kapil/build/tmp/work/cortexa9hf-neon-agl-linux-gnueabi/ltp/20170116- r0/temp<br> /log.do_compile.161006)<br> ERROR:
Logfile of failure stored in:
/home/sathishc/kapil/build/tmp/work/cortexa9hf-neon-agl- linux-gnueabi/ltp/20170116-r0/temp/log.do_compile.161006<br>
Log
data follows:<br>
| DEBUG: Executing python function
externalsrc_compile_prefunc<br>
| NOTE: ltp: compiling from
external source tree
/home/sathishc/kapil/build/https:/<a href="http://github.com/linux-test-project/ltp.git">github.com/linux-test-project/ltp.git</a><br>
|
DEBUG: Python function externalsrc_compile_prefunc finished<br>
|
DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32',
'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi',
'common']<br>
| DEBUG: Executing shell function do_compile<br>
|
NOTE: make -j 16<br>
| ERROR: oe_runmake failed<br> | make:
Entering directory
'/home/sathishc/kapil/build/https:/<a href="http://github.com/linux-test-">github.com/linux-test-</a> project/ltp.git/testcases/kernel'<br>
|
make: 'include/linux_syscall_numbers.h' is up to date.<br> | make:
Leaving directory
'/home/sathishc/kapil/build/https:/<a href="http://github.com/linux-test-">github.com/linux-test-</a> project/ltp.git/testcases/kernel'<br> |
/home/sathishc/kapil/build/https:/<a href="http://github.com/linux-test-">github.com/linux-test-</a> project/ltp.git/include/mk/<a href="http://automake.mk:108">automake.mk:108</a>:
*** target pattern contains no '%'. Stop.<br>
| ERROR:
Function failed: do_compile (log file is located at
/home/sathishc/kapil/build/tmp/work/cortexa9hf-neon-agl-linux-gnueabi/ltp/20170116- r0/temp/log.do_compile.161006)</p>
<br>}}}<br></div><div>Note : <br> $ bitbake --version<br> BitBake Build Tool Core version 1.34.0<br></div><div>Regards,<br></div>Abhishek</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 27, 2018 at 7:41 PM, Cyril Hrubis <span dir="ltr"><<a href="mailto:chrubis@suse.cz" target="_blank">chrubis@suse.cz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi!<br>
<span class="">> I am planning to use the LTP latest version on YOCTO latest vesion.<br>
> It seems that the earlier YOCTO versions are released with LTP and<br>
> latest version are not.<br>
> Found the below difficulties so far:<br>
> 1. Latest LTP version(20180118) suitable for old gcc version(4.8).<br>
> 2. But at the same time, latest version of YOCTO build(2.3) supporting<br>
> latest<br>
> gcc version(6.3) only.<br>
> <br>
> so we want to use a latest LTP version(20180118) with latest YOCTO<br>
> build(2.3) which has latest gcc version(6.3) .<br>
> <br>
> Please share your valuable inputs with me to achieve the same.<br>
<br>
</span>LTP should not depend on gcc version at all, it should compile fine with<br>
anything new enough. We do test the build with travis for each commit<br>
againts various gcc versions starting at 4.9 to gcc 7 and also with<br>
several clang versions.<br>
<span class="HOEnZb"><font color="#888888"><br>
-- <br>
Cyril Hrubis<br>
<a href="mailto:chrubis@suse.cz">chrubis@suse.cz</a><br>
</font></span></blockquote></div><br></div>
<br>
<table cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td valign="middle">
<p><span>The information contained in this e-mail message (including any </span></p>
<p><span>attachments) may be confidential, proprietary, privileged, or otherwise</span></p>
<p><span>exempt from disclosure under applicable laws. It is intended to be </span></p>
<p><span>conveyed only to the designated recipient(s). Any use, dissemination, </span></p>
<p><span>distribution, printing, retaining or copying of this e-mail (including its </span></p>
<p><span>attachments) by unintended recipient(s) is strictly prohibited and may </span></p>
<p><span>be unlawful. If you are not an intended recipient of this e-mail, or believe </span></p>
<p><span>that you have received this e-mail in error, please notify the sender </span></p>
<p><span>immediately (by replying to this e-mail), delete any and all copies of </span></p>
<p><span>this e-mail (including any attachments) from your system, and do not</span></p>
<p><span>disclose the content of this e-mail to any other person. Thank you for your cooperation.</span></p>
</td>
</tr>
</tbody>
</table>
<br>
<img><i style="font-family:Calibri;font-size:14px"><span style="font-size:10pt">This e-mail message (including any </span>attachments) may be confidential, proprietary, privileged, or otherwise exempt from disclosure under applicable laws. If you are not an intended recipient, please delete this message. Thank you.</i><br style="font-family:Calibri;font-size:14px">