Re: compile crash #1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Jan 20, 2006 at 10:06:42PM -0600, Sokar Someone wrote:
> changed to debian stable gcc --version == 3.3.5-13
> 
> getting the :
> 
> ../../gcc-2.95.3/gcc/libgcc2.c:41 stdlib.h: No such file or directory
> ../../gcc-2.95.3/gcc/libgcc2.c:42 unistd.h: No such file or directory
> 
> error... again
> 
> dl'd bbc-2.1-with-sources.tar.gz
> 
> is there something else i am supposed to be working with?
> 

The bbc-2.1-with-sources.tar.gz would be a bit outdated.  A tarball of the
current snapshot that I'm building with, which compiles from start to finish
without intervention on a fresh install of Debian Sarge, can be obtained from:

  http://bccd.cs.uni.edu/bbc-images/lnx-bbc.tar.bz2

If it doesn't compile for you, chances are you have a Debian package missing,
such as bin86.  I can provide my Debian package list from 
'dpkg --get-selections' and walk anyone through an 'apt-get dselect-upgrade'
if there's interest.

This tarball has gar.conf.mk set up to fetch things from bccd.cs.uni.edu's
garchive first, lnx-bbc.org second.  I have direct access to bccd.cs.uni.edu
and can make sure that the garchive is "sync'd".

This brings up a great question, Sokar.   Going forward, how should the tree be
maintained?  I started on the lnx-bbc with cvs and can continue working with
arch.  There's also subversion.  Does anyone have a compelling reason to use
one or the other?
- -- 
Paul Gray                                         -o)
323 Wright Hall                                   /\\
University of Northern Iowa                      _\_V
Message void if penguin violated ...  Don't mess with the penguin
No one says, "Hey, I can't read that ASCII attachment ya sent me."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFD0mErOH45TZW7mh4RAoKAAJsF6X35I/Fs97DcoT+Qlk2uvTxgEgCfQeGh
mInlh5kzdbjDHvRHJ9kjNZ0=
=OeHG
-----END PGP SIGNATURE-----