Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: "Paul Garceau" Organization: New Dawn Productions To: cygwin@sourceware.cygnus.com Date: Sun, 13 Aug 2000 15:55:27 -0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: working around "more" (Was Re: what is my mistake?!!!!!) Reply-to: Paul Garceau Message-ID: <3996C4EF.1582.1AA749@localhost> In-reply-to: <200008122345.QAA09912@california.sandia.gov> References: <010a01c004b1$c57b79a0$b3644fc2@msm.com.eg> from "Mohammed Abdel'al" at "Aug 13, 2000 02:05:13 am" X-mailer: Pegasus Mail for Win32 (v3.12c) Haven't looked at the code...but if it is indeed mixed between C and C++, you may need to set all of the "C" references (syntax, headers, functions) to "extern C", leaving the C++ as they are...just a thought...not sure this is a solution. Finally, try setting your "make" compile variable (CXX?) to "c++" instead of "gcc". It is not at all unusual for assumptions to be made in such cases, considering that from a generic standpoint, gcc is supposed to automatically sense c++ code and adopt accordingly. I personally don't trust the compiler that far, so when I am compiling for a c++ app, I always find the (CXX) and (LINK) variables and set them both to "c++" or, as an alternative, "g++" when I am building c++ apps, or anything that includes c++ headers, syntax, etc. This eliminates the assumption, at least from my standpoint, that anything compiled with "gcc" will automatically compile as "g++" or "c++" when .cxx/.cpp files are sensed. Peace, Paul G. Nothing real can be threatened. Nothing unreal exists. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com