From: Av Vl <anvitvl@altavista.com>
To: gcc-help@gcc.gnu.org
Subject: Internal compiler error
Date: Mon, 02 Jul 2001 08:04:00 -0000 [thread overview]
Message-ID: <20010702150432.5189.cpmta@c012.sfo.cp.net> (raw)
Hi. I've downloaded gcc-3.0 and glibc-2.2.3 recently. I've installed gcc to /usr, everything seemed to be ok, but after recompilation of NVidia kernel driver for X it didn't start anymore. Moreover, X fails to start because of the GLX module(using the opensource nv driver). After installation of glibc-2.2.3 i can't recompile either glibc or gcc because of some internal errors, though a few source tarballs have successfully compiled. Actually, gcc --version show 3.0 and /lib/libc.so.6 2.2.3. Now i get unresolved symbols when either inserting NVdriver or alsa sound driver. My linux system is a total mess. Can anyone help me to fix it?
Find the best deals on the web at AltaVista Shopping!
http://www.shopping.altavista.com
next reply other threads:[~2001-07-02 8:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 8:04 Av Vl [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-19 13:17 internal " Matt Sexton via gcc-help
2018-01-19 13:26 ` Mikhail Maltsev
2018-01-19 14:35 ` Matt Sexton via gcc-help
2018-01-19 15:54 ` Matt Sexton via gcc-help
2018-01-22 13:14 ` Mason
2018-01-22 13:21 ` Matt Sexton via gcc-help
2012-12-24 16:44 Internal Compiler Error tanle
2012-12-24 18:19 ` Andrew Haley
2012-12-27 17:27 ` Iyer, Balaji V
2010-07-12 9:04 internal compiler error Malte.Mauelshagen
2010-07-12 9:56 ` Ian Lance Taylor
2008-02-29 21:27 raian.ufop
2008-02-29 22:16 ` Brian Dessent
2008-03-03 18:50 ` raian.ufop
2003-07-30 20:29 Internal " DEEPA SIVASANKARANE
2001-07-03 8:36 Av Vl
1999-09-29 12:58 Guardian
1999-09-30 3:33 ` jwk
1999-09-30 23:56 ` jwk
1999-10-01 0:00 ` jwk
1999-10-01 13:49 ` Guardian
1999-10-31 13:57 ` Guardian
1999-09-30 23:56 ` Guardian
1999-10-01 0:00 ` Guardian
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=20010702150432.5189.cpmta@c012.sfo.cp.net \
--to=anvitvl@altavista.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).