Trouble recompiling

Trouble recompiling

[christopher.j.regan]

Hello
   We currently have code compiled for redhat 7.3 and we are trying to upgrade to 9.0 and recompile programs in the process. Anyway the main problem is during compilation we include a file called mybastring.h which is just a modified version of bastring.h
with string locking. The problem comes with the includes that bastring.h includes. They do not seem to compile under the version of gcc that comes with redhat 9. There are all kinds of errors such as "ISO C++ forbids". This makes me think there is now a
replacement for bastring under the current version of gcc. I have tried using all kinds of different compiler switches and have tried both gcc and g++. Nothing seems to help with the problem. Any help would be appreciated. If you need more info i can do
that. Thank You for your help


Christopher Regan
Factory Applications Programmer
(845) 902-1313

"That's why i'm easy, i'm easy like sunday morning."

Re: Trouble recompiling

[Paul Ingelbrant]

Citerar christopher.j.regan@philips.com:

> Hello
>    We currently have code compiled for redhat 7.3 and we are trying to
> upgrade to 9.0 and recompile programs in the process. Anyway the main problem
> is during compilation we include a file called mybastring.h which is just a
> modified version of bastring.h
> with string locking. The problem comes with the includes that bastring.h
> includes. They do not seem to compile under the version of gcc that comes
> with redhat 9. There are all kinds of errors such as "ISO C++ forbids". This
> makes me think there is now a
> replacement for bastring under the current version of gcc. I have tried using
> all kinds of different compiler switches and have tried both gcc and g++.
> Nothing seems to help with the problem. Any help would be appreciated. If you
> need more info i can do
> that. Thank You for your help
> 
> 
> Christopher Regan
> Factory Applications Programmer
> (845) 902-1313
> 
> "That's why i'm easy, i'm easy like sunday morning."
> 
 
I believe the "ISO C++ forbids" errors are due to gcc trying to be more ISO-
complient, and later versions more so. For a quick solution downloading an 
older version of gcc would probably work...  Check the FAQ for info on 
installing multiple version of gcc on the same system (I think you need to use -
-prefix).

If you are developing, and just not recompiling old code file, I guess now is a 
good time to learn a little more of ISO-C++. ;-) 
(On the other hand, isn't the ISO-C++ complience thing ruining a good 
language?) 

/Paul

using GCC as a lint-like tool, for C++

[Eljay Love-Jensen]

Hi everyone,

Anyone else using GCC (3.3.x) as a lint-like tool?

(I'm interested in C++.  Not so interested in C code lint checking, thus the absence of C-specific flags.)

I'm using these flags:
* -ansi
* -pedantic
* -Wall
** -W
** -Wendif
** -Wcast-qual
** -Wwrite-strings
** -Wcast-align
** -Wpointer-arith
** -Wconversion
*** -Wredundant-decls
*** -Wunreachable-code
*** -Winline
*** -Wlarger-than-256

Paranoia rating
---------------------
* paranoid
** super paranoid
*** really super-duper paranoid

Anyone else doing this?  Any hints, tips, tricks, techniques?

Thanks,
--Eljay

Re: Trouble recompiling

[Liguo Song]

On Tue, 21 Oct 2003 christopher.j.regan@philips.com wrote:

> Hello
>    We currently have code compiled for redhat 7.3 and we are trying to upgrade to 9.0 and recompile programs in the process. Anyway the main problem is during compilation we include a file called mybastring.h which is just a modified version of bastring.h
> with string locking. The problem comes with the includes that bastring.h includes. They do not seem to compile under the version of gcc that comes with redhat 9. There are all kinds of errors such as "ISO C++ forbids". This makes me think there is now a
> replacement for bastring under the current version of gcc. I have tried using all kinds of different compiler switches and have tried both gcc and g++. Nothing seems to help with the problem. Any help would be appreciated. If you need more info i can do
> that. Thank You for your help
> 
> 
> Christopher Regan
> Factory Applications Programmer
> (845) 902-1313
> 
> "That's why i'm easy, i'm easy like sunday morning."
> 
> 

Some info on the version of gcc would be more helpful here than the
version of RH. :)

But here is my guess anyway. Do you have "using namespace std;" in
your code?

Good luck.


Liguo (Leo)

Re: Trouble recompiling

[christopher.j.regan]

Thank You for your response

>I believe the "ISO C++ forbids" errors are due to gcc trying to be more ISO-
>complient, and later versions more so. For a quick solution downloading an
>older version of gcc would probably work...  Check the FAQ for info on
>installing multiple version of gcc on the same system (I think you need to use -
>-prefix).

I will have to try that if i can't come up with a way to fix the problem.

I guess the main problem is that it isn't my code that is having the problem.
One of my files includes a file (straits.h) which comes with g++ (std/straits.h) that is throwing the errors
and not compiling. Thus i was wondering if when i include bastring.h, which is the file
that does the include of std/strait, if i should be using something besides bastring. I tried
just include <string> but that just goes and does an include on bastring which causes the same
problems. I have searched the entire system and there is only 1 straits.h, just wondering if bastring
is no longer compatible with the latest gcc and if i should be using something else to get locking
strings. If the file exists under the g++ tree shouldn't it be able to compile?


Christopher Regan
Factory Applications Programmer
(845) 902-1313

"That's why i'm easy, i'm easy like sunday morning."

RE: Trouble recompiling

[lrtaylor]

-----Original Message-----
From: Paul Ingelbrant [mailto:pi@otimo.se] 
 
> (On the other hand, isn't the ISO-C++ complience thing ruining a good 
> language?) 

Oh, I don't know.  I quite like it.  :-)

Lyle