User forums > General (but related to Code::Blocks)
Compile Code::Blocks from SVN under ubuntu (for newbie): experience feed back
Folco:
I fully agree with Jens. I do not recommend the procedure of the first post. I usually install or upgrade with this method and all works fine. All the packages I use are official (wxWidgets, Subversion), and are part of Ubuntu repositories.
I recommand to add "gdb" in the apt-get line provided by Jens.
(except that I have to add "/usr/local/lib" in /etc/ls.so.conf, then running ldconfig)
BentFX:
I just spent several hours fighting with a new codeblocks build.
Build commands...
--- Code: ---./configure --with-contrib-plugins=all
make
sudo make install
--- End code ---
Build finishes without error. I'm unable to tell if there were any meaningful warnings.
Running codeblocks fails with...
--- Code: ---codeblocks: symbol lookup error: codeblocks: undefined symbol: _ZTI17wxScrollingDialog
--- End code ---
I can run from the script at codeblocks-10.05/src/src/codeblocks or codeblocks-10.05/src/src/.libs/lt-codeblocks, with these errors in the startup log.
--- Code: ---<snip>
Scanning for plugins in /usr/local/lib/codeblocks/plugins
/usr/local/lib/codeblocks/plugins/libwxsmithcontribitems.so: not loaded (missing symbols?)
/usr/local/lib/codeblocks/plugins/libwxSmithAui.so: not loaded (missing symbols?)
/usr/local/lib/codeblocks/plugins/libwxsmith.so: not loaded (missing symbols?)
Loaded 35 plugins
</snip>
--- End code ---
After much googling and struggling I realized it was not finding libraries which did exist in /usr/local/lib...
Had to run
--- Code: ---sudo ldconfig
--- End code ---
It sorted all issues, and I'm up and running 10.05.
It should be part of the build instructions, or better be run by "make install."
All it does is tell the system to reexamine and cache the current list of installed libraries. It is not a destructive command, and it doesn't "relink" anything.
EDIT:
System info...
Ubuntu 10.04 amd64
wxWidgets 2.8.10(distro) & 2.9.2(built) linked to 2.8.10(after build errors :) )
oBFusCATed:
--- Quote from: BentFX on September 25, 2011, 02:40:29 pm ---Had to run
--- Code: ---sudo ldconfig
--- End code ---
It sorted all issues, and I'm up and running 10.05.
It should be part of the build instructions, or better be run by "make install."
All it does is tell the system to reexamine and cache the current list of installed libraries. It is not a destructive command, and it doesn't "relink" anything.
--- End quote ---
And why would you need to do it?
On an ages old Centos 5.6 I do not have to run it.
p.s. Have you tried to use the Jens nightlies repo? If you don't have to patch C::B with your patches, this is far more easier.
p.p.s. Keep in mind that what you're doing is wrong. On modern distros "make install" must be called only by the package manager/generator!
BentFX:
--- Quote ---And why would you need to do it?
--- End quote ---
Quite simply, because it solved the problem with the libraries not being found.
--- Quote ---On an ages old Centos 5.6 I do not have to run it.
--- End quote ---
That's all well and good. Two questions come to mind. If you do run it, does it break anything? Does the system even use ldconfig to catalog the installed libraries?
--- Quote ---p.s. Have you tried to use the Jens nightlies repo? If you don't have to patch C::B with your patches, this is far more easier.
--- End quote ---
Doesn't matter now, does it? Did I say I was angry about the difficulties. I like to build from source. And generally don't enjoy nightlys. Like I said I'm up and running, and it was only after running ldconfig.
--- Quote ---p.p.s. Keep in mind that what you're doing is wrong. On modern distros "make install" must be called only by the package manager/generator!
--- End quote ---
I don't understand??? "make install" is part of the published build instructions??? I guess it makes sense if you hold your head just right... On my box I am the "package manager", so I run "make install" when I build a program from source.
oBFusCATed:
--- Quote from: BentFX on September 25, 2011, 03:40:56 pm ---I like to build from source. And generally don't enjoy nightlys. Like I said I'm up and running, and it was only after running ldconfig.
--- End quote ---
Then why are you building from SVN sources ?
Or using a binary distro? If you like to build source packages install a source based distro like Gentoo :)
--- Quote from: BentFX on September 25, 2011, 03:40:56 pm ---I don't understand??? "make install" is part of the published build instructions??? I guess it makes sense if you hold your head just right... On my box I am the "package manager", so I run "make install" when I build a program from source.
--- End quote ---
Because:
1. "make uninstall" is quite unreliable
2. Have you seen that we ship both debian and redhat build system files?
3. It is easier to maintain in the long run.
4. The main package manager will manage the dependencies for C::B correctly.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version