Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: "Ralf Baechle" <ralf@oss.sgi.com>
Cc: "MIPS/Linux List \(SGI\)" <linux-mips@oss.sgi.com>
Subject: Re: Dumb Question on Cross-Development
Date: Mon, 2 Apr 2001 21:20:44 +0200	[thread overview]
Message-ID: <00fa01c0bbaa$0bd7cb60$0deca8c0@Ulysses> (raw)
In-Reply-To: 20010402151425.A8471@bacchus.dhis.org

> > I've historically done all of my MIPS/Linux development
> > native, on Indies, P-5064's, Atlas, and Malta.  But now
> > that we seem to be in a situation where the latest,
> > greatest, and most correct compilers are x86 cross-dev
> > only.
>
> There is nothing that keeps you from building those compiler as native
> compilers also.  Usually I only crosscompile kernels and do all other
> work native.

"Let them eat cake".  My Athlon is an order of magnitude
faster than my 4Kc, and several times faster than my
Algor/R5260.  It also has much more memory and a
CD-RW unit for backup, unlike my MIPS boxes.  As
MIPS/Linux becomes more an embedded platform
and less an SGI/DEC legacy platform, people are in
general not going to put up with being forced to buy
old Indy's to do their target application work!

> > I've cut over to building kernels on my Athlon box.
> > I'd like to start building apps and benchmarks (not
> > necessarily from srpm's).  Plainly, I need a set of
> > libraries (naive attempts at cross-compilation of
> > user code with the egcs 1.1.2 compiler results in
> > complaints about the missing crt1.o), and possibly
> > some variant include files.
>
> Which looks like you don't have a glibc package installed.

That's correct.  Because I have the strong suspicion that
RH 7.0 PC rpm is too stupid to put it somewhere useful, and
is far more likely to clobber my native i686 libc unless I give
it the correct incantations.   Hence my question.  And
of course, if it ends up somewhere other than /usr/lib,
presumably I need to tweak mips-linux-gcc to know
where it is.  I'm sure that's documented somewhere,
too, but it would save me several hours if someone had
a description of how to install the full cross environment
on a Linux PC.

> > Are these packaged somewhere, and is there an FAQ/HowTo on how
> > to set them up?
>
> Guess I should occasionally roll an uptodate crosscompiler package ...

If not you, someone certainly needs to.

> > This may have been handled in Ralf's HowTo, but that seems to have
> > disappeared from the web.
>
> http://oss.sgi.com/mips/mips-howto.html.  Where are you looking?

There is no visible link to it on the oss.sgi.com/mips page - then again
there's no visible link to oss.sgi.com/mips from the oss.sgi.com page,
so at least things are consistent.  ;-)  It used to be accessible from the
FAQ that used to be at oss.sgi.com/mips/faq.html, but that document
has be deleted, leaving no forwarding address.  The pointers on Brad
LaRonde's site is even older (remember linux.sgi.com?).

> It's still
> on the web and is also being distributed as part of the LDP project.
Heck,
> the HOWTO even seems to ship with a number of Intel distributions, at
least
> Conectiva 6.0 and Redhat 6.2 seem to include it, even though fairly old
> versions.

That's great.  Now, why can't there be a pointer to it on one of the
pages accessible to someone dropping into oss.sgi.com/mips?

            Regards,

            Kevin K.

WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: "MIPS/Linux List (SGI)" <linux-mips@oss.sgi.com>
Subject: Re: Dumb Question on Cross-Development
Date: Mon, 2 Apr 2001 21:20:44 +0200	[thread overview]
Message-ID: <00fa01c0bbaa$0bd7cb60$0deca8c0@Ulysses> (raw)
Message-ID: <20010402192044.PWDlPXj9rlSwuE99Ly1liwhCG2T5wreBASiZmRKbzEo@z> (raw)
In-Reply-To: 20010402151425.A8471@bacchus.dhis.org

> > I've historically done all of my MIPS/Linux development
> > native, on Indies, P-5064's, Atlas, and Malta.  But now
> > that we seem to be in a situation where the latest,
> > greatest, and most correct compilers are x86 cross-dev
> > only.
>
> There is nothing that keeps you from building those compiler as native
> compilers also.  Usually I only crosscompile kernels and do all other
> work native.

"Let them eat cake".  My Athlon is an order of magnitude
faster than my 4Kc, and several times faster than my
Algor/R5260.  It also has much more memory and a
CD-RW unit for backup, unlike my MIPS boxes.  As
MIPS/Linux becomes more an embedded platform
and less an SGI/DEC legacy platform, people are in
general not going to put up with being forced to buy
old Indy's to do their target application work!

> > I've cut over to building kernels on my Athlon box.
> > I'd like to start building apps and benchmarks (not
> > necessarily from srpm's).  Plainly, I need a set of
> > libraries (naive attempts at cross-compilation of
> > user code with the egcs 1.1.2 compiler results in
> > complaints about the missing crt1.o), and possibly
> > some variant include files.
>
> Which looks like you don't have a glibc package installed.

