Re: [Gcl-devel] GCL build failure

[arnuld uttre]

> On 9/9/14, Camm Maguire <address@hidden> wrote:

> Greetings!  Thanks for your report -- nice to meet a gNewSense user!

It is nice to see GCL developing too :)


> This is a Debian based target.  On my Debian machine, ucontext_t is
> broght in by signal.h.  The output of the following will help:
>
> grep -r ucontext_t /usr/include

address@hidden:/usr/local/src/gcl# grep -r ucontext_t /usr/include
grep: /usr/include/python2.5_d/numpy: No such file or directory
/usr/include/ucontext.h:extern int getcontext (ucontext_t *__ucp) __THROW;
/usr/include/ucontext.h:extern int setcontext (__const ucontext_t
*__ucp) __THROW;
/usr/include/ucontext.h:extern int swapcontext (ucontext_t *__restrict __oucp,
/usr/include/ucontext.h:                        __const ucontext_t *__restrict 
__ucp) __THROW;
/usr/include/ucontext.h:extern void makecontext (ucontext_t *__ucp,
void (*__func) (void),
/usr/include/signal.h:/* This will define `ucontext_t' and `mcontext_t'.  */
grep: /usr/include/python2.5/numpy: No such file or directory
/usr/include/sys/ucontext.h:  } ucontext_t;
/usr/include/sys/ucontext.h:  } ucontext_t;
address@hidden:/usr/local/src/gcl#




> Presumably this structure was already correctly found in the preceding
> compilation of o/usig.c, which you can examine with
>
> cpp -Ih o/usig.c

This throws out huge lines of code on screen.






-- 
http://uttre.wordpress.com/
http://lispmachine.wordpress.com/2010/12/08/extract-of-programming/