Error building libbsd

Nicolas Tsiogkas lou.nick at gmail.com
Fri Jun 22 07:44:07 UTC 2018


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>
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>> 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>> wrote:
> >
> >
> >
> >         On Thu, Jun 21, 2018 at 8:52 AM, Nicolas Tsiogkas
> >         <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>
> >             http://lists.rtems.org/mailman/listinfo/users
> >
> >
> >
> >
> > _______________________________________________
> > users mailing list
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20180622/2a16728b/attachment-0002.html>


More information about the users mailing list