<div dir="ltr">Hi,<div><br></div><div>sorry for the late reply.</div><div><br></div><div>So, the patch didn't do a thing. Got the same print.</div><div><br></div><div>But I tried to run waf with python3</div><div><br></div><div><font face="monospace, monospace">python3 /home/niko/.local/bin/waf-2.0.8</font><br></div><div><font face="monospace, monospace"><br></font></div><div><font face="arial, helvetica, sans-serif">and</font></div><div><font face="arial, helvetica, sans-serif"><br></font></div><div><font face="arial, helvetica, sans-serif"><span style="font-family:monospace,monospace;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">python3 /home/niko/.local/bin/waf-2.0.8 install</span><br></font></div><div><br></div><div>That was successful. From that I can assume that there is some issue with the python2 shipped with ubuntu? I can try at home as well in case there is something specific with the python configuration on my current pc and report back.</div><div><br></div><div>Thanks for the help.</div><div><br></div><div>Regards,</div><div>Niko</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jun 22, 2018 at 9:56 PM Christian Mauderer <<a href="mailto:list@c-mauderer.de">list@c-mauderer.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Niko,<br>
<br>
Am 22.06.2018 um 13:23 schrieb Nicolas Tsiogkas:<br>
> Hi,<br>
> <br>
> waf was downloaded by the website (<a href="http://waf.io" rel="noreferrer" target="_blank">waf.io</a> <<a href="http://waf.io" rel="noreferrer" target="_blank">http://waf.io</a>>)<br>
> <br>
> niko@im-desktop-021:~/sandbox/rtems-libbsd$ which waf-2.0.8 <br>
> /home/niko/.local/bin/waf-2.0.8<br>
<br>
Should be OK.<br>
<br>
> <br>
> running also with waf-2.0.4 which used to work gives the same error<br>
> <br>
> ~/sandbox/rtems-libbsd$ waf-2.0.8 -v<br>
> Could not create the directory ///h<br>
> <br>
> ~/sandbox/rtems-libbsd$ waf-2.0.4 -v<br>
> Could not create the directory ///h<br>
> <br>
> that's pretty weird.<br>
<br>
Yes it is. The build scripts do a lot of stuff in preparation for the<br>
real build. But as far as I know nothing of it should create a<br>
directory. The first operation that creates a directory should print the<br>
following line:<br>
<br>
[ 1/99] Compiling testsuite/include/rtems/bsd/test/<a href="http://network-config.h.in" rel="noreferrer" target="_blank">network-config.h.in</a><br>
<br>
Anyway: To find out how far you get into the build scripts, I added a<br>
few debug messages. Could you try to apply the attached patch and see<br>
whether it prints some messages. Note that the messages are not really<br>
clean and it seems that there is a bug that prints them two times. But<br>
they should give a hint when the build process breaks.<br>
<br>
Best Regards<br>
<br>
Christian Mauderer<br>
<br>
> <br>
> Regards,<br>
> Niko<br>
> <br>
> On Fri, Jun 22, 2018 at 12:23 PM Christian Mauderer<br>
> <<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>> wrote:<br>
> <br>
> Hello Niko,<br>
> <br>
> from a quick glance, everything till the waf call looks good. What is<br>
> really odd is the output of the last waf-2.0.8 call. There should be a<br>
> lot more output starting with something like<br>
> <br>
> ----<br>
> Waf: Entering directory<br>
> `/home/EB/christian_m/Projekte/some-project/rtems-libbsd/build/arm-rtems5-atsamv-everything'<br>
> [ 1/122] Creating<br>
> build/arm-rtems5-atsamv-everything/build-include/rtems/bsd/modules.h<br>
> [ 2/122] Compiling rtemsbsd/rtems/generate_kvm_symbols<br>
> [ 3/122] Compiling<br>
> testsuite/include/rtems/bsd/test/<a href="http://network-config.h.in" rel="noreferrer" target="_blank">network-config.h.in</a><br>
> <<a href="http://network-config.h.in" rel="noreferrer" target="_blank">http://network-config.h.in</a>><br>
> [ 4/122] Compiling freebsd/sys/crypto/blowfish/bf_locl.h<br>
> [ 5/122] Compiling freebsd/sys/crypto/blowfish/bf_pi.h<br>
> ...<br>
> ----<br>
> <br>
> You are even missing the "Waf: Entering directory". So that seems like a<br>
> quite early bug.<br>
> <br>
> You can try whether a `waf -v` provides more output. Beneath that: Where<br>
> does your waf come from? You call it with a version number.<br>
> <br>
> Best regards<br>
> <br>
> Christian Mauderer<br>
> <br>
> Am 22.06.2018 um 11:21 schrieb Nicolas Tsiogkas:<br>
> > Hi,<br>
> ><br>
> > I did the process again with no luck. I am attaching a zip with<br>
> command<br>
> > outputs/logs.<br>
> ><br>
> > Regards,<br>
> > Niko<br>
> ><br>
> > On Fri, Jun 22, 2018 at 9:44 AM Nicolas Tsiogkas<br>
> <<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a> <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a>><br>
> > <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a> <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a>>>> wrote:<br>
> ><br>
> > Hi Christian,<br>
> ><br>
> > it is a fresh clone. Although I had a previous build with 4.11 I<br>
> > decided try from scratch given the changes.<br>
> ><br>
> > Error is during the build. I'm configuring normally and when I try<br>
> > to waf it then it fails.<br>
> ><br>
> > Is there any way to increase the verbosity? I will repeat all the<br>
> > process from scratch keeping logs so I can send them and try<br>
> to find<br>
> > the issue. <br>
> ><br>
> > Thanks for your time!<br>
> ><br>
> > Regards,<br>
> > Niko<br>
> ><br>
> > On Thu, Jun 21, 2018 at 6:49 PM Christian Mauderer<br>
> > <<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>><br>
> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>>>> wrote:<br>
> ><br>
> > Am 21.06.2018 um 16:26 schrieb Nicolas Tsiogkas:<br>
> > > And apparently I forgot the host.<br>
> > ><br>
> > > It is ubuntu 16.04:<br>
> > > Linux im-desktop-021 4.13.0-45-generic<br>
> #50~16.04.1-Ubuntu SMP<br>
> > Wed May 30<br>
> > > 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux<br>
> > > gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) <br>
> > ><br>
> > > N.<br>
> > ><br>
> > ><br>
> > > On Thu, Jun 21, 2018 at 4:19 PM Nicolas Tsiogkas<br>
> > <<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a> <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a>><br>
> <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a> <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a>>><br>
> > > <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a> <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a>><br>
> <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a> <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a>>>>> wrote:<br>
> > ><br>
> > > Hi Joel,<br>
> > ><br>
> > > waf-2.0.8 configure --prefix="$sandbox/5"<br>
> > > --rtems-bsps=arm/xilinx_zynq_a9_qemu <br>
> > ><br>
> > > has the following output:<br>
> > ><br>
> > > Setting top to :<br>
> > > /home/niko/sandbox/rtems-libbsd <br>
> > > Setting out to :<br>
> > > /home/niko/sandbox/rtems-libbsd/build <br>
> > > RTEMS Version : 5 <br>
> > > Architectures : arm-rtems5 <br>
> > > Board Support Package :<br>
> > > arm-rtems5-xilinx_zynq_a9_qemu <br>
> > > Show commands : no <br>
> > > Long commands : no <br>
> > > Checking for program 'arm-rtems5-gcc' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-gcc <br>
> > > Checking for program 'arm-rtems5-g++' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-g++ <br>
> > > Checking for program 'arm-rtems5-gcc' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-gcc <br>
> > > Checking for program 'arm-rtems5-ld' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-ld <br>
> > > Checking for program 'arm-rtems5-ar' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-ar <br>
> > > Checking for program 'arm-rtems5-nm' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-nm <br>
> > > Checking for program 'arm-rtems5-objdump' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-objdump <br>
> > > Checking for program 'arm-rtems5-objcopy' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-objcopy <br>
> > > Checking for program 'arm-rtems5-readelf' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-readelf <br>
> > > Checking for program 'arm-rtems5-strip' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-strip <br>
> > > Checking for program 'rtems-ld' :<br>
> > > /home/niko/sandbox/5/bin/rtems-ld <br>
> > > Checking for program 'rtems-tld' :<br>
> > > /home/niko/sandbox/5/bin/rtems-tld <br>
> > > Checking for program 'rtems-bin2c' :<br>
> > > /home/niko/sandbox/5/bin/rtems-bin2c <br>
> > > Checking for program 'tar' : /bin/tar <br>
> > > Checking for program 'gcc, cc' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-gcc <br>
> > > Checking for program 'ar' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-ar <br>
> > > Checking for program 'g++, c++' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-g++ <br>
> > > Checking for program 'ar' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-ar <br>
> > > Checking for program 'gas, gcc' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-gcc <br>
> > > Checking for program 'ar' :<br>
> > > /home/niko/sandbox/5/bin/arm-rtems5-ar <br>
> > > Compiler version (arm-rtems5-gcc) : 7.3.0<br>
> 20180125<br>
> > (RTEMS 5,<br>
> > > RSB 8ee4e8cd557c25fca59bb9751751ad4172530958, Newlib<br>
> 3.0.0) <br>
> > > Checking for RTEMS CPU options header : started <br>
> > > -> processing test results : all ok <br>
> > > Checking for RTEMS_DEBUG : no <br>
> > > Checking for RTEMS_MULTIPROCESSING : no <br>
> > > Checking for RTEMS_NEWLIB : yes <br>
> > > Checking for RTEMS_POSIX_API : yes <br>
> > > Checking for RTEMS_SMP : no <br>
> > > Checking for RTEMS_NETWORKING : no <br>
> > > Checking for RTEMS header : started <br>
> > > -> processing test results : all ok <br>
> > > Checking for header dlfcn.h : yes <br>
> > > Checking for header rtems/pci.h : yes <br>
> > > Configure variant: :<br>
> > > arm-rtems5-xilinx_zynq_a9_qemu-default <br>
> > > Checking for header rtems/rtems-debugger.h : yes <br>
> > > 'configure' finished successfully (0.744s)<br>
> > ><br>
> > > Cheers,<br>
> > > Niko<br>
> > ><br>
> > > On Thu, Jun 21, 2018 at 4:09 PM Joel Sherrill<br>
> > <<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a> <mailto:<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a>><br>
> <mailto:<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a> <mailto:<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a>>><br>
> > > <mailto:<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a> <mailto:<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a>><br>
> <mailto:<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a> <mailto:<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a>>>>> wrote:<br>
> > ><br>
> > ><br>
> > ><br>
> > > On Thu, Jun 21, 2018 at 8:52 AM, Nicolas Tsiogkas<br>
> > > <<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a> <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a>><br>
> <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a> <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a>>><br>
> > <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a> <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a>><br>
> <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a> <mailto:<a href="mailto:lou.nick@gmail.com" target="_blank">lou.nick@gmail.com</a>>>>> wrote:<br>
> > ><br>
> > > Hi,<br>
> > ><br>
> > > following the steps described<br>
> > > in <a href="https://github.com/RTEMS/rtems-libbsd" rel="noreferrer" target="_blank">https://github.com/RTEMS/rtems-libbsd</a> I<br>
> get an<br>
> > error<br>
> > ><br>
> > > "Could not create the directory ///h" while<br>
> trying<br>
> > to build<br>
> > > with waf 2.0.8<br>
> > ><br>
> > > Is it a known problem?<br>
> > ><br>
> > ><br>
> > > Not to me.<br>
> > ><br>
> > > What's your configure command and host? <br>
> > ><br>
> > ><br>
> > > I have seen that the installation procedure has<br>
> > changed<br>
> > > since 4.11 and now the tools and the bsps are<br>
> > installed in<br>
> > > the same prefix, but that shouldn't matter I<br>
> suppose.<br>
> > ><br>
> > > Thank you in advance.<br>
> > ><br>
> > > Regards,<br>
> > > Niko<br>
> > ><br>
> > > _______________________________________________<br>
> > > users mailing list<br>
> > > <a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>><br>
> > <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>>><br>
> > > <a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > users mailing list<br>
> > > <a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>><br>
> > > <a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><br>
> > ><br>
> ><br>
> > Hello Nicolas,<br>
> ><br>
> > I also don't know that problem. The directory that should<br>
> be created<br>
> > "///h" looks like there are some variables missing between the<br>
> > slashes.<br>
> > But I'm not aware of any directory h that should be created<br>
> > somewhere.<br>
> ><br>
> > - Did you upgrade from a earlier build or do you build in<br>
> a fresh<br>
> > checkout? There have been some changes to the build system in<br>
> > the last<br>
> > months that have lead to incompatible cache files. If it is an<br>
> > old tree,<br>
> > try to remove `build` and `.lock-waf_*`.<br>
> ><br>
> > - About when does the problem happen? It seems your configure<br>
> > runs fine.<br>
> > So I assume that it appears during build or install. Maybe<br>
> you could<br>
> > provide some lines of context to the error message?<br>
> ><br>
> > Best regards<br>
> ><br>
> > Christian Mauderer<br>
> ><br>
> <br>
> -- <br>
> --------------------------------------------<br>
> embedded brains GmbH<br>
> Herr Christian Mauderer<br>
> Dornierstr. 4<br>
> D-82178 Puchheim<br>
> Germany<br>
> email: <a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> Phone: +49-89-18 94 741 - 18<br>
> Fax: +49-89-18 94 741 - 08<br>
> PGP: Public key available on request.<br>
> <br>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.<br>
> <br>
<br>
</blockquote></div>