All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumba12345@aol.com
To: linux-mips@linux-mips.org
Subject: Re: cross-compiler for mips (r5432)
Date: Wed, 9 Apr 2003 04:30:04 EDT	[thread overview]
Message-ID: <1a4.129edea5.2bc5340c@aol.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2622 bytes --]


       Not sure if this will help any, but this configuration helped me build 
a sparc -> mips cross compiler using glibc 2.3.2, gcc 3.2.2, and binutils 
2.13.90.0.16.  Works fine so far, I've built kernels with it and had no 
issues yet.  Although, I do not claim to be an expert in the field of 
cross-compiling -- it seems to be almost an artform.

//------------------

export myARCH=mips-unknown-linux-gnu
export myHOST=sparc-unknown-linux-gnu
export myDEST=/home/crossdev/mips

binutils:
../configure --target=${myARCH} --host=${myHOST} --prefix=${myDEST} 
--enable-shared --enable-64-bit-bfd && make

gcc-bootstrap:
../configure --prefix=${myDEST} --target=${myARCH} --host=${myHOST} 
--with-newlib --without-headers --disable-shared --disable-threads 
--enable-languages=c --disable-multilib && make

glibc:
CC="${myARCH}-gcc" CFLAGS="-O2 -mips2" ../configure --prefix=${myDEST} 
--host=${myARCH} --build=${myHOST} --without-tls --without-__thread 
--enable-add-ons=linuxthreads --enable-kernel=2.4.0 --with-gd=no 
--without-cvs --disable-profile --with-headers="${myDEST}/include" && make 
-j2

gcc-full
../configure --prefix=${myDEST} --target=${myARCH} --host=${myHOST} 
--disable-multilib --enable-shared --enable-languages="c,c++,ada,f77,objc" 
--enable-nls --without-included-gettext --with-system-zlib 
--enable-threads=posix --enable-long-long --disable-checking 
--enable-cstdio=stdio --enable-clocale=generic --enable-__cxa_atexit 
--enable-version-specific-runtime-libs --with-local-prefix=${prefix}/local 
--with-libs="${myDEST}/lib" --with-headers="${myDEST}/${myARCH}/include" && 
make -j2

//------------------

--Kumba


In a message dated 4/9/2003 02:19:18 Eastern Daylight Time, 
madhavis@sasken.com writes:


> Hi
> 
> I want to install a cross-compiler for MIPS(R5432 CPU) on an i686 host.
> Since R4000 is compatible with R5432, I am using "mips3" as the target.
> binutils-2.13 and I phase compilation of gcc-3.2 happened without any
> problems. But, glibc-2.2.5 is giving many compilation problems. This is
> how I configured glibc:
> 
> configure --build=i686-linux --host=mips3el-linux --enable-add-ons
> --prefix=/usr.
> 
> Could someone guide me on this or give me some pointers for installation?
> Is the target option "mips3" the right choice for R5432?
> 
> Thank you in advance.
> 
> regards
> Madhavi.
> 
> Madhavi Suram
> Software Engineer
> Customer Delivery / Networks
> Sasken Communication Technologies Limited
> 139/25, Ring Road, Domlur
> Bangalore - 560071 India
> Email: madhavis@sasken.com
> Tel: + 91 80 5355501 Extn: 8062
> Fax: + 91 80 5351133
> URL: www.sasken.com
> 

[-- Attachment #2: Type: text/html, Size: 3086 bytes --]

             reply	other threads:[~2003-04-09 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09  8:30 Kumba12345 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-09  6:17 cross-compiler for mips (r5432) Madhavi
2003-04-09  6:17 ` Madhavi
2003-04-09 13:54 ` Ralf Baechle

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=1a4.129edea5.2bc5340c@aol.com \
    --to=kumba12345@aol.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.