X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: problem with compilation output Date: 4 Mar 2006 17:46:47 GMT Lines: 29 Message-ID: <46u247FctkmbU2@news.dfncis.de> References: <44076F99 DOT 69604EE3 AT compuserve DOT de> X-Trace: news.dfncis.de oUbJUNYSZoMAGPi1JgRruQnLYnROgeGYWDxvUWtNTI0HwVOMXvV5qlg+I8 X-Orig-Path: not-for-mail To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Florian Liebig wrote: > hi guys. i'm trying to compile a small kernel in gcc c++ 2.7.2. I've been meaning to ask you this before: why do you use such an incredibly ancient version of GCC? > all the time , when trying to link my c++ compiled .o file, Similar question: why write it in C++, of all things? > C:\GNU>gcc -Wall -O -fstrength-reduce -fomit-frame-pointer sys.cpp > -nostdlib > c:/gnu/bin\ld.exe: warning: cannot find entry symbol start; defaulting > to 000010a8 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. > 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. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.