Juho Snellman wrote:
> Jon Buller <jon@...> writes:
>> I'm trying to build SBCL on a NetBSD 4.0_beta2 i386 machine and ended up
>> in LDB. The messages leading up to this were:
>> However, I have very little idea how to debug or fix this, and any hints
>> or suggestions would be welcome. For what it is worth, I was building
>> this a few days ago, but it was failing to build some of the contrib
>> stuff then. I'm now building in a chroot sandbox, and I've moved the
>> disk partitions around a bit, but none of that should matter. This was
>> being bootstrapped with clisp 2.39, but when it was getting past warm
>> init, I was doing it with both that and SBCL itself.
> I'm not completetely sure of what you mean by the last
> sentence. Building with clisp as the host is not recommended. It works
> some times, but most of the time something gets miscompiled (either
> due to a clisp or SBCL bug), which causes a failure pretty much like
> the one you describe. But are you saying that the same thing happens
> when you're using SBCL as the host compiler?
Sorry that wasn't as clear as it should have been. What I meant was
that before I reconfigured the disks, and I was building and installing
in the "main" system, it worked with both SBCL and CLisp. In fact I
have never had problems like that with CLisp before, and that goes back
off and on to building SBCL 0.9.1.
However, now I have a chroot environment for the build, (for rebuilding
the OS and while it's in place, might as well do SBCL as well...) it's
not working. I do not believe that the libraries in the chroot
environment are broken, as NetBSD is able to build all it's tools,
libraries, utilities, etc. install and run them there, etc. OTOH, I
lost my copy of SBCL in the process, and now I can't rebuild it from
CLisp like I used to.
BTW, this is in an attempt to update the lang/sbcl package in pkgsrc
(from 0.9.1 to something more recent) but I was having problems with the
contrib packages. It looked like the lisp version of
getprotobyname("tcp") was returning NULL, but I wasn't able to dig in
too deeply, and now I can't even get that far.
And while I'm rambling on, I have a minor nit: Why use tar to install
the sb-* contrib packages? It makes the automated tools to build
packages break, since they do a "find install/prefix -newer
file_touched_before_install" to make the packaging manifest lists. It
seems that "cp -r" would work just as well as tar for the job at hand.
But to be really pedantic, is there any point to installing the CVS
Finally, thanks for the great system. It really works wonderfully
almost all the time for me, and it is so much faster than CLisp...