Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[kriko]

I'm trying to make rpms for suse 10.2, but the problem is that suse comes with wxGTK 2.6, amuleCVS requires 2.8, so I need to make wxGTK packages first. However when I try to build wxGTK I get an error about missing gtk2+ packages, which doesn't exist (I have gtk2 and devel).  So my best guess would be to pass "--disable-gtk2 --with-gtk", is it possible to do that with rpmbuild?  Currently I'm using following syntax:
rpmbuld -ta wxGTK-2.8.3.tar.gz

[skolnick]

nope, you cannot build amule CVS with GTK support, only GTK2. My best guess would be you to use the .tar.bz2 file provided in www.wxwidgets.org and build the library yourself. THen, compile aMule using that library.

Regards.

[kriko]

This is a pain, wxGTK just doesn't compile on my box. Does someone know what happened to Gerd78, he used to make amule cvs packages for suse. Can someone contact him (I did months ago via PM, but no response)? If hosting a repo is issue, there is someone that can freely provide space for suse amule packages.

[skolnick]

I have no idea about Gerd78, but if you post here your configure line, and the error you get, maybe we can help you to compile wxGTK siccessfully. It should compile, I've compiled it on some exotic configurations and it works, so suse should be no different.

Regards.

[wuischke]

I think the error lies in the spec, which is most probably written for Fedora Core. Either change the spec to reflect the suse package names or do a quick-and-dirty package using checkinstall.

[kriko]

I get this error:

Code: [Select]

kriko@linux:~/Desktop> rpmbuild -ta wxGTK-2.8.3.tar.gz
error: Failed build dependencies:
        gtk+-2.0-devel is needed by wx-gtk2-unicode-2.8.3-3.x86_64
I think wuischke is right, it might be the spec file, cause I have gtk and gtk2 installed (devel packages as well). Does any of you guys know a good site for learning stuff about .spec?

[wuischke]

Try http://www.rpm.org/RPM-HOWTO/ or look at suse/fedora package creation wiki entries.

[kriko]

Almost made it 
at the end I got:

Code: [Select]

+ /usr/lib/rpm/brp-lib64-linux
sf@suse.de: if you find problems with this script, drop me a note
gllib_glcanvas.o:     file format elf64-x86-64
/var/tmp/wx-gtk2-unicode-root/usr/lib/libwx_gtk2u_gl-2.8.a: should be in */lib64
error: Bad exit status from /var/tmp/rpm-tmp.12964 (%install)
So, should I change the variable in spec file to point at /usr/lib64 ? Should I do that only for static libs or for shared libs too?

I attached spec file to see what I'm talking about.

[skolnick]

I am not familiar with the rpmbuild command, I always build it the "hard" way: uncompress, untar, ./configure --enable-unicode --disable-debug --enable-optimize, make, make install. Have you tried this method? or are you sure there are no parameters you should give to compile 64-bit version? (it seems to me you are compiling for 64bit processor).

Regards.

[kriko]

It works  if I do it "the hard" way, this messages appears at the end of the process, so I think it is a problem with .spec file. Maybe it is because the binaries are built for x64 platform and .spec tries to install them into /usr/lib instead of /usr/lib64. And, yes I'm compiling on 64-bit platform.

[phoenix]

This is exactly the problem. The path in the spec file is probably hard coded to lib. Look for examples in other packages, shouldn't be hard to figure it out.