That's correct.  Because I have the strong suspicion that
RH 7.0 PC rpm is too stupid to put it somewhere useful, and
is far more likely to clobber my native i686 libc unless I give
it the correct incantations.   Hence my question.  And
of course, if it ends up somewhere other than /usr/lib,
presumably I need to tweak mips-linux-gcc to know
where it is.  I'm sure that's documented somewhere,
too, but it would save me several hours if someone had
a description of how to install the full cross environment
on a Linux PC.

> > Are these packaged somewhere, and is there an FAQ/HowTo on how
> > to set them up?
>
> Guess I should occasionally roll an uptodate crosscompiler package ...

If not you, someone certainly needs to.

> > This may have been handled in Ralf's HowTo, but that seems to have
> > disappeared from the web.
>
> http://oss.sgi.com/mips/mips-howto.html.  Where are you looking?

There is no visible link to it on the oss.sgi.com/mips page - then again
there's no visible link to oss.sgi.com/mips from the oss.sgi.com page,
so at least things are consistent.  ;-)  It used to be accessible from the
FAQ that used to be at oss.sgi.com/mips/faq.html, but that document
has be deleted, leaving no forwarding address.  The pointers on Brad
LaRonde's site is even older (remember linux.sgi.com?).

> It's still
> on the web and is also being distributed as part of the LDP project.
Heck,
> the HOWTO even seems to ship with a number of Intel distributions, at
least
> Conectiva 6.0 and Redhat 6.2 seem to include it, even though fairly old
> versions.

That's great.  Now, why can't there be a pointer to it on one of the
pages accessible to someone dropping into oss.sgi.com/mips?

            Regards,

            Kevin K.

  parent reply	other threads:[~2001-04-02 19:17 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02 12:24 Dumb Question on Cross-Development Kevin D. Kissell
2001-04-02 12:24 ` Kevin D. Kissell
2001-04-02 13:14 ` Ralf Baechle
2001-04-02 13:14   ` Ralf Baechle
2001-04-02 19:20   ` Kevin D. Kissell [this message]
2001-04-02 19:20     ` Kevin D. Kissell
2001-04-02 21:48     ` Florian Lohoff
2001-04-02 22:22       ` Kevin D. Kissell
2001-04-02 22:22         ` Kevin D. Kissell
2001-04-02 22:30         ` Florian Lohoff
2001-04-03  2:57           ` Joe deBlaquiere
2001-04-04 15:17             ` Jay Carlson
2001-04-04 15:17               ` Jay Carlson
2001-04-03  6:11           ` Geert Uytterhoeven
2001-04-03  9:52             ` Maciej W. Rozycki
2001-04-03  9:50           ` Maciej W. Rozycki
2001-04-03 17:34           ` Jun Sun
2001-04-04 10:02             ` Florian Lohoff
2001-04-04 10:15               ` Geert Uytterhoeven
2001-04-04 11:02                 ` Florian Lohoff
2001-04-04 12:15                 ` Maciej W. Rozycki
2001-04-04 11:22               ` Alan Cox
2001-04-04 11:22                 ` Alan Cox
2001-04-04 16:05                 ` Florian Lohoff
2001-04-04 18:06               ` Jun Sun
2001-04-04 18:45                 ` Florian Lohoff
2001-04-06  9:37           ` Wichert Akkerman
2001-04-03  9:26       ` Maciej W. Rozycki
2001-04-03 15:10         ` Ralf Baechle
2001-04-04 12:06           ` Maciej W. Rozycki
2001-04-04 12:29             ` Ralf Baechle
2001-04-04 13:39               ` Maciej W. Rozycki
2001-04-04 14:23                 ` Carsten Langgaard
2001-04-04 15:37                   ` Maciej W. Rozycki
2001-04-05 10:54                     ` Carsten Langgaard
2001-04-05 12:05                       ` Maciej W. Rozycki
2001-04-05 14:35                         ` Carsten Langgaard
2001-04-05 16:50                           ` Maciej W. Rozycki
2001-04-05 12:32                       ` Ralf Baechle
2001-04-06 15:30                         ` Maciej W. Rozycki
2001-04-07 15:29                 ` Joe deBlaquiere
2001-04-09 12:16                   ` Maciej W. Rozycki
2001-04-02 21:56     ` Thiemo Seufer
2001-04-02 23:41 ` Binutils fixed to deal with 'insmod' issue and discussion Steven J. Hill
2001-04-03  2:17   ` Thiemo Seufer
2001-04-03  8:26     ` Ralf Baechle
2001-04-03 17:27       ` Steven J. Hill
2001-04-04  5:57         ` Andreas Jaeger
2001-04-04 16:12       ` Thiemo Seufer
2001-04-03 15:46     ` Steven J. Hill
2001-04-03 16:59   ` Maciej W. Rozycki
2001-04-03 16:56     ` Steven J. Hill
2001-04-04 11:35       ` Maciej W. Rozycki

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='00fa01c0bbaa$0bd7cb60$0deca8c0@Ulysses' \
    --to=kevink@mips.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.com \
    /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