From: "Mark Haney" <mhaney@ercbroadband.org>
To: <gentoo-amd64@lists.gentoo.org>
Subject: Re: [gentoo-amd64] kdelibs don't compile after upgrade to GCC4.1.1 UPDATE - AAAGH!
Date: Thu, 26 Apr 2007 18:12:48 -0400 [thread overview]
Message-ID: <463123E0.20108@ercbroadband.org> (raw)
In-Reply-To: <200704270005.37249.bo.andresen@zlin.dk>
Bo Ørsted Andresen wrote:
> On Thursday 26 April 2007 23:43:41 Mark Haney wrote:
>> Well, I gotta say my attempt to move to gcc 4.1.1 has been a total
>> disaster. KDElibs refuses to compile regardless of what I try to do,
>> even after re-reading and following the wiki page about the upgrade.
>
> What wiki? Why are you following a wiki? What you should be following is:
>
> http://www.gentoo.org/doc/en/gcc-upgrading.xml
>
Yes, this is the page I was following. I called it wiki in the generic
sense. Still doesn't change the fact that a gcc upgrade just doesn't
work for me.
--
Ita erat quando hic adveni.
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2007-04-26 22:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 19:00 [gentoo-amd64] kdelibs don't compile after upgrade to GCC 4.1.1 Mark Haney
2007-04-25 19:06 ` Hemmann, Volker Armin
2007-04-26 11:41 ` Mark Haney
2007-04-26 11:51 ` [gentoo-amd64] kdelibs don't compile after upgrade to GCC 4.1.1 UPDATE Mark Haney
2007-04-26 14:57 ` Daniel Gryniewicz
2007-04-26 21:43 ` [gentoo-amd64] kdelibs don't compile after upgrade to GCC4.1.1 UPDATE - AAAGH! Mark Haney
2007-04-26 22:05 ` Bo Ørsted Andresen
2007-04-26 22:12 ` Mark Haney [this message]
2007-04-26 22:47 ` Boyd Stephen Smith Jr.
2007-04-27 11:10 ` Mark Haney
2007-04-27 11:33 ` Hemmann, Volker Armin
2007-04-27 11:53 ` Mark Haney
2007-04-27 11:57 ` Hemmann, Volker Armin
2007-04-27 12:03 ` Mark Haney
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=463123E0.20108@ercbroadband.org \
--to=mhaney@ercbroadband.org \
--cc=gentoo-amd64@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