www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/09/18/06:58:57

Date: Wed, 18 Sep 1996 13:39:59 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Christian Axbrink <sa9471 AT ida DOT utb DOT hb DOT se>
Cc: djgpp AT delorie DOT com
Subject: Re: What parts of DJGPP are 'pure' unix ?
In-Reply-To: <323DADCE.3699@ida.utb.hb.se>
Message-Id: <Pine.SUN.3.91.960918133416.1037E-100000@is>
Mime-Version: 1.0

On Mon, 16 Sep 1996, Christian Axbrink wrote:

> This implies either that at least some parts of the DJGPP package is
> *completely*  Unix compatible (I mean, we are not talking about any old
> application here, we are talking about the compiler, the most convoluted
> and low-level thing on any system, yes?) or unwholesomely smart and
> allknowing makefiles.
> So I wonder, wich parts are compiled from 'pure' GNU unix source code,
> and wich parts are rewritten for DOS ?  

Gcc has a way to autoconfigure itself (when you build it) to 
a version that will run on a certain machine and a certain operating 
syste.  Basically, this is done by selecting header files specific to 
that machine/OS combination.

The DJGPP-specific parts of GCC are made of 2 things:

1) The i386 code-generation
This is (almost) the same as for any other system which runs on Intel 
processors.

2) The MSDOS-specific issues (like the pathnames with drives etc.).
These are included in the official GCC sources, conitioned on cpp 
directives like #ifdef MSDOS.

This way, the MSDOS support is both specific to MSDOS and part of the 
official GCC distribution.

> Is it possible to recompile the libraries with pentium opt. ?

Just get the sources of the library and run Make.

- Raw text -


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