Author Topic: [issue compiling] codeblocks_13.12-1.tar.gz [RedHat5]  (Read 12230 times)

Offline hereticus

  • Single posting newcomer
  • *
  • Posts: 6
[issue compiling] codeblocks_13.12-1.tar.gz [RedHat5]
« on: April 26, 2014, 04:32:45 pm »
Hi,

I have an issue compiling  codeblocks_13.12-1.tar.gz at Red Hat 5 platform

I use
gcc 4.7.2
gnu make 3.82

Code: [Select]
make[5]: Entering directory `/SCRATCH/aramt/codeblocks-13.12/src/src/resources/images/16x16'
make[5]: *** No rule to make target `*.png', needed by `all-am'.  Stop.
make[5]: Leaving directory `/SCRATCH/aramt/codeblocks-13.12/src/src/resources/images/16x16'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/SCRATCH/aramt/codeblocks-13.12/src/src/resources/images'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/SCRATCH/aramt/codeblocks-13.12/src/src/resources'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/SCRATCH/aramt/codeblocks-13.12/src/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/SCRATCH/aramt/codeblocks-13.12/src'
make: *** [all-recursive] Error 1

When I enter
Code: [Select]
/SCRATCH/aramt/codeblocks-13.12/src/src/resources/images/16x16and run
Code: [Select]
makeI am getting
Code: [Select]
make: *** No rule to make target `*.png', needed by `all-am'.  Stop.
Any suggestions?

Thanks

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11932
    • Travis build status
Re: [issue compiling] codeblocks_13.12-1.tar.gz [RedHat5]
« Reply #1 on: April 26, 2014, 06:04:59 pm »
Probably it is related to a not supported version of autotools or something. The 13.12 package build fine for me on a gentoo machine... If I find time I'll try it on a centos6 machine, too.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline jens

  • Administrator
  • Lives here!
  • *****
  • Posts: 7265
    • Jens' unofficial debian-repository for the Code::Blocks - IDE
Re: [issue compiling] codeblocks_13.12-1.tar.gz [RedHat5]
« Reply #2 on: April 26, 2014, 06:11:39 pm »
Builds fine on CentOS 5 with mock, so it should also build on plain CentOS/Redhat.

Offline jens

  • Administrator
  • Lives here!
  • *****
  • Posts: 7265
    • Jens' unofficial debian-repository for the Code::Blocks - IDE
Re: [issue compiling] codeblocks_13.12-1.tar.gz [RedHat5]
« Reply #3 on: April 26, 2014, 06:22:40 pm »
By the way:
is it really gcc 4.7.2 ?

Where did you get it from ?

Offline hereticus

  • Single posting newcomer
  • *
  • Posts: 6
Re: [issue compiling] codeblocks_13.12-1.tar.gz [RedHat5]
« Reply #4 on: April 27, 2014, 02:59:44 pm »
By the way:
is it really gcc 4.7.2 ?

Where did you get it from ?
I wonder what is surprising you?)
ftp://mirrors.kernel.org/gnu/gcc/gcc-4.7.2

Offline hereticus

  • Single posting newcomer
  • *
  • Posts: 6
Re: [issue compiling] codeblocks_13.12-1.tar.gz [RedHat5]
« Reply #5 on: April 27, 2014, 03:01:38 pm »
Probably it is related to a not supported version of autotools or something. The 13.12 package build fine for me on a gentoo machine... If I find time I'll try it on a centos6 machine, too.

I work in corporate environment that does not tend to have the latest tools. And sometimes very old tools are available by default. I had compile error such as
zip -u *....
with error message that -u option is not recognized. I somehow found newer version of zip binary to continue my way.

Now I will check autotools versions.

Thanks.

Offline jens

  • Administrator
  • Lives here!
  • *****
  • Posts: 7265
    • Jens' unofficial debian-repository for the Code::Blocks - IDE
