Error building libbsd

Nicolas Tsiogkas lou.nick at gmail.com
Thu Jun 28 12:10:31 UTC 2018


Hi,

some later report. I compiled the examples and some private project with
waf and all was smoothly. I suspect that there must be something with the
libbsd scripts.

Cheers,
Niko

On Mon, Jun 25, 2018 at 10:20 AM Nicolas Tsiogkas <lou.nick at gmail.com>
wrote:

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


More information about the users mailing list