const (char*) handling in gcc 4.2.1 versus gcc 4.0
const (char*) handling in gcc 4.2.1 versus gcc 4.0
- Subject: const (char*) handling in gcc 4.2.1 versus gcc 4.0
- From: Dieter Oberkofler <email@hidden>
- Date: Sat, 19 Sep 2009 08:03:44 +0200
| I'm getting tons of "warning: deprecated conversion from string constant to 'char*'" warnings when building with gcc 4.2.1 and (except for the fact that most of them are in 3rd party code) I pretty much like gcc to point me to some const misuse that got undetected with previous versions. It would be nice if I could disable this warning for my 3rd party code but I did not find any option for this.
Unfortunately I now seem to have hit a wall with gcc 4.2.1 when linking with a static library that was compiled with gcc 4.0 and I do not have access to the source code.
I get an error message like this: ----- Undefined symbols: "RWCString::assertElement(unsigned long) const", referenced from: RWCString::operator[](unsigned long) constin Test_I18N.o ld: symbol(s) not found -----
Compiling my code with gcc 4.0 does not show this error message. t's along shot but my best guess is hat it has something to do with deprecated conversion from string constant to 'char*'" also implicating some change in the code generation between gcc 4.0 and 4.2.1 .
Did someone experience any similar problems and maybe found a solution? Is it maybe generally not supported to link a gcc 4.2.1 compiled source base with a gcc 4.0 build static library? Any other ideas?
Thank you, -D
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden