From: "Longman, Bill" <longman@sharplabs.com>
To: "'gentoo-laptop@lists.gentoo.org'" <gentoo-laptop@lists.gentoo.org>
Subject: RE: [gentoo-laptop] problem with glibc update
Date: Wed, 3 Jan 2007 08:42:57 -0800 [thread overview]
Message-ID: <789E617C880666438EDEE30C2A3E8D1001450818@mailsrvnt05.enet.sharplabs.com> (raw)
> Hi Thanks, but I do have sys-devel/gcc version 4.1.1-r1.
>
> Does anybody know what the problem could be?
You probably have it but is it configured? What does "gcc-config -c" tell
you? You may need to turn it on. You'll need to find the gcc upgrade docs if
you go from 3.4 to 4.1.
--
gentoo-laptop@gentoo.org mailing list
next reply other threads:[~2007-01-03 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 16:42 Longman, Bill [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-03 0:55 [gentoo-laptop] problem with glibc update maillists
2007-01-03 7:28 ` Praveen C
2007-01-03 13:18 ` maillists
2007-01-03 19:08 ` Devon Miller
2007-01-03 21:47 ` maillists
2007-01-04 0:17 ` Randy Barlow
2007-01-04 0:57 ` maillists
2007-01-04 16:26 ` Devon Miller
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=789E617C880666438EDEE30C2A3E8D1001450818@mailsrvnt05.enet.sharplabs.com \
--to=longman@sharplabs.com \
--cc=gentoo-laptop@lists.gentoo.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