>>>>> "Ronald" == Ronald Florence <[EMAIL PROTECTED]> writes:
Ronald> Andre Poenitz <[EMAIL PROTECTED]> writes:
>> > The file is big and i am am not a programmer. I did the
>> "~MathGridInset();" in > math_gridinset.h directly under the first
>> "public:"
>> >
>> > and in math_gridinset.C > under the using std::vector;
>> >
>> > MathGridInset::~MathGridInset() > {}
>>
>> While this is not wrong, it should not be needed at all.
>>
>> This somehow smells like a broken compiler...
Ronald> Apple's versions of gcc-3.1 and gcc-3.3, including the newest
Ronald> release of gcc-3.3 with MacOS-10.3, are all broken, at least
Ronald> for C++. There are numerous bugs, many of which I have
Ronald> reported to Apple, none of which they seem eager to fix. LyX
Ronald> versions after 1.3 can only be compiled with Apple's gcc-2.95.
It seems that some people at apple care about this weak symbols issue:
http://gcc.gnu.org/ml/gcc/2003-10/msg00465.html
I also found this in
http://developer.apple.com/documentation/DeveloperTools/gcc-3.3/gcc/C---Dialect-Options.html
-fno-weak
Do not use weak symbol support, even if it is provided by
the linker. By default, G++ will use weak symbols if they are
available. This option exists only for testing, and should not be
used by end-users; it will result in inferior code and has no
benefits. This option may be removed in a future release of G++.
Might it be useful?
JMarc