From owner-freebsd-current  Tue Nov 26 04:28:46 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id EAA00915
          for current-outgoing; Tue, 26 Nov 1996 04:28:46 -0800 (PST)
Received: from jupiter.planet.co.at (jupiter.planet.co.at [193.170.249.3])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA00595
          for <freebsd-current@freebsd.org>; Tue, 26 Nov 1996 04:23:11 -0800 (PST)
Received: from safeconcept.utimaco.co.at (safeconcept.utimaco.co.at [193.170.249.226]) by jupiter.planet.co.at (8.6.12/8.6.12) with ESMTP id NAA02034 for <freebsd-current@freebsd.org>; Tue, 26 Nov 1996 13:22:12 +0100
Received: from christian (christian.utimaco.co.at [10.0.0.39]) by safeconcept.utimaco.co.at (8.6.12/8.6.12) with SMTP id NAA01558; Tue, 26 Nov 1996 13:24:05 +0100
Message-ID: <329AE112.148C@utimaco.co.at>
Date: Tue, 26 Nov 1996 13:22:42 +0100
From: "DI. Christian Gusenbauer" <Christian.Gusenbauer@utimaco.co.at>
Organization: Utimaco Safe-Concept
X-Mailer: Mozilla 2.01 (WinNT; I)
MIME-Version: 1.0
To: FreeBsd Current <freebsd-current@freebsd.org>
CC: Christian.Gusenbauer@safeconcept.utimaco.co.at
Subject: Re: Dosboot and bcc
References: <199611261028.VAA03791@godzilla.zeta.org.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Bruce Evans wrote:
> 
> >During the last weekend, I tried to get dosboot to be compiled using bcc.
> >I managed the problems with the K&R standard and am now having the next
> >problems: bcc does not support "long long"!
> 
> DOS compilers don't handle `long long' either, do they?  You'll have to
> edit some of the header files.  See the old version of dosboot :-).

:), as you know, the intention was to edit none of the standard headers ...

But I already modified bcc and now he understands "long long" but does not
generate code. The "long long" is only used to calculate the size of a structure
and I hope I modified the right place. Well, I'll see ...

bcc might also have a problem with some #define statements. Perhaps I'll use
the gcc preprocessor.

Christian.

--
Christian Gusenbauer
Christian.Gusenbauer@utimaco.co.at