RPM Spec file is ready

[TheTuxKeeper]

I got the same problem (suse 10) as baboo, then tried out your new method Daniel, but I get errors :
configure.in:61: error: possibly undefined macro: AM_OPTIONS_WXCONFIG
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:62: error: possibly undefined macro: AM_PATH_WXCONFIG
error: Bad exit status from /var/tmp/rpm-tmp.933 (%build)

Which of baboo's errors ?
The first one, the bad magic error, or the second one with wxUSleep ?

The second one shouldn't happen because Suse 10 has wxGTK 2.6.1 and this error should be eleminated with wxGTK >= 2.6.0 .

Your error can be a not installed wxGTK-devel package or a bad installation of the same package.

[baboo]

THANK YOU
Finnally, finnally!
It's done using daniel's method, the "s" and not the "S". Thank you man... Now I will have a peacefull weekend, I wish u have a nice one too.
Bye bye!

[killerbot]

I got the user daniel does not exist stuff, and also I got the wxUsleep problem.
Even on Suse 10 !!


Lieven

[TheTuxKeeper]

The daniel does not exist stuff is no problem, it's normal when the source RPM is created as normal user and not as root.

Do you have installed the Suse wxGTK-devel package?

Or is it a selfcompiled one?

[killerbot]

certainly not self compiled, will check if installed, and if not, install it

[killerbot]

installed wxGTK-devel and could cretate the rpm .. yeah

[kisoft]

I got the same problem (suse 10) as baboo, then tried out your new method Daniel, but I get errors :
configure.in:61: error: possibly undefined macro: AM_OPTIONS_WXCONFIG

I compile C::B on my Linux SuSE 10 tomorow. I read a read.me file. But I found some troubles.
I solve my troubles. I do:

 - I download rpm by Daniel2000
 - I install rpm and found src.tgz file
 - I install C::B into ~/devel
 - on execute ./bootstrap, I see errors (see above)
 - I correct my ACLOCAL_FLAGS evnironment variable:
   export ACLOCAL_FLAGS="-I /usr/share/aclocal -I /usr/share/aclocal-1.9 --acdir=`wx-config --cflags` $ACLOCAL_FLAGS"
 - ./bootstrap executed wih no problem

-I /usr/share/aclocal
-I /usr/share/aclocal-1.9

this directories content macros AM_CONDITIONAL & similar macros.

I have low experience with Linux SuSE.
May be guru correct my method.
But this method is work on my SuSE 10.0.

PS export line I wrote by memory, may be some errors

SuSE 10.0
wxGTK+ 2.6.2 (downloaded from wxWidgets site, compiled with no problem)
C::B from Daniel2000 rpm for SuSE 10.0

[Davidlee62]

It the same error like here: http://forums.codeblocks.org/index.php/topic,1146.0.html

To fix it do these steps as root:


1. Extract the sources and the specfile

Code

rpm -i codeblocks-1.0-rc2.src.rpm

2. move (not only copy) the sources ( /usr/src/packages/SOURCES/codeblocks-1.0rc2.tgz ) to another place, perhaps to the home directory
3. go to the home directory and extract the sources with

Code

tar -xzf codeblocks-1.0rc2.tgz

4. go in the directory codeblocks-1.0rc2/src/sdk of the extracted sources
5. edit in the lines 253 and 268 of cbthreadpool.cpp "wxUSleep" to "wxUsleep" ( uppercase 'S' to lowercase 's')
6. go back to the home directory
7. create a new archive in the directory where the old ones were with

Code

tar -czf /usr/src/packages/SOURCES/codeblocks-1.0rc2.tgz codeblocks-1.0rc2

8. build the rpm by using the specfile:

Code

rpmbuild -bb /usr/src/packages/SPECS/codeblocks-rc2.spec

9. when everything goes right the binary RPM should be in one of the subdirectories of /usr/src/packages/RPMS (normally i586 or i686)

Puh, I hope that works and I've no typo

Daniel

Hi Danel,

I am using FC4 and working in KDE , I'd like to know if the codeblock can work  as your prompt to compile the RPM package ? Thanks.

David

[TheTuxKeeper]

Hi Danel,

I am using FC4 and working in KDE , I'd like to know if the codeblock can work as your prompt to compile the RPM package ? Thanks.

David

You want to know whether you can use an already compiled Codeblocks during the RPM building process? (Did I get this right ? I'm just too stupid to be sure that I got the right sense :oops: )

If that was your question: you only can't use codeblocks during the installation of the binary RPM, the other steps don't change anything on your system.

Daniel