From: "Thomas T. Veldhouse" <veldy@veldy.net>
To: <tclark@telia.com>, <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] gcc3.2 emerge bug?
Date: Fri, 16 Aug 2002 07:09:16 -0500 [thread overview]
Message-ID: <005501c2451d$bf1f68b0$8204dca7@northamerica.corp.microsoft.com> (raw)
In-Reply-To: 200208152122.48533.tclark@telia.com
I find this one a bit hard to understand. Could you rephrase what you are
telling us and what the bug is?
Thank you,
Tom Veldhouse
----- Original Message -----
From: "Tony Clark" <tclark@telia.com>
To: <gentoo-dev@gentoo.org>
Sent: Thursday, August 15, 2002 2:22 PM
Subject: [gentoo-dev] gcc3.2 emerge bug?
I just found gcc3.2 in portage. when it went to install it told me it could
and run this "ebuild gcc-3.2.ebuild digest". That fixed the problem and it
is
building now.
tony
--
Contract ASIC and FPGA design.
_______________________________________________
gentoo-dev mailing list
gentoo-dev@gentoo.org
http://lists.gentoo.org/mailman/listinfo/gentoo-dev
prev parent reply other threads:[~2002-08-16 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 19:22 [gentoo-dev] gcc3.2 emerge bug? Tony Clark
2002-08-16 12:09 ` Thomas T. Veldhouse [this message]
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='005501c2451d$bf1f68b0$8204dca7@northamerica.corp.microsoft.com' \
--to=veldy@veldy.net \
--cc=gentoo-dev@gentoo.org \
--cc=tclark@telia.com \
/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