From: Ralf Baechle <ralf@oss.sgi.com>
To: "J. Scott Kasten" <jsk@tetracon-eng.net>
Cc: Keith M Wesolowski <wesolows@foobazco.org>, linux-mips@oss.sgi.com
Subject: Re: Simple Linux/MIPS 0.2b
Date: Fri, 14 Jul 2000 00:51:55 +0200 [thread overview]
Message-ID: <20000714005155.C8972@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.SGI.4.10.10007131037590.20247-100000@thor.tetracon-eng.net>; from jsk@tetracon-eng.net on Thu, Jul 13, 2000 at 10:58:48AM -0300
On Thu, Jul 13, 2000 at 10:58:48AM -0300, J. Scott Kasten wrote:
> distro and drop them in place, everything seems happy and works fine.
> Thus, there's something funky about the so's I'm building myself.
>
> I've tried building the XFree 4.0.1 libraries, Lesstiff libraries, and
> libraries from our own code base. All breaks the same way.
>
> #1 What form of black magic are you guys using to do this?
Holy Penguin Pee (TM). Available at www.antarctica.com.br ;-)
> #2 Are there specific compiler flags/phases that should/shouldn't be used
> with MIPS arch so's that are different than what I'd normally do under
> Linux?
No compiler flags needed.
> #3 Should I be trying to cross compile the so's them selves instead of
> native builds?
That should make no difference in the resulting binaries if you use the
same versions of everything.
> #4 Are you using different flavors of gcc/binutils to do different jobs
> because of known breakages?
We have various known problems with the various binutils version around.
We're working on getting a current snapshot of binutils working
properly but right now we still have various problems, therefore
egcs 1.0.3a + binutils 2.8.1 is still the recommended version.
Ralf
next prev parent reply other threads:[~2000-07-13 22:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-13 7:16 Simple Linux/MIPS 0.2b Keith M Wesolowski
2000-07-13 13:58 ` J. Scott Kasten
2000-07-13 22:51 ` Ralf Baechle [this message]
2000-07-13 22:39 ` J. Scott Kasten
2000-07-19 14:04 ` Maciej W. Rozycki
2000-07-19 14:19 ` Hiroshi Kawashima
2000-07-20 18:09 ` Maciej W. Rozycki
2000-07-19 14:54 ` J. Scott Kasten
2000-07-19 16:28 ` Andy Isaacson
2000-07-19 17:13 ` Keith M Wesolowski
2000-07-19 17:42 ` J. Scott Kasten
2000-07-19 22:56 ` J. Scott Kasten
2000-07-20 1:39 ` Keith M Wesolowski
2000-07-20 1:19 ` J. Scott Kasten
2000-07-20 1:51 ` Keith M Wesolowski
2000-07-20 1:43 ` J. Scott Kasten
2000-07-26 15:53 ` big endian Debian root image Chris Ruvolo
2000-07-26 17:10 ` J. Scott Kasten
2000-07-20 12:27 ` Simple Linux/MIPS 0.2b Ralf Baechle
2000-07-20 18:57 ` Maciej W. Rozycki
2000-07-21 10:21 ` Maciej W. Rozycki
2000-07-13 23:30 ` Keith M Wesolowski
2000-07-13 22:59 ` 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=20000714005155.C8972@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=jsk@tetracon-eng.net \
--cc=linux-mips@oss.sgi.com \
--cc=wesolows@foobazco.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