From: "Bill Cunningham" <billcun@suddenlink.net>
To: <gcc-help@gcc.gnu.org>
Subject: gcc 4.6.0 breaks
Date: Thu, 02 Jun 2011 23:40:00 -0000 [thread overview]
Message-ID: <001701cc217e$5aaaf150$a9d3daad@YOUREDC1953E71> (raw)
I tried to mail in a log concerning the error from this compilation and
the mailer daemon mailed it back and said it was too large. It was
concerning not knowing something about the right kind of object files.
ldconfig -v showed that ld.so knows where the libraries are.
Bill
next reply other threads:[~2011-06-02 23:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 23:40 Bill Cunningham [this message]
2011-06-02 23:48 Bill Cunningham
2011-06-03 0:06 ` Jonathan Wakely
2011-06-03 0:50 ` Bill Cunningham
2011-06-03 5:48 ` Ian Lance Taylor
2011-06-03 18:13 ` Bill Cunningham
2011-06-03 20:14 ` Ian Lance Taylor
2011-06-03 22:20 ` Jonathan Wakely
2011-06-03 8:13 ` Jonathan Wakely
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='001701cc217e$5aaaf150$a9d3daad@YOUREDC1953E71' \
--to=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).