X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Message-ID: <440DABF5.62C32FA1@compuserve.de>
Date: Tue, 07 Mar 2006 16:51:18 +0100
From: Florian Liebig <FlorianLiebigEMD AT compuserve DOT de>
X-Mailer: Mozilla 4.7 [de]C-CCK-MCD CSO 1.0  (Win95; I)
X-Accept-Language: de,en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: problem with compilation output
References: <44076F99 DOT 69604EE3 AT compuserve DOT de> <46u247FctkmbU2 AT news DOT dfncis DOT de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 42
NNTP-Posting-Host: 5b705d91.news.freenet.de
X-Trace: DXC=KbiJ AT 1NiigKo@ECUP[Pk7CKZSdekToV0B_T4Xk`f6M<@>aZV>XS8K_AelR`TjV<h1HLMa4I6hbbKK
X-Complaints-To: abuse AT freenet DOT de
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

moin,moin (hello) mr. broeker.
first of all, thank you for your time.

Hans-Bernhard Broeker schrieb:

> I've been meaning to ask you this before: why do you use such an
> incredibly ancient version of GCC?

because i've purchased an gnu c/c++ compiler a few years ago, a package that
came on cd. (ISBN is :
3-8266-2714-8, price was 39.80 deutsche mark :^/ ).
i've downloaded an update later, like from the pentium compiler group, that
designed a cc1.exe, gcc.exe for the pentium processor.

>
> > all the time , when trying to link my c++ compiled .o file,
>
> Similar question: why write it in C++, of all things?

That is because I want to use OOP things, like classes with its automatic
const./dest. calls. I like this.

> That one's easy: you didn't load the standard runtime library, nor did
> you supply an alternative that would allo the program to know how to
> start itself up.

Yes, indeed, didn't I allow ld / gcc to load std.RT.-lib, because I tried to
design everything that'll be needed to execute the kernel code by myself.

> > sys.cc(.text+0x47): undefined reference to `__builtin_delete'
> > sys.cc(.text+0x101): undefined reference to `__main'
> > How can I avoid __builtin_delete from being called,
> By writing C instead of C++.  By not using any objects, maybe.

That doesn't sounds good. So, there is no way round designing the kernel in
pure ansi c code, using perhaps nasty, ugly code structures to emulate
things like 'auto-cleanups' (destroying of allocated data etc.)...

> Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
> Even if all the snow were burnt, ashes would remain.