From: "Mathias W." <m.weigt@uni-bonn.de>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] Still Problems with compiling the kernel
Date: Mon, 02 Jul 2007 10:58:58 +0200 [thread overview]
Message-ID: <4688BE52.3030505@uni-bonn.de> (raw)
In-Reply-To: <4687E11E.9030501@gentoo.org>
Kumba schrieb:
> I did hit the ldscripts error, which needed a fix in binutils-config.
> But this ranlib-based one, I haven't hit in the last few times I've run
> catalyst to build newer livecds. All I can say, is use crossdev to
> completely remove all traces of cross-compilers, then follow behind it
> in /usr and remove any left overs that might be remaining (usually in
> /usr/${CHOST}/*). Then, remove all your kernel trees.
I did this and hopefully removed everything which looked like mips64.
> Remerge everything, using gcc-4.1.2 and binutils-2.17, and cross
> fingers. Make sure you're running "make vmlinux" for 64bit targets
> (IP28, IP27, IP30) or vmlinux.32 for quasi-64bit targets (IP22, IP32).
> Also make sure you have the latest crossdev too.
Now I emerged gcc-4.1.2 but then kgcc64-4.1.2 fails during compile:
rm -f include/limits.h
cp xlimits.h include/limits.h
cp /var/tmp/portage/sys-devel/kgcc64-4.1.2/work/gcc-4.1.2/gcc/unwind-generic.h include/unwind.h
chmod a+r include/limits.h
rm -f include/README
cp /var/tmp/portage/sys-devel/kgcc64-4.1.2/work/gcc-4.1.2/gcc/../fixincludes/README-fixinc include/README
chmod a+r include/README
echo timestamp > stmp-int-hdrs
make[2]: *** No rule to make target `/usr/bin/mips64-unknown-linux-gnu-as', needed by `stamp-as'. Stop.
make[2]: Leaving directory `/var/tmp/portage/sys-devel/kgcc64-4.1.2/work/build/gcc'
make[1]: *** [all-gcc] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-devel/kgcc64-4.1.2/work/build'
make: *** [all] Error 2
!!! ERROR: sys-devel/kgcc64-4.1.2 failed.
Call stack:
ebuild.sh, line 1615: Called dyn_compile
ebuild.sh, line 972: Called qa_call 'src_compile'
ebuild.sh, line 44: Called src_compile
ebuild.sh, line 1305: Called toolchain_src_compile
toolchain.eclass, line 26: Called gcc_src_compile
toolchain.eclass, line 1541: Called gcc_do_make
toolchain.eclass, line 1415: Called die
!!! emake failed with all
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/sys-devel/kgcc64-4.1.2/temp/build.log'.
----------------------------------------
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
next prev parent reply other threads:[~2007-07-02 8:59 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. [this message]
2007-07-02 14:17 ` J. Scott Kasten
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=4688BE52.3030505@uni-bonn.de \
--to=m.weigt@uni-bonn.de \
--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