Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Gleb O. Raiko" <raiko@niisi.msk.ru>
To: Ulf Carlsson <ulfc@calypso.engr.sgi.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>,
	"Bradley D. LaRonde" <brad@ltc.com>,
	linux-mips <linux-mips@fnet.fr>,
	linux <linux@cthulhu.engr.sgi.com>
Subject: Re: XFree 4.0.1 on mips, mipsel
Date: Tue, 27 Jun 2000 12:01:04 +0400	[thread overview]
Message-ID: <39585F40.67B6FA74@niisi.msk.ru> (raw)
In-Reply-To: 14678.31422.353864.773880@calypso.engr.sgi.com

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

Ulf Carlsson wrote:
> 
> Ralf Baechle writes:
>  > On Sat, Jun 24, 2000 at 01:12:18PM +0200, Guido Guenther wrote:
>  >
>  > > [..snip..]
>  > > > If you cross-compile, you just redefine most of the stuff like CcCmd,
>  > > > ArCmd, etc, anyway.
>  > > Yes, but you have to make sure the redefinitions don't get redefined
>  > > again, therefore IMHO an "#ifdef AsCmd" is needed. Otherwise the
>  > > definition in hosts.def will be overriden by the one in linux.cf.
>  >
>  > Does X building ever need the hostcompiler?  If not, then you can easily
>  > do crossbuilds like:
>  >
>  >   PATH=<prefix>/<target>/bin:$PATH make ...
> 
> Yes.  You need the hostcompiler when you do X builds.  It is possible
> to get around it though.  I have the commands that I used in two shell
> scripts.
> 
> First I have to to prepare for the cross build:
> 
> #!/bin/sh
> make clean
> make Makefile.boot
> make Makefiles
> (cd config; make)
> make includes
> make depend
> (cd fonts/bdf; for i in $(find -name 'Makefile'); do sed -e 's/\$(XBUILDBINDIR)\///' < $i > $i.tmp; mv $i.tmp $i; done)
> 
> Then I'm ready to build the rest with the cross compiler:
> 
> #!/bin/sh
> export PATH=/usr/glibc-mips/bin:$PATH
> make -k CC=mips-linux-gcc LD=mips-linux-ld AS=mips-linux-as RANLIB=mips-linux-ranlib $@
> 
> You probably have a better solution though :-)

Sure, host.def attached.

[-- Attachment #2: host.def --]
[-- Type: image/x-xbitmap, Size: 2633 bytes --]

  reply	other threads:[~2000-06-27  7:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-23 16:17 XFree 4.0.1 on mips, mipsel Guido Guenther
2000-06-23 16:53 ` Bradley D. LaRonde
2000-06-23 16:53   ` Bradley D. LaRonde
2000-06-23 16:55   ` Guido Guenther
2000-06-23 17:09     ` Bradley D. LaRonde
2000-06-23 17:07       ` Guido Guenther
2000-06-23 17:46         ` Bradley D. LaRonde
2000-06-23 17:45           ` Guido Guenther
2000-06-24  9:21           ` Gleb O. Raiko
2000-06-24 11:12             ` Guido Guenther
2000-06-24 22:12               ` Ralf Baechle
2000-06-25 21:33                 ` Ulf Carlsson
2000-06-27  8:01                   ` Gleb O. Raiko [this message]
2000-06-27  7:57                 ` Gleb O. Raiko
2000-06-27  9:17                   ` Guido Guenther
2000-06-28  7:20                     ` Gleb O. Raiko
2000-06-23 17:02   ` Hiroshi Kawashima
2000-06-23 17:08     ` Bradley D. LaRonde
2000-06-23 17:08       ` Bradley D. LaRonde
2000-06-23 17:21       ` Hiroshi Kawashima
2000-07-12 19:12 ` 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=39585F40.67B6FA74@niisi.msk.ru \
    --to=raiko@niisi.msk.ru \
    --cc=brad@ltc.com \
    --cc=linux-mips@fnet.fr \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@oss.sgi.com \
    --cc=ulfc@calypso.engr.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