From: GHui <ugiwgh@gmail.com>
To: "Andrew Haley" <aph@redhat.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Problem with gcc-4.8.2 compile
Date: Tue, 22 Oct 2013 14:39:00 -0000 [thread overview]
Message-ID: <tencent_50D0A8FB3842F39237020561@qq.com> (raw)
Sorry, I misunderstand top-post.
Did you mean that I shouldn't cc to gcc-help@gcc.gnu.org, or others?
To execute "rpm -qf /lib64/libc.so" to find which pkg it belong to.
In my system(el6).
The /usr/lib64/libc.so belong to glibc-devel-2.12.
The /lib64/libc.so belong to none.
So, I think someone made it.
Thanks for you help.
GHui
------------------ Original ------------------
From: "Andrew Haley";<aph@redhat.com>;
Date: Tue, Oct 22, 2013 09:46 PM
To: "GHui"<ugiwgh@gmail.com>;
Cc: "gcc-help"<gcc-help@gcc.gnu.org>;
Subject: Re: Problem with gcc-4.8.2 compile
On 10/22/2013 02:15 PM, GHui wrote:
> I compiled gcc with the following step
> 1) cd gcc-4.8.1
> 2) mkdir build
> 3) cd build
> 4)../configure --build=x86_64-redhat-linux --prefix=/usr/local/gcc-4.8.1 --enable-FEATURE=yes --with-gmp=/usr/local/gmp-4.3.2 --with-mpfr=/usr/local/mpfr-2.4.2 --with-mpc=/usr/local/mpc-0.8.1/ --enable-languages=c,c++ --disable-multilib
> 5) make
Please do not top-post on gcc-help or I will not help you.
I wonder if you may be missing some libraries. glibc-devel, perhaps?
"yum-builddep gcc" as root should install everything.
Enterprise Linux Server release 6.0 is old.
Andrew.
next reply other threads:[~2013-10-22 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 14:39 GHui [this message]
2013-10-26 21:32 ` Jonathan Wakely
-- strict thread matches above, loose matches on Subject: below --
2013-10-22 13:36 GHui
2013-10-22 1:26 GHui
2013-10-22 8:25 ` Andrew Haley
2013-10-22 9:29 ` GHui
2013-10-22 10:22 ` Andrew Haley
2013-10-22 10:25 ` Andrew Haley
[not found] ` <tencent_43D371E83A8EED71300F1003@qq.com>
2013-10-22 13:46 ` Andrew Haley
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=tencent_50D0A8FB3842F39237020561@qq.com \
--to=ugiwgh@gmail.com \
--cc=aph@redhat.com \
--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).