Well, I would come to the hardware conclusion too if it were not for two
things:
1) I can compile the kernel (2.2.12) all day long with no problems.
2) I had a working system and compiled gcc-2.95.1 with egcs-1.1.2 and
glibc-2.1.2 with the the resulting gcc ( I only had a problem when I
botched the install of the resulting library and ended up --long story--
re-installing the base debian 2.1 system etc... etc...).
3) I had the same problem on another machine running slackware 3.0 that I
upgraded by hand to glibc-2.0.7. There was some kind of funny interaction
between the supplied gcc-2.7.2.3 and gcc-2.8.1 that I was trying to build.
I ended up downgrading to gcc-2.7.2.1 and then gcc-2.8.1 would build.
Then, I could build egcs-1.1.2 and then glibc-2.0.7. I still don't know
why gcc-2.7.2.1 would build gcc-2.8.1, but 2.7.2.3 would not.
If nobody has any insight for me, I guess I will have to go through this
time consuming, "step up through compiler versions" process again.
I also am wondering why configure can't seem to determine the right minor
number for the installed glibc.
Sorry to bother you folks with this, but it's frustrating to say the least
:)
Tim Hillman
On Thu, 30 Sep 1999, Keith Duthie wrote:
> On Wed, 29 Sep 1999, Tim Hillman wrote:
>
> > I see in the faq that comes with the source, there is a reference to
> > Signal 11 on Linux, but there is no entry for it. Only a reference to a
> > file on a server someplace that I can't seem to get to. I think it is out
> > of date.
> Your problem is either not enough virtual memory, or (more likely) bad
> hardware. Look at http://www.bitwizard.nl/sig11/ for more details.
>
> --
> Understanding is a three edged sword. Do you *want* to get the point?
> http://www.albatross.co.nz/~psycho/ O-
>
>
