[bitc-dev] Compiling on FreeBSD 6.1

[Christopher Nelson]

> On Fri, 2006-05-19 at 08:57 -0600, Christopher Nelson wrote:
> > I downloaded the source tree for coyotos last night, and being 
> > particularly interested in BitC, I tried to compile it on FreeBSD.
> > There were a few basic erros in libsherpa and astmaker, 
> most of which 
> > boiled down to the need to add:
> >  
> > -I/usr/local/include
> > -L/usr/local/lib
> >  
> > To the INC and LIB sections in the Makefile so that it 
> could find gmp 
> > and the gc stuff.  A couple of other minor corrections, 
> like removing 
> > the sys/statfs.h include and adding a couple others, were needed.
> 
> Why are libgc and libgmp installed in non-standard places?

In FreeBSD that _is_ the standard place for those libraries and include
files.  Anything that gets installed from the ports collection goes in
/usr/local.  So there's a whole 'nother root system based at /usr/local/
with /etc /bin /sbin /include /lib and so on.  It's not what I would
prefer, but... That's the way it is! :-D
 
> Also, can you specify what include changes were needed? We 
> may simply be able to adopt those chagnes.

Sure.  I'll have to do it when I get home, b/c I don't have access to my
build machine from here.

> > Does anyone have any idea what the problem might be, or 
> what I could 
> > do to get past it?
> 
> Not without a lot more information...

:-D  I started with GDB as requested, and it seems like there's some
sort of hangup in the GC path, so I'm recompiling the GC without some of
the options that it had.  I turned off parallel marking, and next I'll
turn off pthreads support.  One of the options was "redirect", that is,
provide automatic malloc support.  Do you use the GC stuff explicitly,
or just through the normal malloc stuff?  It's not *supposed* to cause
problems to turn that on, but I can see how it would if you didn't
expect certain allocations to get collected...

-={C}=-