<font size=2 face="sans-serif">Thanks, Nick - the patch from Patrick (attached
to that ticket) worked for me as well.</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Nick Withers"
<nick.withers@anu.edu.au></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif"><Athanasios.Tsiodras@esa.int>,
<users@rtems.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">27/01/2016 11:54</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: RTEMS build
failure for 4.11/rtems-sparc</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Hi there Athanasios!<br>
<br>
On Wed, 2016-01-27 at 11:48 +0100, Athanasios.Tsiodras@esa.int wrote:<br>
> Hello RTEMS wizards.<br>
> <br>
> I am trying to setup a nightly build process for 4.11/rtems-sparc<br>
> (which <br>
> is the target of interest for my section of the European Space<br>
> Agency). I <br>
> managed to get a firewall exception from our tech department so I
can<br>
> (finally) checkout directly from git.rtems.org.<br>
> <br>
> The following sequence of commands, however, showcases a failed<br>
> attempt to <br>
> build 4.11/rtems-sparc :<br>
> <br>
> $ git clone git://git.rtems.org/rtems-source-builder.git<br>
> $ cd rtems-source-builder<br>
> $ git checkout 4.11<br>
> $ sudo apt-get build-dep binutils gcc g++ gdb unzip
git python2.7<br>
> -dev<br>
> ...<br>
> $ ./source-builder/sb-check<br>
> RTEMS Source Builder - Check, 4.11 (436ec884a86c)<br>
> Environment is ok<br>
> <br>
> $ cd rtems<br>
> $ ../source-builder/sb-set-builder --log=l-sparc.txt
<br>
> --prefix=$HOME/development/rtems/4.11 4.11/rtems-sparc<br>
> ...<br>
> config: tools/rtems-gdb-7.9-1.cfg<br>
> package: sparc-rtems4.11-gdb-7.9-i686-linux-gnu-1<br>
> building: sparc-rtems4.11-gdb-7.9-i686-linux-gnu-1<br>
> reporting: tools/rtems-gdb-7.9-1.cfg -> <br>
> sparc-rtems4.11-gdb-7.9-i686-linux-gnu-1.txt<br>
> reporting: tools/rtems-gdb-7.9-1.cfg -> <br>
> sparc-rtems4.11-gdb-7.9-i686-linux-gnu-1.xml<br>
> config: tools/rtems-tools-4.11-1.cfg<br>
> package: rtems-tools-4.11-1<br>
> git: reset: git://git.rtems.org/rtems-tools.git<br>
> git: checkout: git://git.rtems.org/rtems-tools.git =>
4.11<br>
> git: pull: git://git.rtems.org/rtems-tools.git<br>
> building: rtems-tools-4.11-1<br>
> error: building rtems-tools-4.11-1<br>
> Build FAILED<br>
> <br>
> Right after building GDB (successfully - I can see the sparc<br>
> -rtems4.11-gdb <br>
> binary in the "temp" build folder) RSB tries to build rtems-tools<br>
> -4.11, <br>
> via an auto-generated "doit" script. After checking out
from <br>
> git://git.rtems.org/rtems-tools.git the script tries to "cd
<br>
> rtems-tools-4.11" but in fact the only thing that exists in that<br>
> folder <br>
> after checking out from rtems-tools.git is:<br>
> <br>
> thanassis@taste <br>
> ~/development/rtems/src/rtems-source-builder/rtems/build/rtems-tools<br>
> -4.11-1<br>
> $ ls -l<br>
> total 20<br>
> drwxr-xr-x 2 thanassis thanassis 4096 Jan 27 10:46 ./<br>
> drwxr-xr-x 8 thanassis thanassis 4096 Jan 27 10:35 ../<br>
> -rwxr-xr-x 1 thanassis thanassis 5313 Jan 27 10:45 doit*<br>
> lrwxrwxrwx 1 thanassis thanassis 92 Jan 27 10:35 rtems-tools.git
-><br>
> /home/thanassis/development/rtems/src/rtems-source<br>
> -builder/rtems/sources/git/rtems-tools.git/<br>
> <br>
> ...so the process fails.<br>
> <br>
> I verified that this is indeed the issue by patching "doit"
to<br>
> introduce a <br>
> second symlink:<br>
> <br>
> $ diff -u doit doit.new<br>
> --- doit 2016-01-27 11:24:40.738260198
+0100<br>
> +++ doit.new 2016-01-27 11:34:12.614248399
+0100<br>
> @@ -82,6 +82,7 @@<br>
> cd <br>
> /home/thanassis/development/rtems/src/rtems-source<br>
> -builder/rtems/build/rtems-tools-4.11-1<br>
> /bin/rm -rf ${rtems_tools_source}<br>
> ln -s <br>
> /home/thanassis/development/rtems/src/rtems-source<br>
> -builder/rtems/sources/git/rtems-tools.git <br>
> ${source_dir_rtems_tools}<br>
> +ln -s <br>
> /home/thanassis/development/rtems/src/rtems-source<br>
> -builder/rtems/sources/git/rtems-tools.git <br>
> rtems-tools-4.11<br>
> cd ${rtems_tools_source}<br>
> /bin/chmod -R a+rX,g-w,o-w .<br>
> <br>
> After this change, "doit" completes successfully:<br>
> <br>
> thanassis@taste <br>
> ~/development/rtems/src/rtems-source-builder/rtems/build/rtems-tools<br>
> -4.11-1<br>
> $ ./doit.new<br>
> => rtems-tools-4.11-1:<br>
> ==> %prep:<br>
> ==> clean %{buildroot}: <br>
> /home/thanassis/development/rtems/src/rtems-source<br>
> -builder/rtems/build/tmp/rtems-tools-4.11-1-root-thanassis<br>
> ==> %build:<br>
> Setting top to
: <br>
> /home/thanassis/development/rtems/src/rtems-source<br>
> -builder/rtems/sources/git/rtems-tools.git<br>
> Setting out to
: <br>
> /home/thanassis/development/rtems/src/rtems-source<br>
> -builder/rtems/sources/git/rtems-tools.git/build<br>
> Version
:<br>
> 4.11.3175451a890e_modified <br>
> (4.11)<br>
> Checking for 'gcc' (C compiler)
: /usr/bin/gcc<br>
> Checking for 'g++' (C++ compiler)
: /usr/bin/g++<br>
> Checking for header alloca.h
: yes<br>
> Checking for header fcntl.h
: yes<br>
> Checking for header process.h
: not found<br>
> ...<br>
> + install <br>
> /home/thanassis/development/rtems/src/rtems-source<br>
> -builder/rtems/build/tmp/rtems-tools-4.11-1-root<br>
> -thanassis/home/thanassis/development/rtems/4.11/share/rtems/tester/r<br>
> tems/version.cfg <br>
> (from tester/rtems/version.cfg)<br>
> Waf: Leaving directory <br>
> `/home/thanassis/development/rtems/src/rtems-source<br>
> -builder/rtems/sources/git/rtems-tools.git/build'<br>
> 'install' finished successfully (0.779s)<br>
> ==> %clean:<br>
> <br>
> Here's the final form of the build folder afterwards:<br>
> <br>
> thanassis@taste <br>
> ~/development/rtems/src/rtems-source-builder/rtems/build/rtems-tools<br>
> -4.11-1<br>
> $ ls -l<br>
> total 24<br>
> -rwxr-xr-x 1 thanassis thanassis 5308 Jan 27 11:24 doit<br>
> -rwxr-xr-x 1 thanassis thanassis 5425 Jan 27 11:34 doit.new<br>
> lrwxrwxrwx 1 thanassis thanassis 92 Jan 27 11:34
rtems-tools<br>
> -4.11 -> <br>
> /home/thanassis/development/rtems/src/rtems-source<br>
> -builder/rtems/sources/git/rtems-tools.git<br>
> lrwxrwxrwx 1 thanassis thanassis 92 Jan 27 11:24
rtems<br>
> -tools.git -> <br>
> /home/thanassis/development/rtems/src/rtems-source<br>
> -builder/rtems/sources/git/rtems-tools.git<br>
> <br>
> The hack works, but I of course need to somehow introduce this in
the<br>
> process that emits "doit" - which I understand is driven
from the<br>
> config <br>
> files.<br>
> <br>
> Any help?<br>
> Thanks in advance!<br>
<br>
Could you please try the patch in </font></tt><a href=https://devel.rtems.org/ticket/2495><tt><font size=2>https://devel.rtems.org/ticket/2495</font></tt></a><tt><font size=2>
?<br>
<br>
What a great bug report!<br>
<br>
> P.S. I am not the only one experiencing this - see relevant question<br>
> on <br>
> StackOverflow a month ago: <br>
> <br>
> </font></tt><a href="http://stackoverflow.com/questions/34369549/shell-cmd-failed-while-bu"><tt><font size=2>http://stackoverflow.com/questions/34369549/shell-cmd-failed-while-bu</font></tt></a><tt><font size=2><br>
> ilding-rtems-on-linux-mint<br>
> <br>
> This message and any attachments are intended for the use of the<br>
> addressee or addressees only.<br>
> The unauthorised disclosure, use, dissemination or copying (either
in<br>
> whole or in part) of its<br>
> content is not permitted.<br>
> If you received this message in error, please notify the sender and<br>
> delete it from your system.<br>
> Emails can be altered and their integrity cannot be guaranteed by
the<br>
> sender.<br>
> <br>
> Please consider the environment before printing this email.<br>
> <br>
> _______________________________________________<br>
> users mailing list<br>
> users@rtems.org<br>
> </font></tt><a href=http://lists.rtems.org/mailman/listinfo/users><tt><font size=2>http://lists.rtems.org/mailman/listinfo/users</font></tt></a><tt><font size=2><br>
</font></tt>
<br><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>