Before I even start, any idea if installation on Red Hat Enterprise LINUX Core 4 has been attempted? Has been successful? Can utilize the Fedora Core 4/5 items??
-Kirk
Hello,
If you can use FC4/5, I am not sure. RHEL 4 is based auf FC3. Anyway, you can give the C::B RPM package a try. The next release, RHEL 5 would be based on FC5, which should make possible to use C::B RPM package (AFAIK).
Anyway, you can try to compile the SVN sources by yourself. It is not that difficult :).
Best wishes,
Michael
The package will work, if you have a RH/FC wxGTK 2.6 package installed. But there is no package for FC3, so I don't think that there is one for RHEL 4.
You will have to compile wxGTK too, if there is no wxGTK 2.6 package available. Try to use the src.rpm from FC4 (http://stentz.freshrpms.net/rpm.html?id=473) and compile it with
rpmbuild --rebuild wxGTK-2.6.2-0.2.2.fc4.src.rpm
Perhaps you will need to solve some dependencies.
I never tested this, so I can't say whether it really works (perhaps even solving the dependencies will fail because of different package names).
Good luck ;)
Daniel
OK, we're getting there. I was able to get RC1 working - a step above my last attempt. Now on to the SVNs. I rebuilt GTK as suggested by daniel2000. That worked without any problems, so I installed the new package (2.6.2) and so far everything seems to behave itself.
The 08 May 2006 build of C::B, however, now complains about needing libstdc++.so.6:
libstdc++.so.6(GLIBCXX_3.4.4) is needed by codeblocks...
libstdc++.so.6(GLIBCXX_3.4.6) is needed by codeblocks...
Thing is, libstdc++.so.6 exists in /usr/lib as a link to libstdc++.so.6.0.3. So, it exists, but the C::B installation can't find it?? I'm using gcc 3.4.5, in case that helps.
-Kirk
Oh sorry, I forgot this :(
RHEL4 and FC3 use an older glibc. So you have to compile codeblocks yourself, too.
You can take two ways ;) :
1.) If you want to compile codeblocks and have an rpm as result take a look at Compiling Code::Blocks in RPM based distributions (http://wiki.codeblocks.org/index.php?title=Compiling_Code::Blocks_in_RPM_based_distributions)
2.) If not read Compiling Code::Blocks in Linux (applies to all distros)#Code::Blocks_installation (http://wiki.codeblocks.org/index.php?title=Compiling_Code::Blocks_in_Linux_%28applies_to_all_distros%29#Code::Blocks_installation)
gcc 3.4.5 is good, so it should work :D
Yeah, I was working on that. I took the step to get the latest SVN, so I downloaded/installed SubVersion, tested that it is working, and now when I execute
svn checkout svn://svn.berlios.de/codeblocks/trunk
I get "cannot connect to host...connection was actively refused by target machine"
I have a feeling that if I could get the source, I could get it to compile. Any ideas there??
-Kirk
Probably an issue with your firewall/router.
Quote from: mandrav on November 26, 2005, 03:17:52 PM
Indeed, the migration is finished :D
For anonymous SVN access you can use either svn checkout svn://svn.berlios.de/codeblocks/trunk (via svn protocol), or svn checkout http://svn.berlios.de/svnroot/repos/codeblocks/trunk (via HTTP).
Developers must use either svn checkout svn+ssh://developername@svn.berlios.de/svnroot/repos/codeblocks/trunk (via svn+ssh protocol), or svn checkout https://developername@svn.berlios.de/svnroot/repos/codeblocks/trunk (via HTTPS).
Try the http method.
I should have mentioned that I did indeed try that method. I get this:
svn: REPORT request failed on '/svnroot/repos/codeblocks/!svn/vcc/default'
svn: REPORT of '/svnroot/repos/codeblocks/!svn/vcc/default': 400 Bad Request (http://svn.berlios.de)
Quote from: KirkD on May 10, 2006, 08:32:20 PM
svn: REPORT request failed on '/svnroot/repos/codeblocks/!svn/vcc/default'
svn: REPORT of '/svnroot/repos/codeblocks/!svn/vcc/default': 400 Bad Request (http://svn.berlios.de)
What are these paths? These aren't ours...
Not mine either. They are what SubVersion gives me when I give the specified command.
I found this with google ;)
Quote from: http://marc2.theaimsgroup.com/?l=geronimo-user&m=113037291503818&w=2Try https instead of http.
My guess is you have a proxying firewall which is messing up the svn
stream. Since https is encrypted your firewall can't corrupt it.
Try it and let us know whether it worked :-)
Holy crap, it worked! :D
Now on to the build process.... I promise to make that a new thread. :P
Indeed it worked. I now have Code::Blocks rev 2438 running on LINUX and Windows.
Thanks for all your help and patience. Hopefully I can give something back one day.
If anyone is interested in my installation notes, I'm happy to post them.