From: "J. Scott Kasten" <jscottkasten@yahoo.com>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] Still Problems with compiling the kernel
Date: Mon, 2 Jul 2007 10:17:07 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707021013440.6982@bluefang.tetracon-eng.net> (raw)
In-Reply-To: <4688BE52.3030505@uni-bonn.de>
Ouch! When I do ebuilds, I allways use the -b to make binary packages for
quick reinstall or duplication on another machine. Perhaps you would like
some of my packages related to base and compiler???
-Scott-
On Mon, 2 Jul 2007, Mathias W. wrote:
> Now I'm not sure if this may be in relation to the cleaning because I had
> kgcc64-4.1.1 before.
> (I'm pretty sure that I did too much cleaning because kgcc64-4.1.1 shows the
> same error now)
>
> I think I rebuild this machine from Scratch: is there a newer stage3
> available than this: stage3-mips4-2006.0.tar.bz2 ?
>
> --
> Mathias Weigt
>
>
>
> --
> gentoo-mips@gentoo.org mailing list
>
>
>
--
gentoo-mips@gentoo.org mailing list
prev parent reply other threads:[~2007-07-02 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 8:11 [gentoo-mips] Still Problems with compiling the kernel Mathias W.
2007-07-01 17:15 ` Kumba
2007-07-02 8:58 ` Mathias W.
2007-07-02 14:17 ` J. Scott Kasten [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=Pine.LNX.4.64.0707021013440.6982@bluefang.tetracon-eng.net \
--to=jscottkasten@yahoo.com \
--cc=gentoo-mips@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