User forums > Help
Settings don't get saved (svn 4454)
Biplab:
--- Quote from: johne53 on September 25, 2007, 04:36:36 pm ---What is the important step you think I missed?
--- End quote ---
For most of the popular Linux distributions, the following few instructions are sufficient if you check out source from SVN.
--- Quote ---./bootstrap
./configure
make
su
make install
--- End quote ---
If you download the source tarball, you may omit the first instruction.
Personally I use Windows XP SP2 on 2 PCs and with Fedora Core 7 on one more PC. All of them has C::B installed. Apart from that I've several Linux VMs installed (Ubuntu 7.04, Ubuntu 7.10 Alpha, Fedora 7 & 8 Beta, OpenSUSE-10.3 Beta, PC-BSD-1.3, Debian Etch, PC-Linux 2007, etc) and all of them has C::B installed for testing. Why I'm writing this. Because I didn't face such problem in any of these platforms.
Several other users have also confirmed that C::B works fine with them. Still you keep on saying the following.
--- Quote from: johne53 on September 25, 2007, 04:36:36 pm ---However, each time I did an update, C::B just became more & more unreliable. Eventually, I was advised to try installing from source.
--- End quote ---
IMHO, you made a mess of your C::B installation. And you are blaming C::B again and again.
johne53:
I can only repeat that, up until a week ago, I'd only ever installed from rpm packages. I, personally, haven't done anything to my installation (apart from using it) until a week ago when I installed and re-built it from source code. Also, I've never performed an update because of having problems. I updated because I needed a new feature - but in every case, the problems were immediately apparent, directly after updating. So what can I have done to cause this??
--- Quote from: Biplab on September 25, 2007, 05:06:13 pm ---For most of the popular Linux distributions, the following few instructions are sufficient if you check out source from SVN.
--- Quote ---./bootstrap
./configure
make
su
make install
--- End quote ---
--- End quote ---
That's exactly what I did. Just for the record, I've now done a make clean and followed those same instructions again. The new executable has today's date & time but is still giving me the same erratic performance.
Immediately after re-building, I re-booted, opened a project, placed a breakpoint at a line where it should reach and pressed F8. The program launched without stopping at the breakpoint. I exited the program and hit F8 again. The same thing happened. Without doing anything I exited the program and hit F8 for a third time. This time I got the same errors that I reported in my thread about debugging problems:-
--- Quote ---Setting breakpoints
Debugger name and version: GNU gdb 6.5
No symbol table is loaded. Use the "file" command.
--- End quote ---
My guess is that either C::B has got out of step with something it depends on - or maybe some kind of config file or startup file has become corrupted. Is there a way to completely uninstall C::B including all it's config files (and preferably wxWidgets) so I can re-install them both fresh?
johne53:
Since my last post I've uninstalled (using Yast) wxWidgets, wxWidgets-devel, wxGTK and wxGTK-devel (strangely, although I've been told that wxWidgets and wxGTK are the same thing, Yast doesn't consider them to be the same).
I then re-installed all 4 using the rpm packages that I originally downloaded (versions 2.8 ).
Next I went to my C::B root folder and typed make clean - then deleted the C::B executable and checked that my desktop icon was now non-functional, just to be absolutely sure the old version had gone...!
Then I typed the following:-
./bootstrap
./configure --enable-contrib
make
sudo make install
I even found an old default.conf file and used that, in case my most recent file was corrupted.
I've now got a brand new executable (dated a few minutes ago) - but it's still got the same problems.... :(
The only thing I can think of is to follow the wiki, step-by-step. However, the wiki refers to libraries such as wxWidgets 2.6.3 which I've been told is now out-of-date. Also, I already know that at least one of its instructions (make -f Makefile.unix) wouldn't work for me when I tried it, last time.
Biplab:
Let me make a wild guess. Is it due to AppArmor (OpenSUSE comes with it)?? It works as a security layer providing security against malicious programs (I hope I'm correct). May be you've set the security level to the strictest one.
Check this possibility. Though I had OpenSUSE installed in my PC and I never faced such problems. But you know sometimes your Anti-Virus creates such nuisance on Windows. ;)
johne53:
Good suggestion. Under Windows I used to have spurious problems with things working erratically when I used to use Zone Alarm - and I eventually had to replace it. However, AppArmor is disabled for OpenSuse in my current setup.
I can't help feeling that this is an "out-of-step" problem. Does C::B have any other dependencies - or require a minimum level of certain other libraries - apart from wxGTK? So far I've just been concentrating on wxGTK but presumably there are other dependencies too? The annoying thing is that it all worked fine when I first installed C::B. These problems started to appear gradually, as & when I updated it - which again makes me think that I should have been updattng something else to keep in step.
Also I've noticed there's an option to install "wxGTK debug info" which I've never installed. Should I have installed that?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version