www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/11/16/19:51:30

From: cdamond AT uclink2 DOT berkeley DOT edu
Newsgroups: comp.os.msdos.djgpp
Subject: cross-compiling: FROM linux TO msdos
Date: 17 Nov 1996 00:01:32 GMT
Organization: I need to put my ORGANIZATION here.
Lines: 28
Message-ID: <56lkks$gpg@agate.berkeley.edu>
NNTP-Posting-Host: beshaba.hip.berkeley.edu
Originator: lucifer AT agate DOT berkeley DOT edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

I'm trying to compile a C cross-compiler out of the gcc sources.  I want
it run with an i486-unknown-linux host and i486-unknown-msdos target, and
I'm compiling it on an i486-unknown-linux (host==server).  Thus, this is
sort of the inverse of djgpp.

So far, following the directions, I've managed to successfully compile
gcc-2.7.2.1 with i486-unknown-linux -> i486-unknown-linux, but when I try
to specify the target as msdos, it says that that configuration is not
supported, when it is specifically mentioned in the docs as a supported
target. I know I also need cross-compiled binutils eventually (the
instructions don't seem to indicate that I don't need them yet) but the
directions on building them for a cross-compiler are much worse than
gcc's.

So, a few questions for someone who's done this before (or someone smart
who hasn't):

+Why does the gcc configuration utility not acknowledge the valid target
 msdos?

+Is there an easier way to do this, since I know the processor is the same
 (and thus the assmbler code should be, shouldn't it?)

+How do you build the binutils for a cross-compiler?  Do I need to, given
 that they are intended to produce code for the same processor?

+Is there anything else besides gcc and binutils I need (special msdos
 libraries or headers for example) to set up a cross-compiler?

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019