Problem building master

[Isaac Gutekunst]

../rtems/configure --enable-rtemsbsp="stm32f7x" --enable-maintainer-mode 
--disable-tests  --enable-cxx  --target=arm-rtems4.12 
--prefix=$RTEMS/lib-rtems --disable-networking

Since this is still our unreleased BSP, there could be some issues 
related to it. I'm just not sure what to look for.


I built GCC last week I believe.

Here is the --version output:

arm-rtems4.12-gcc (GCC) 6.0.0 20160228 (RTEMS 4.12, RSB 
b537e5536459e207fc8e56a1df3774c1700606d5, Newlib 2.3.0.20160226)


Isaac

On 03/07/2016 11:32 AM, Joel Sherrill wrote:
> This is odd. I just did a fresh update and rebuilt sparc/sis with POSIX
> enabled.
> I didn't have trouble.
>
> The gcc+newlib version bumped last week but that shouldn't have had an
> impact
> yet and wouldn't have broken this. It added prototypes for a few pthread
> routines
> I am adding.
>
> How did you configure exactly?
>
> --joel
>
> On Mon, Mar 7, 2016 at 9:24 AM, Isaac Gutekunst
> <isaac.gutekunst at vecna.com <mailto:isaac.gutekunst at vecna.com>> wrote:
>
>     Correcting my subject typo.
>
>     On 03/07/2016 10:23 AM, Isaac Gutekunst wrote:
>
>         Hi,
>
>         I'm trying to build RTEMS master for ARM, and am getting the
>         following
>         compile error:
>
>         ../../../../../../rtems/c/src/../../cpukit/libfs/src/pipe/fifo.c: In
>         function 'pipe_interruptible':
>         ../../../../../../rtems/c/src/../../cpukit/libfs/src/pipe/fifo.c:76:34:
>         error: 'Thread_queue_Control {aka struct <anonymous>}' has no member
>         named 'state'
>              the_barrier->Barrier.Wait_queue.state |=
>         STATES_INTERRUPTIBLE_BY_SIGNAL;
>                                             ^
>         ../../../../../../rtems/c/src/../../cpukit/libfs/src/pipe/fifo.c:80:34:
>         error: 'Thread_queue_Control {aka struct <anonymous>}' has no member
>         named 'state'
>              the_barrier->Barrier.Wait_queue.state |=
>         STATES_INTERRUPTIBLE_BY_SIGNAL;
>
>
>         I can't seem to find a definition for the Barrier_Control struct,
>         andhaven't been able to find a root cause.
>
>         It could as always be a bootstrapping/cleaning problem where the
>         wrong
>         file is being built, but I don't think so.
>
>         Anyone know what's going on?
>
>         Thanks,
>
>         Isaac
>         _______________________________________________
>         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 <mailto:users at rtems.org>
>     http://lists.rtems.org/mailman/listinfo/users
>
>