[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

troubles building rtems - first hacks



Hi

> The pipe code must be horribly broken in CygWin.  Report this and
mention
> that you saw it building a cross-compiler for RTEMS.  It may help get
> responses.
Ok!
> > Then it will fail at:
> > /gcc-m68k-rtems/bin/m68k-rtems-gcc -Dmcpu32 -D__mcpu32__  -m68020
> > -mnobitfield -
> > msoft-float -Wall -ansi -fasm -g -B/rtems-build/gen68360/lib/ -specs
> > bsp_specs -
> > qrtems -I/rtems-build/gen68360/lib/include/ka9q  -O4
> > -fomit-frame-pointer     -c
> >  -o o-gen68360/key.o
> > ../../../../../rtems-980219/c/src/exec/posix/src/key.c
> > ../../../../../rtems-980219/c/src/exec/posix/src/key.c: In function
> > `_POSIX_Keys
> > _Run_destructors':
> > ../../../../../rtems-980219/c/src/exec/posix/src/key.c:259:
> > `PTHREAD_DESTRUCTOR_
> > ITERATIONS' undeclared (first use this function)
> > ../../../../../rtems-980219/c/src/exec/posix/src/key.c:259: (Each
> > undeclared ide
> > ntifier is reported only once
> > ../../../../../rtems-980219/c/src/exec/posix/src/key.c:259: for each
> > function it
> >  appears in.)
> 
> You are not getting the right newlib source.  I don't know why. 
This gets
> reported periodically but I never rememebr seeing the fix.  Did you
apply
> the newlib-rtems patch?
> 
Yes I did.
I gave a look at the source code and it's odd. It's just standard C...
except of the first line:
what is #include_next ?

I'm going to try without posix first

Geoffroy
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com