unable to compile rtems-libbsd

Sat May 13 00:57:48 UTC 2017

Thanks Gedare.  Yeah the tool chain is the problem.  The problem lies with macro __NULLABILITY_PRAGMA_PUSH and __NULLABILITY_PRAGMA_POP are introduced in a later version of the tool in which current libbsd uses.  Anyway, if people try to get around rebuilding the tool chain, one can add

#define __NULLABILITY_PRAGMA_PUSH
#define __NULLABILITY_PRAGMA_POP

in <sys/cdefs.h>.  This file (along with other toolchain header files) is located in the toolchain include directory.

In my opinion, the err.h should've been implemented as
#ifdef __NULLABILITY_PRAGMA_PUSH
__NULLABILITY_PRAGMA_PUSH
#endif

rather than assuming it is always defined.

Phong.

-----Original Message-----
From: gedare at gwmail.gwu.edu [mailto:gedare at gwmail.gwu.edu] On Behalf Of Gedare Bloom
Sent: Thursday, May 11, 2017 10:02 AM
To: Pham, Phong
Cc: users at rtems.org; Hillman, Robert
Subject: Re: unable to compile rtems-libbsd

On Thu, May 11, 2017 at 12:26 PM, Pham, Phong <phamp at ddc-web.com> wrote:
>
>
> Hi,
>
>
>
> After following the README.waf procedure, I receive the following
> error (at the end of the email) in step 8 right when I issued waf command.
>
>
>
> Any advise on the compiler error below?  I am currently using RTEMS
> checkedout (cloned) on May 8th 2017 but the tool chain (RSB) that I
> successfully compiled is early Jan.  Re-cloning tool chain w/ today’s
> date???
>
Generally it is necessary to keep your tool chain (RSB) synced with the version of RTEMS you use. In this case, you are using the development master branch, so you definitely may have breakage caused by an outdated tool chain. So definitely try that first, and re-build your RTEMS with the updated toolchain before trying the libbsd.

>
>
> I randomly selected powerpc virtex5 RTEMS BSP, configure it, make,
> make install it, re-configure waf, run waf and still receive the same
> error…  Do you have a PowerPC BSP that is known to be compatible with
> rtems-libbsd so that waf can compile so I can use it as a baseline?  I
> know the README.waf provide xilinx_zynq_a9_qemu as a BSP ex. but it is
> for ARM…
>
Sebastian?

>
>
> Thanks,
>
> Phong.
>
>
>
> Below is the compiler error when I use my scs750 BSP.
>
>
>
> In file included from ../../freebsd/sbin/pfctl/parse.y:76:0:
>
> ../../freebsd/include/err.h:49:1: error: expected '=', ',', ';', 'asm'
> or '__attribute__' before 'void'
>
> void err(int, const char *, ...) __dead2 __printf0like(2, 3);
>
> ^~~~
>
> In file included from ../../freebsd/sbin/pfctl/parse.y:78:0:
>
> /home/phamp/development/rtems/4.12/powerpc-rtems4.12/include/pwd.h:51:1:
> error: expected '=', ',', ';', 'asm' or '__attribute__' before 'struct'
>
> struct passwd {
>
> ^~~~~~
>
> ../../freebsd/sbin/pfctl/parse.y: In function '_bsd_pfctl_pfctlyparse':
>
> ../../freebsd/sbin/pfctl/parse.y:3342:24: error: 'struct passwd' has
> no member named 'pw_uid'
>
>      $$ = pw->pw_uid;
>
>                         ^
>
>
>
> Build failed
>
> -> task in 'yacc_pfctly' failed with exit status 1:
>
>               {task 44351728: c parse.c -> parse.c.10.o}
>
> ['/home/phamp/development/rtems/4.12/bin/powerpc-rtems4.12-gcc',
> '-qrtems',
> '-B/home/phamp/development/rtems/4.12/powerpc-rtems4.12/lib/',
> '-B/home/phamp/development/rtems/4.12/powerpc-rtems4.12/scs750/lib/',
> '--specs', 'bsp_specs', '-mcpu=750', '-mcpu=750', '-mmultiple',
> '-mmultiple', '-mstring', '-mstring', '-mstrict-align',
> '-mstrict-align', '-O2', '-g', '-fno-strict-aliasing',
> '-ffreestanding', '-fno-common', '-w', '-Irtemsbsd/powerpc/include',
> '-I../../rtemsbsd/powerpc/include',
> '-Ifreebsd/sys/powerpc/include',
> '-I../../freebsd/sys/powerpc/include',
> '-Irtemsbsd/include', '-I../../rtemsbsd/include', '-Ifreebsd/sys',
> '-I../../freebsd/sys', '-Ifreebsd/sys/contrib/pf',
> '-I../../freebsd/sys/contrib/pf', '-Ifreebsd/sys/net',
> '-I../../freebsd/sys/net', '-Ifreebsd/include',
> '-I../../freebsd/include', '-Ifreebsd/lib', '-I../../freebsd/lib',
> '-Ifreebsd/lib/libbsdstat', '-I../../freebsd/lib/libbsdstat',
> '-Ifreebsd/lib/libc/include', '-I../../freebsd/lib/libc/include',
> '-Ifreebsd/lib/libc/isc/include',
> '-I../../freebsd/lib/libc/isc/include', '-Ifreebsd/lib/libc/resolv',
> '-I../../freebsd/lib/libc/resolv', '-Ifreebsd/lib/libutil',
> '-I../../freebsd/lib/libutil', '-Ifreebsd/lib/libkvm',
> '-I../../freebsd/lib/libkvm', '-Ifreebsd/lib/libmemstat',
> '-I../../freebsd/lib/libmemstat', '-Ifreebsd/lib/libipsec',
> '-I../../freebsd/lib/libipsec', '-Ifreebsd/contrib/expat/lib',
> '-I../../freebsd/contrib/expat/lib', '-Ifreebsd/contrib/libpcap',
> '-I../../freebsd/contrib/libpcap', '-Ifreebsd/contrib/libxo',
> '-I../../freebsd/contrib/libxo', '-Irtemsbsd/sys',
> '-I../../rtemsbsd/sys', '-ImDNSResponder/mDNSCore',
> '-I../../mDNSResponder/mDNSCore', '-ImDNSResponder/mDNSShared',
> '-I../../mDNSResponder/mDNSShared',
> '-ImDNSResponder/mDNSPosix', '-I../../mDNSResponder/mDNSPosix',
> '-Itestsuite/include', '-I../../testsuite/include',
> '-DHAVE_RTEMS_SCORE_CPUOPTS_H=1', '-DHAVE_RTEMS_H=1',
> '../../freebsd/sbin/pfctl/parse.c', '-c',
> '-o/home/phamp/Desktop/rtems-dev/rtems_0508/rtems-libbsd/build/powerpc
> -rtems4.12-scs750/freebsd/sbin/pfctl/parse.c.10.o']
>
> Notice: This e-mail and any files transmitted with it may contain Data
> Device Corporation's privileged and proprietary information. It is
> intended solely for the use of the individual or entity to whom it is
> addressed. If you are not the named recipient of this transmission,
> any disclosure, copying, distribution or reliance on the contents of
> this message is prohibited. If you received this e-mail in error,
> please destroy it and any attached files and notify me immediately.
>
>
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
Notice: This e-mail and any files transmitted with it may contain Data Device Corporation's privileged and proprietary information. It is intended solely for the use of the individual or entity to whom it is addressed. If you are not the named recipient of this transmission, any disclosure, copying, distribution or reliance on the contents of this message is prohibited. If you received this e-mail in error, please destroy it and any attached files and notify me immediately.