> -Original Message-
> From: Chris Johns [mailto:chr...@rtems.org]
> Sent: Thursday, August 31, 2017 3:00 AM
> To: Jeff Mayes ; Christian Mauderer mauderer.de>; devel@rtems.org
> Subject: Re: problem building libbsd with waf
>
> On 31/08/2017 07:32, Jeff Mayes
On 31/08/2017 07:32, Jeff Mayes wrote:
>
> I'm using a CentOS 7 VM and I've built it successfully on previous occasions.
>
Shared disk in the VM? I have found various issues when sharing disks with the
host.
Chris
___
devel mailing list
devel@rtems.
Am 30.08.2017 um 23:32 schrieb Jeff Mayes:
>
>
>> -Original Message-
>> From: Christian Mauderer [mailto:l...@c-mauderer.de]
>> Sent: Wednesday, August 30, 2017 2:38 PM
>> To: Jeff Mayes ; devel@rtems.org
>> Subject: Re: problem building libbsd w
> -Original Message-
> From: Christian Mauderer [mailto:l...@c-mauderer.de]
> Sent: Wednesday, August 30, 2017 2:38 PM
> To: Jeff Mayes ; devel@rtems.org
> Subject: Re: problem building libbsd with waf
>
> Am 29.08.2017 um 17:39 schrieb Jeff Mayes:
> > Hi
&g
Am 29.08.2017 um 17:39 schrieb Jeff Mayes:
> Hi
>
>
>
> I’m trying to build rtems and rtems-libbsd. It all goes fine until the
> waf build fails with this:
>
> / Checking for RTEMS CPU options header : no/
>
>
>
> This occurs for both i386 and arm. Part of the config.log is below.
>
There's probably something wrong with my environment.
>
>
> > -Original Message-
> > From: Chris Johns [mailto:chr...@rtems.org]
> > Sent: Wednesday, August 30, 2017 3:24 AM
> > To: Jeff Mayes ; devel@rtems.org
> > Subject: Re: problem building lib
> Subject: Re: problem building libbsd with waf
>
> On 30/8/17 1:39 am, Jeff Mayes wrote:
> >
> > I'm trying to build rtems and rtems-libbsd. It all goes fine until
> > the waf build fails with this:
> >
> > / Checking for RTEMS CPU options header : n
On 30/8/17 1:39 am, Jeff Mayes wrote:
>
> I’m trying to build rtems and rtems-libbsd. It all goes fine until the waf
> build fails with this:
>
> / Checking for RTEMS CPU options header : no/
>
>
>
> This occurs for both i386 and arm. Part of the config.log is below.
>
>
>
> Any idea