Re: [issue compiling] codeblocks_13.12-1.tar.gz [RedHat5]
« Reply #6 on: April 27, 2014, 03:13:13 pm »
By the way:
is it really gcc 4.7.2 ?

Where did you get it from ?
I wonder what is surprising you?)
ftp://mirrors.kernel.org/gnu/gcc/gcc-4.7.2
I know that it is possible to compile gcc on your own.
But I wonder why you do it.
Code::Blocks compiles fine on CentOS 5 with default packages (gcc 4.1.2) if you have repoforge-repo active (wxGTK), except for the NassiShneiderman-plugin, which needs a boost version, that is not available for CentOS/RedHat 5.
Or at least was not when first building packages for my repo.
By the way, you can also use prebuild Code::Blocks packages from my repo (see signature).

Offline hereticus

  • Single posting newcomer
  • *
  • Posts: 6
Re: [issue compiling] codeblocks_13.12-1.tar.gz [RedHat5]
« Reply #7 on: April 27, 2014, 03:30:43 pm »
jens

There are corporate standards that are updated each year in the company that I work. I must follow it by default.
Corporate standards assume using specific versions of certain tools.
gcc-4.7.2 is our standard compiler at this point

There are other compilers available in our corporate repo such as 4.8.2, even 4.2 but I must use default version unless there are reasons not to use them.
« Last Edit: April 27, 2014, 03:33:41 pm by hereticus »

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11932
    • Travis build status
Re: [issue compiling] codeblocks_13.12-1.tar.gz [RedHat5]
« Reply #8 on: April 27, 2014, 04:04:04 pm »
We don't care what compiler do you use to build your software or what corporate standards you're following.

But generally C::B should be built with the native compiler for the distro. In your case this is gcc 4.1.2.
The reason is that all required libraries are often built with this compiler and so the binary compatibility is better.
Also this is the reason why major binary distros (red hat/debian) doesn't change the compiler after a major release is made until the next major release.

So either you're using gcc 4.1.2 and you don't realize it (g++ --version to check the default compiler) or either you're using some strange command (if this is the case please post it).
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline hereticus

  • Single posting newcomer
  • *
  • Posts: 6
Re: [issue compiling] codeblocks_13.12-1.tar.gz [RedHat5]
« Reply #9 on: April 28, 2014, 12:33:16 pm »
We don't care what compiler do you use to build your software or what corporate standards you're following.

But generally C::B should be built with the native compiler for the distro. In your case this is gcc 4.1.2.
The reason is that all required libraries are often built with this compiler and so the binary compatibility is better.
Also this is the reason why major binary distros (red hat/debian) doesn't change the compiler after a major release is made until the next major release.

This was helpful.
It works with RH5 native tools.
Thanks for directions!

Offline hereticus

  • Single posting newcomer
  • *
  • Posts: 6
Re: [issue compiling] codeblocks_13.12-1.tar.gz [RedHat5]
« Reply #10 on: April 28, 2014, 12:36:53 pm »
Can you also give quick directions how to compile codeblock statically without having need to have wxGTK-2.8.12/lib in the LD_LIBRARY path?
Thanks

Offline stahta01

  • Lives here!
  • ****
  • Posts: 6610
    • My Best Post
Re: [issue compiling] codeblocks_13.12-1.tar.gz [RedHat5]
« Reply #11 on: April 28, 2014, 04:15:55 pm »
Can you also give quick directions how to compile codeblock statically without having need to have wxGTK-2.8.12/lib in the LD_LIBRARY path?
Thanks

You can NOT do that (statically link to wxGTK); unless you wish to do a lot of work and NOT be able to use add/remove CB plugins.

Tim S.
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11932
    • Travis build status
Re: [issue compiling] codeblocks_13.12-1.tar.gz [RedHat5]
« Reply #12 on: April 28, 2014, 10:38:31 pm »
Just build wxGTK as static library and hope it will work, probably it won't...
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]