delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mailnull set sender to djgpp-bounces using -f |
From: | "deckerben" <deckerben AT freenet DOT de> |
Newsgroups: | comp.os.msdos.djgpp |
References: | <3ca78d87$0$364$9b622d9e AT news DOT freenet DOT de> <a8eoih$m9u$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <3cab2f26$0$152$9b622d9e AT news DOT freenet DOT de> <Pine DOT GSO DOT 4 DOT 44 DOT 0204040850130 DOT 10680-100000 AT mozart DOT orchestra DOT cse DOT unsw DOT EDU DOT AU> <3cace922$0$12701$9b622d9e AT news DOT freenet DOT de> <3CAD6C24 DOT 495D4F57 AT phekda DOT freeserve DOT co DOT uk> <3cb2d8a3$0$28200$9b622d9e AT news DOT freenet DOT de> <a8umnd$ob7$2 AT antares DOT lu DOT erisoft DOT se> <3cb348ac$0$12731$9b622d9e AT news DOT freenet DOT de> <1018390249 DOT 788433 AT queeg DOT ludd DOT luth DOT se> <3cb37fd8$0$4034$9b622d9e AT news DOT freenet DOT de> <a90r0t$jsc$1 AT antares DOT lu DOT erisoft DOT se> |
Subject: | Re: making dxe2gen with clio.rice.edu binaries -or- "undefined reference to 'operator'"? |
Date: | Wed, 10 Apr 2002 13:46:32 +0200 |
X-Priority: | 3 |
X-MSMail-Priority: | Normal |
X-Newsreader: | Microsoft Outlook Express 6.00.2600.0000 |
X-MimeOLE: | Produced By Microsoft MimeOLE V6.00.2600.0000 |
Lines: | 33 |
Message-ID: | <3cb4234e$0$345$9b622d9e@news.freenet.de> |
NNTP-Posting-Host: | 213.6.64.162 |
X-Trace: | 1018438478 news.freenet.de 345 213.6.64.162 |
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 |
> Richard Dawe wrote: > : "gcc knows it should link in the standard C++ library, because it knows its > : C++ from the file extension" > > MartinS wrote: > gcc don't know that (unless that has changed). gpp and gxx should know > that. So, my original question was: > I was hoping for a way that DJGPP could see the difference and adapt itself > 'on-the-fly' as they say. > Some compilers know, for instance, that they should automaticly try a full > C++ convention with source files that have the .cpp file extension, and an > ANSI C convention when they end with .c The answer is: It can't. > I think there's a confusion between compilation and linking. `gcc' knows > friom the file-name extension it's a C++ program, so it compiles it as > such; but it does _not_ instruct the linker to scan the C++ libraries. > `gpp' does the latter. Nothing like a half-job. Thanks, I found out what I wanted to know, anyhow. Ben
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |