Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: Kumba <kumba@gentoo.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Oddities with CVS Kernels, Memory on Indigo2
Date: Tue, 15 Apr 2003 09:50:34 +0100	[thread overview]
Message-ID: <20030415095034.A29593@ftp.linux-mips.org> (raw)
In-Reply-To: <3E9BC44B.8080708@gentoo.org>; from kumba@gentoo.org on Tue, Apr 15, 2003 at 04:35:23AM -0400

On Tue, Apr 15, 2003 at 04:35:23AM -0400, Kumba wrote:
> 	A question with the CVS Kernel.  Are there any known issues as to the 
> specific toolchain used to build it?  Currently I'm using GCC 3.2.2 + 
> Glibc 2.3.2 + Binutils 2.13.90.0.16.  I tried a CVS updateshortly after 
> testing this kernel, and it still doesn't boot, so either my timing is 
> really bad, or I'm using a toolchain with known issues.  I have noticed 
> the toolchain does not support -mcpu in .18 of binutils, and I 
> originally thought this was only going to be a GCC change in 3.3, but my 
> guess if it's the same in .18/.20, and as such I'll need to use the 
> instructions posted about a month about to use -mabi/-march?

silly question: you specified -r linux_2_4 when checkouting kernel, didn't
you? otherwise you are trying to boot 2.5.47, which has broken serial console
support.

anyway, toolchains i'm using to build 32-bit kernel:
$ mips-linux-gcc -v
Reading specs from /home/ladis/mips-tools/lib/gcc-lib/mips-linux/3.2/specs
Configured with: ../gcc-3.2/configure --prefix=/home/ladis/mips-tools --disable-shared --with-gnu-as --enable-languages=c --disable-nls --with-newlib --enable-checking=no --disable-threads --with-headers=/home/ladis/src/linux/include --target=mips-linux
Thread model: single
gcc version 3.2
$ mips-linux-ld -v
GNU ld version 2.13

64-bit kernel (egcs is patched with egcs-1.1.2.diff.gz from linux-mips.org ftp):
$ mips64-linux-gcc -v
Reading specs from /home/ladis/mips-tools/lib/gcc-lib/mips64-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
$ mips64-linux-ld -v
GNU ld version 2.13

	ladis

  reply	other threads:[~2003-04-15  8:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-13  5:13 Oddities with CVS Kernels, Memory on Indigo2 Kumba
2003-04-14 14:07 ` Ladislav Michl
2003-04-14 15:53   ` Kumba
2003-04-14 16:00     ` Marc Zyngier
2003-04-14 16:16       ` Kumba
2003-04-14 16:27         ` Marc Zyngier
2003-04-14 16:24       ` Kumba
2003-04-14 16:35         ` Ladislav Michl
2003-04-14 16:58           ` Kumba
2003-04-15  8:35   ` Kumba
2003-04-15  8:50     ` Ladislav Michl [this message]
2003-04-15  9:02       ` Kumba

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=20030415095034.A29593@ftp.linux-mips.org \
    --to=ladis@linux-mips.org \
    --cc=kumba@gentoo.org \
    --cc=linux-mips@linux-mips.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