X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Message-ID: <491BB129.3000706@iki.fi>
Date: Thu, 13 Nov 2008 06:46:33 +0200
From: Andris Pavenis <andris DOT pavenis AT iki DOT fi>
User-Agent: Thunderbird 2.0.0.16 (X11/20080723)
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: How can I compile C++ code (write for Linux) with DJGPP?
References: <e55088bb-82f0-4be7-8dc4-22637d1e6c34 AT d42g2000prb DOT googlegroups DOT com> 	<200811111729 DOT mABHT4ZF019503 AT envy DOT delorie DOT com> <a2e6a0ee-5401-4036-95ba-f638c2501113 AT u29g2000pro DOT googlegroups DOT com>
In-Reply-To: <a2e6a0ee-5401-4036-95ba-f638c2501113@u29g2000pro.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Datnhan wrote:
> Hi,
> 
> I repeat ----------------------------
> Warnings can be ignored. ====> WARNINGS ARE NOT THE PROBLEM
> ERRORs can be found after the line filled with asterisks in the text
> below. The errors occur in gen.h and gen.c.
> ---------------------------------------- end repeat
> 
> At the bottom of this message I list ERRORS only.
> 
> I found some recent papers which used this code, but they compile this
> code on Linux/Unix. So I think the problems is in DJGPP... but I am
> not sure... I am very new to DJGPP, and I never run a Linux system. If
> you can help me solve the problem with DJGPP, i will be grateful.

I would suggest to get some recent enough book about C++ if needed
(like "C++ Programming Language, Third Edition" by Bjarne Stroustrup.

Source could be updated to correspond to C++ standard, then hopefully
many warnings will go away (use standard compliant C++ header names,
std namespace, etc).

Another problem with new GCC versions and old sources is that old GCC versions
tolerated some missing includes, but new ones does not.

Otherwise required changes can be done with not too large work, but it is
better to leave for exercise. I do not have time for that.

Additionally: Warnings often matter and reveal real code errors, that could
sometimes be difficult to notice otherwise. That is the reason why I myself am
often using GCC command line options "-Wall -Wextra -Werror" (generate much warnings,
generate even more warnings and treat them all as errors)

Andris