From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Linux-Mips <linux-mips@linux-mips.org>
Subject: Re: What toolchain for vr4181
Date: Thu, 9 Oct 2003 13:25:30 +0200 (MEST) [thread overview]
Message-ID: <Pine.GSO.4.21.0310091320000.7430-100000@waterleaf.sonytel.be> (raw)
In-Reply-To: <20031009110418.GO20846@lug-owl.de>
On Thu, 9 Oct 2003, Jan-Benedict Glaw wrote:
> On Thu, 2003-10-09 10:30:57 +0200, Geert Uytterhoeven <geert@linux-m68k.org>
> wrote in message <Pine.GSO.4.21.0310091030110.7086-100000@waterleaf.sonytel.be>:
> > On Wed, 8 Oct 2003, [iso-8859-1] Jørg Ulrich Hansen wrote:
> > >
> > > Where is a good starting point for a toolchain that will build and work?
> > > I would prefere to build it my self because at a later state I might build
> > > it under cygwin. But a prebuild does also have interest.
> >
> > At work we use plain binutils 2.13.2.1 and gcc 3.2.2, which we build ourselves
> > (host is Solaris/SPARC).
>
> Joined trees? Which configury? Unfortunately, toolchain questions are
> quite FAQs, but there doesn't really exist _that_ good HOWTOs which
> actually contain exactly helpful hints (eg. which versions and/or which
> additional patches are needed).
>
> If companies have some kind of scripts or the like they use, I'd really
> love to see them published. That'd really help all those guys out
> there:)
Binutils (binutils-2.13.2.1.tar.bz2):
configure --target=mips-linux --prefix=/wherever/you/want
Gcc (gcc-core-3.2.2.tar.bz2):
configure --target=mips-linux --prefix=/wherever/you/want --enable-languages=c --enable-shared --with-gnu-as --with-gnu-ld --with-system-zlib --enable-long-long --enable-nls --without-included-gettext
I took the development libraries and includes from Debian:
libc6-dev_2.2.5-11.2_mips.deb
libc6_2.2.5-11.2_mips.deb
zlib1g-dev_1%3a1.1.4-1_mips.deb
zlib1g_1%3a1.1.4-1_mips.deb
I wrote very simple Perl clones of dpkg and dpkg-deb with just enough
functionality to get `dpkg-cross -i' working on Solaris. I don't know whether I
can share them, though.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2003-10-09 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 16:49 What toolchain for vr4181 Jørg Ulrich Hansen
2003-10-09 8:30 ` Geert Uytterhoeven
2003-10-09 11:04 ` Jan-Benedict Glaw
2003-10-09 11:25 ` Geert Uytterhoeven [this message]
2003-12-28 20:30 ` Geert Uytterhoeven
2004-01-07 6:42 ` Jan-Benedict Glaw
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.GSO.4.21.0310091320000.7430-100000@waterleaf.sonytel.be \
--to=geert@linux-m68k.org \
--cc=jbglaw@lug-owl.de \
--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.