I'm happy that the problem was solved!
One of our libraries doesn't compile on gcc 4.0, but it's a good thing. We=
will need to rewrite the C++ code of this library more correctly.
Sometime a strict compilation is more borring but finally is a better thing=
---------- Forwarded message ----------
From: Athanasios Anastasiou <thanos@...>
Date: Jul 22, 2005 6:47 PM
Subject: Solution Found!!!
To: jbrandmeyer@..., cyril.bazin@..., craig@...
First of all i would like to say that i tried two or three times to
forward my message about C++ to the gumstix list and it bounced
back....Could there be a problem about it?
Secondly, i think i found what was wrong with my piece of code. g++
4.0.1 which comes with FC4 is much more strict on the way things are
written. So in my case, i should realy have declared the arguments to
the copy constructor as const and from that point on, all the functions
that deal with the object but do not change its state (all of them
functions like getbuffer, getsize, and so on) as const...Once i did that
it compiled with zero errors. And the same was true for the gumstix
compiler.... So in a way, the const qualifier is enforced in newer
version of g++ (probably in an attempt to reduce bugs??? :-) )
So, g++ 3.3.3 might just not have been so strict with the code.
All the best.
Get latest updates about Open Source Projects, Conferences and News.