From: Bryan Hundven <bryanhundven@gmail.com>
To: Bill Cunningham <billcun@suddenlink.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc-4.6.0 breaks
Date: Thu, 02 Jun 2011 03:11:00 -0000 [thread overview]
Message-ID: <BANLkTi=PrinUuz=AftTFiEQLV7g8p1QZug@mail.gmail.com> (raw)
In-Reply-To: <000f01cc20cf$551c7830$a9d3daad@YOUREDC1953E71>
On Wed, Jun 1, 2011 at 7:46 PM, Bill Cunningham <billcun@suddenlink.net> 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
next prev parent reply other threads:[~2011-06-02 3:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 2:29 Dennis Clarke
2011-06-02 2:47 ` Bill Cunningham
2011-06-02 3:11 ` Bryan Hundven [this message]
2011-06-02 4:59 ` Miles Bader
2011-06-02 8:31 ` Bryan Hundven
-- strict thread matches above, loose matches on Subject: below --
2011-06-02 2:16 Dennis Clarke
2011-06-02 2:25 ` Bill Cunningham
2011-06-02 8:12 ` Jonathan Wakely
[not found] ` <002701cc2103$ef433780$a9d3daad@YOUREDC1953E71>
[not found] ` <BANLkTinaXqk2ts7q8n3-Uoa=z0B2-xwR6Q@mail.gmail.com>
2011-06-02 11:22 ` Bill Cunningham
2011-06-02 11:32 ` Jonathan Wakely
2011-06-02 12:17 ` Bill Cunningham
2011-06-02 14:11 ` Jonathan Wakely
2011-06-02 14:21 ` Marc Glisse
2011-06-02 15:06 ` Jonathan Wakely
2011-06-02 19:41 ` Bill Cunningham
2011-06-02 18:28 ` kevin diggs
2011-06-02 2:11 Bill Cunningham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=PrinUuz=AftTFiEQLV7g8p1QZug@mail.gmail.com' \
--to=bryanhundven@gmail.com \
--cc=billcun@suddenlink.net \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).