Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Pete Popov <ppopov@mvista.com>,
	"linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: userland packages
Date: Fri, 27 Oct 2000 10:14:23 -0700	[thread overview]
Message-ID: <39F9B7EF.D6469D07@mvista.com> (raw)
In-Reply-To: 20001027043432.F6628@bacchus.dhis.org

Ralf Baechle wrote:
> 
> On Thu, Oct 26, 2000 at 05:36:17PM -0700, Pete Popov wrote:
> 
> > Is there a guide on how to rebuild userland packages from source code?
> > I've installed the cross compiler and can compile a kernel, but when I
> > try to build a simple userland app, the compiler can't find libraries,
> > include files, etc.
> 
> You have to copy all the includes and libraries to
> /usr/mips-linux/{include,lib}/, then fixup linker scripts that disguise
> themselfes as .so files like libc.so and you can start.
> 
> Getting everything to crosscompile is a hard job, I really recomend
> native builds.
> 

Pete,

He is not telling the truth. :-)  See his very own MIPS-HOWTO,
cross-compile section :

http://www.linux.sgi.com/mips-howto.html

Also, you can take a look of the rpm spec files for the toolchains I put
on ftp.mvista.com/pub/Area51/mips_le/.  So far all my usrland stuff are
cross-compiled - I don't have the luxury of a desktop MIPS with 1.6GB
RAM.

Jun

  reply	other threads:[~2000-10-27 17:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-27  0:36 userland packages Pete Popov
2000-10-27  2:34 ` Ralf Baechle
2000-10-27 17:14   ` Jun Sun [this message]
2000-10-27 23:27     ` Ralf Baechle
2000-10-27 23:30       ` Pete Popov
2000-10-30 10:27       ` Maciej W. Rozycki
2000-10-30 21:41         ` 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=39F9B7EF.D6469D07@mvista.com \
    --to=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ppopov@mvista.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