From: Richard M K. <kr...@pr...> - 2004-09-14 12:52:11
|
On Tue, Sep 14, 2004 at 07:26:14AM +0100, Christophe Rhodes wrote: > Nikodemus Siivola <tsi...@cc...> writes: > > > If it makes things work and doesn't break things elsewhere, doing > > that #include sounds like a good thing... > > > > Offhand, no -- but while building _gc-internal.o_? There's no > > gc-internal.c, so why is it trying to build something like that? > > /me is confused > > The sound of gc-internal.o is indeed odd. I'm sorry, my report was wrong. The actual error text: -- save.o(.text+0x4d): In function `search_space': /home/kreuter/lisp/impl/sbcl-lt/sbcl-0.8.14.7/src/runtime/gc-internal.h:115: undefined reference to `fixnump' thread.o(.text+0x4d): In function `search_space': /home/kreuter/lisp/impl/sbcl-lt/sbcl-0.8.14.7/src/runtime/gc-internal.h:115: undefined reference to `fixnump' gmake: *** [sbcl] Error 1 -- #include'ing gc.h in gc-internal.h does make these go away, but I don't know whether gc-internal.h is the right place to do that. -- Richard |