This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Migrating C++ source from Microsoft Windows NT to SCO Unix
- To: gcc at gcc dot gnu dot org
- Subject: Migrating C++ source from Microsoft Windows NT to SCO Unix
- From: Timothy_Ko at nag dot national dot com dot au
- Date: Thu, 29 Mar 2001 11:19:49 +1000
Hi,
Recently, we downloaded and installed the current release (2.95.2) of GNU
Compiler Collection (GCC) for a SCO OpenServer 5.05 Unix machine.
I've verified some of the gcc setting by compiling a simple cpp file with
namespace std, #include <string>...
g++ -o test test.cpp
and was success.
Then I try to migrate our existing C++ source from Microsoft Windows NT to SCO
Unix which is developed from Visual C++ 6.0.
However, it comes up syntax errors.
I'm not sure that's incompatiable between Windows and Unix,
or because of I compile without using a makefile,
or gcc installation problem.
Some of the errors like:
1. NabTime.h:82: syntax error before `;'
where we declare as:
__int64 m_iTime64;
2. NabString.h:594: macro `isalnum' used without args
where we declare as:
virtual const bool NabString::isalnum() const;
3. NabString.h:44: sstream: No such file or directory
Thanks
Tim
__________________________________________________________________________
The information contained in this email communication may be confidential. You
should only read, disclose, re-transmit, copy, distribute, act in reliance on or
commercialise the information if you are authorised to do so. If you are not the
intended recipient of this email communication, please notify us immediately by
email to NABpost@nag.national.com.au or reply by email direct to the sender
and then destroy any electronic or paper copy of this message. Any views
expressed in this email communication are those of the individual sender, except
where the sender specifically states them to be the views of a member of the
National Australia Bank Group of companies. The National Australia Bank Group
of companies does not represent, warrant or guarantee that the integrity of this
communication has been maintained nor that the communication is free of errors,
virus or interference.