-----BEGIN PGP SIGNED MESSAGE-----
Hi again,
I'm gonna upload linux-1.3.5-1.3.6.diffs.gz U
¨[¼0 ?? R =
C ¨ è è Ø È
5 ÿÿÿÿÿÿÿÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
Oct 1995 19:07:06 +0100 (MET)
From: Ralf Baechle <ralf@waldorf-gmbh.de>
Message-Id: <199510041806.TAA30095@scotty.waldorf-gmbh.de>
Received: from localhost by scotty.waldorf-gmbh.de (8.6.4/WE-1.0.1)
id TAA30095; Wed, 4 Oct 1995 19:06:58 +0100
Subject: Re: DECstation testing (was DECstation status)
To: linux-mips@fnet.fr
Date: Wed, 4 Oct 1995 19:06:57 +0100 (MET)
In-Reply-To: <199510041613.KAA02954@rover.village.org> from "Warner Losh" at
Oct 4, 95 10:13:38 am
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Length: 1954
Hi,
> I've sent this out a couple of times, but to create a cross compiler
> (following the gnu rules), you basically need to do the following:
>
> 1) grab binutils. configure --target cpu-system_mfg-os. make
> then make install. May need --root or something like that
> if you don't control /usr/local
> 2) Grab the includes and libs from the target machine, place
> them in /usr/local/cpu-system_mfg-os/{lib,include}.
> 3) grab gcc. configure --target cpu-system_mfg-os. make then
> make install.
>
> To build programs for the target, then add -b cpu-system_mfg-os to
> your compilation line. With this method, you can have multiple cross
> compilers on one system.
>
> This differs slightly from the cross compilers that the MIPS Linux
> folks have produced, but it is close enough should you need to do this
> in the future.
That what the GNU people wish how their stuffs should build. They however
ignore that building a complete crossdevelopment environment only from source
makes some extra troubles. For example to build a complete GCC you need to
have an installed standard library (accutally just crt0.o for a.out). To build
the standard libraries you need to have an installed compiler for which you
need to have installed standard library (accutally just crt0.o for a.out). To
build
the standard libraries you need to have an installed compiler for which you
need to have installed standard library (accutally just crt0.o for a.out). To
build
the standard libraries you need to have an installed compiler for which you
need to have installed standard library (accutally just crt0.o for a.out). To
build
the standard libraries you need to have an installed compiler for which you
need to have installed standard library (accutally just crt0.o for a.out). To
build
the standard libraries you need to have an installed compiler for which you ...
Damnit ... I think I just got caught in a recursion ;-)
Ralf
|