On Fri, 2003-08-22 at 21:19, Philipp Thomas wrote:
Ernesto Jardim
[22 Aug 2003 14:43:07 +0100]: On Fri, 2003-08-22 at 12:47, Radu Voicu wrote:
I don't know if it's a gcc problem, but anyway it's strange and pretty annoying - I cannot use SuSE 8.2 because of this issue :(
I'm also considering the hipotesis of changing to debian because of gcc problems ...
[First of all I corrected your quoting (below not above the text you] [quote).]
Why do people think it's always SuSE to blame? In most cases it's buggy code that the compiler complains about, even when it dies with an ICE (internal compiler error).
Your boost problems stem from the fact that you are trying to compile an older version of boost which needs a patch to accept gcc 3.3. Either fetch yourself boost 1.30.2 (it won't compile the python part because it doesn't support python 2.3) or download the boost rpm from ftp.suse.com/pub/people/pthomas/8.2.
Philipp
-- Philipp Thomas work: pthomas@suse.de private: philipp.thomas@t-link.de
Hi I think SuSE has to be blamed for this because I'm using their distribution and no one complained about lyx code (it's a quite old and mature project). The reason is that this happened allready with 8.1 and I've submitted a bug report to suse that replied thanking me but saying that they couldn't do nothing about it. So, because I'm not a technical expert and I'm starting my PhD (that's why I want a updated and robust system) I don't have much choices but changing distribution ... Regards EJ