Re: [Inkscape-devel] questions
Just upgraded to 3.3.2 - alas, the bug is still there. What else can be done, aside from the "magic fix"?
Well, bear in mind that a fix we don't understand isn't really a fix...
The next thing to do I guess is to dissect the compiler's output.
Oh... and where do we start?
But first, what CFLAGS/CXXFLAGS are you using?
...and where to look up these? My Makefile has some KDE_CFLAGS, NOOPT_CFLAGS etc. but no simple CFLAGS.
_________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus&pgmarket=en-ca&RU=http%3a%2...
On Tue, 2003-12-23 at 21:48, bulia byak wrote:
...and where to look up these? My Makefile has some KDE_CFLAGS, NOOPT_CFLAGS etc. but no simple CFLAGS.
I really meant what CFLAGS or CXXFLAGS you specified at ./configure time. If you don't specify, by default it is "-g -O2", I believe.
The first thing to do is see if you can reproduce the bug with optimzation turned off. To do this, do a 'make distclean' and rerun configure like this:
CXXFLAGS="-g" ./configure
If Inkscape built like this does not exhibit the bug, then we can confirm that the bug is specifically with the compiler's optimizer.
-mental
participants (2)
-
bulia byak -
MenTaLguY