Author Topic: installing from SVN on RHEL3  (Read 5898 times)

pl

  • Guest
installing from SVN on RHEL3
« on: October 27, 2006, 02:19:06 am »
My C::B install on Redhat Enterprise Linux 3 has gone something like this:

 download various recent C::B development RPMs
 fail to install above RPMs
 install SVN
  install NEON for SVN
  install HTTPD for SVN
 svn get C::B source
 read build instructions in source
 download, build, install autoconf
 download, build, install automake
 download, build, install libtool
 hack C::B bootstrap file which fails to detect modern versions of above utilities
 locate alternate install instructions on C::B wiki
 get wxGTK source and patch
 apply wxGTK patch
 attempt to build wxGTK
 give up due to meaningless error messages

That's a lot of wasted effort. Is there any chance you could release an RPM of a recent development version which might actually install on RHEL3?

Offline Game_Ender

  • Lives here!
  • ****
  • Posts: 551
Re: installing from SVN on RHEL3
« Reply #1 on: October 27, 2006, 04:42:52 am »
Does RHEL3 have recent versions of any of the needed libraries?  If not why not try Cent0S or Fedora Core and make your life easier? the reason I could think to stick with it is if you still have support but I would assume Red Hat would want to upgrade.

Offline afb

  • Developer
  • Lives here!
  • *****
  • Posts: 884
Re: installing from SVN on RHEL3
« Reply #2 on: October 27, 2006, 11:03:10 am »
I think installing from SRPMS should work OK in CentOS 3 and CentOS 4 ?
wiki: Installing_Code::Blocks_from_source_on_RPM_based_distributions

But subversion, autoconf, automake, libtool and wxGTK should be available.
If they don't come with the OS, they're also available from RPMforge.net...

I'll give it a try in the virtualization sandbox later, and note the exact steps.
« Last Edit: October 27, 2006, 11:05:03 am by afb »

pl

  • Guest
Re: installing from SVN on RHEL3
« Reply #3 on: October 28, 2006, 02:06:35 am »
I'm stuck on RHEL3. RPMForge doesn't appear to have a recent version of wxGTK for RHEL3, either.

Offline afb

  • Developer
  • Lives here!
  • *****
  • Posts: 884
Re: installing from SVN on RHEL3
« Reply #4 on: October 28, 2006, 10:01:39 am »
DarwinPorts doesn't have a recent wxGTK either, so I built one...

Guess we would have to do the same for CentOS 3 (= RHEL 3) ?
Can either use the Fedora version, or the wxWidgets spec files ?

Will update the wiki later, when I update it for Mac OS X / Fedora:
Installing_Code::Blocks_from_source_on_RPM_based_distributions
« Last Edit: October 28, 2006, 05:38:06 pm by afb »

Offline afb

  • Developer
  • Lives here!
  • *****
  • Posts: 884
Re: installing from SVN on RHEL3
« Reply #5 on: October 29, 2006, 10:11:43 am »
I've reported a number of issues that affected RPM building on CentOS 3 / 4,
"make dist" failed and missed files, compiler was older and bootstrap issues...

However, all of these have been fixed now and with the proper patches/specs
Code::Blocks builds and installs OK on the Enterprise Linux OS (CentOS/RHEL).

Will post final instructions and RPMS, once Mac OS X packages are completed.

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: installing from SVN on RHEL3
« Reply #6 on: October 29, 2006, 01:41:50 pm »
I was going to say: "hey, make your life a happier one and don't do all this compilation terror, Subversion and recent wxGTK have been part of the standard distro forever and a day", but then I looked at the package list, and they really were added only in RH Enterprise 4  :(

Isn't there a way to trick rpm/yum/whatever-you-use to download and install from a RH 4 or FC 4 (or newer) repository? That will probably bear a ton of missing dependencies, but RPM should make sure it installs those too, shouldn't it?

Without Subversion and wxGTK 2.6, I am afraid to say you will not be able to build Code::Blocks.

Well... you *can* do without Subversion, if you download the sources on another machine (which has svn) and copy a tarball to your target machine, but you'll have to edit the build script to omit autorevision, and you will have to create the file sdk/autorevision.h by hand, it should look something like this:
Code
/*3151*/
#ifndef AUTOREVISION_H
#define AUTOREVISION_H
#include <wx/string.h>
#define SVN_REVISION "3151"
#define SVN_DATE     "2006-10-28 00:02:25"

namespace autorevision
{
const unsigned int svn_revision = 3151;
const wxString svnRevision(_T("3151"));
}
#endif
[/size]
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline afb

  • Developer
  • Lives here!
  • *****
  • Posts: 884
Re: installing from SVN on RHEL3
« Reply #7 on: October 29, 2006, 01:58:46 pm »
Without Subversion and wxGTK 2.6, I am afraid to say you will not be able to build Code::Blocks.

The wiki instructions involves compiling RPM packages for wxGTK 2.6.3pl2 and Subversion 1.4.0.

So CentOS 3 works fine. Red Hat Linux or CentOS 2.1 however, that might be a bit too archaic :-)
« Last Edit: October 29, 2006, 02:00:39 pm by afb »

Offline afb

  • Developer
  • Lives here!
  • *****
  • Posts: 884
Re: installing from SVN on RHEL3
« Reply #8 on: October 29, 2006, 02:31:32 pm »
Isn't there a way to trick rpm/yum/whatever-you-use to download and install from a RH 4 or FC 4 (or newer) repository? That will probably bear a ton of missing dependencies, but RPM should make sure it installs those too, shouldn't it?

To minimize dependencies from another distribution, it is easier to build wxWidgets and Subversion with the "vendor" minimal specfiles that build packages with (mostly) implicit dependencies.

But I think we should still prefer using RPM packages, rather than compiling from source ? i.e. either compile everything from source code directly, or we build binary packages from source packages.

I do the same approach on Mac OS X, either I compile everything from source code *or* I use the DarwinPorts/MacPorts packages. I prefer to not mix the two approaches (and I am not using Fink)