On Wed, Jun 1, 2011 at 7:46 PM, Bill Cunningham <billcun@xxxxxxxxxxxxxx> wrote: > Dennis Clarke wrote: >>> >>> Dennis Clarke wrote: >>>>> >>>>> Â ÂMy gcc-4.6.0 compilation after compiling for quite some time >>>>> decided to >>>>> break with an error to stderr of something like not recognized >>>>> object files. >>>>> I am compiling with gcc-3.3.6. This can sure be nerve racking. Does >>>>> anyone know what this means? >>>>> >>>> >>>> How would anyone even begin to help with this email content ? >>>> >>>> Okay, so let's see, so you're running Debian Linux on a DEC alpha >>>> and you are trying to bootstrap GCC 4.6.0 while using GCC 3.3.6 with >>>> binutils maybe maybe not and your configure line was black magic >>>> while facing east with a dead cat under a rising moon ? >>>> >>>> My guess is that you need to face west. >>>> >>>> Try again with some content please ! >>> >>> Â ÂI didn't get a log of stderr. I wish I had it turned on now. I'm >>> using an old RH 9 for the i686 and binutils-2.21 along with >>> gcc-3.3.6. I have have >>> gmp mpfc and mpc all installed and I am using make-3.82. I was rather >>> surprised when it broke. If I try again I will get a stderr log. >>> >> >> Can you just login remotely with an xterm or better yet fire up screen >> with session logging and then go to a fresh clean directory. Then >> let's try a boot strap again and this time everything gets logged. >> >> wdyt ? > > Â Nope. Don't have X on my system. Never installed it and removed what few > directories were left. I have xfree86 binaries but they are kind of old and > want an even newer glibc than I have I believe. But I can still get errors > logged with the shell. $ apt-get install screen $ screen -L $ build your toolchain $ exit post screenlog.0 > Bill > > -Bryan
