It took a bit of configuration modificatin and a whole lot of dependency
resolution but I finally managed to build a working version of roxterm 2.3.1
in rpm format for FC14 if anyone is interested.
http://dl.dropbox.com/u/41482403/roxterm-2.3.1-1.fc14.i386.rpm
Did you use an autoconf/make-based build or maitch? A good way to work out
which packages you need to build it is to look at the Build-Depends line in
debian/control.
* I forgot to mention that you may need to use "--nogpgcheck" with yum/rpm to install the roxterm rpm I created. Can't edit or preview posts here apparently. *
@realh: Thanks. I will remember that for next time. I likely installed a
number of packages that I didn't require just trying to get configure and make
to complete/compile without error. I've run into this dependency easter egg
hunt before trying to build debian based programs on fedora systems.
I used autoconf. I couldn't find out much about maitch from a google search or
otherwise.
This was the result from running python ./mscript.py configure:
make[0]: Entering directory "/root/rpmbuild/BUILD/roxterm-2.3.1/build" Searching for program sed... /bin/sed Searching for program git... /usr/bin/git Searching for program xsltproc... /usr/bin/xsltproc Searching for program convert... /usr/bin/convert Searching for program composite... /usr/bin/composite Searching for program xgettext... /usr/bin/xgettext Searching for program msgmerge... /usr/bin/msgmerge Searching for program msgfmt... /usr/bin/msgfmt Searching for program po4a-gettextize... not found WARNING: po4a tools not found, not building documentation's translations Checking pkg-config gtk+-3.0...ok Checking pkg-config vte-2.90...error Checking pkg-config sm ice...ok Checking pkg-config dbus-1...ok Checking pkg-config dbus-glib-1...ok Checking pkg-config gmodule-export-2.0...ok Checking for function get_current_dir_name()... no Checking for function g_mkdir_with_parents()... no Checking for function gdk_window_get_display()... no Checking for function gdk_window_get_screen()... no Checking for function gtk_widget_get_realized()... no Checking for function gtk_widget_get_mapped()... no Checking for function gtk_combo_box_text_new()... no Checking for function gtk_rc_style_unref()... no Checking for function vte_terminal_search_set_gregex()... Traceback (most recent call last): File "./mscript.py", line 186, in <module> "${CFLAGS} ${VTE_CFLAGS}", "${LIBS} ${VTE_LIBS}") File "/root/rpmbuild/BUILD/roxterm-2.3.1/maitch.py", line 890, in check_func if self.check_compile(code, "for function %s()" % func, cflags, libs): File "/root/rpmbuild/BUILD/roxterm-2.3.1/maitch.py", line 845, in check_compile (libs, cflags, tmp, tmp + ".c")).split() File "/root/rpmbuild/BUILD/roxterm-2.3.1/maitch.py", line 794, in subst return subst(self.env, s, novar, recurse, at) File "/root/rpmbuild/BUILD/roxterm-2.3.1/maitch.py", line 1954, in subst result, n = rex.subn(ms, s) File "/root/rpmbuild/BUILD/roxterm-2.3.1/maitch.py", line 1943, in ms return env[s] KeyError: 'VTE_LIBS'
I've installed pretty much everything I could find in the many repositiories I
have installed that included "vte" and "libs" and their devel packages without
success using .
In order for autoconf to work I had to create the following symlinks:
ln -s /usr/lib/rpm/config.sub /usr/share/misc/config.sub
ln -s /usr/lib/rpm/config.guess /usr/share/misc/config.guess
and alter the roxterm.spec.in in a couple places: Copyright needed to be
changed to License and rpmbuild also complained about the "~" in the version,
so I had to edit configure and configure.ac to get rid of the tilde.
I also had to copy roxterm_logo.png, favicon.ico and logo_text.png from the
2.2.2 build to ./Help/lib in the 2.3.1 directory as these files seemed to be
missing from the 2.3.1 source, and if they are supposed to be generated during
the build, that wasn't happening.
@realh: I had a look at the Build-Depends in debian/control and yum outputs
the following (with my additon of possible rpm replacements in brackets):
No package libgtk-3-dev available. (gtk3-devel and/or gtkmm30-devel)
No package libvte-2.90-dev available. (libvtemm-devel and/or libvtemm)
No package libgtk2.0-dev available. (gtk2-devel)
No package libvte-dev available. (libvtemm-devel and/or libvtemm)
No package libsm-dev available. (libSM-devel)
No package libdbus-glib-1-dev available. (dbus-glib-devel)
That really helped speed up the process of narrowing down dependencies as
opposed to running ./configure over and over until the errors are all
eliminated, thanks again!
Maitch is my own build tool, I haven't released it separately yet. It looks
like I need to check the way the script handles the case where GTK3 is present
but not the GTK3-compatible version of VTE. In Debian libvte9 (GTK2 version)
and libvte-2.90 (GTK3 version) can be installed at the same time, and so can
their respective dev packages. I'm sure something similar must be possible in
RedHat because they supported GNOME 3 very early. They might call it libvte3
instead of 2.90.
You shouldn't need any of the lib*mm packages, mm in GTK/GNOME etc libraries
usually means C++.
Maybe something to do with this OS being FC14, pre Gnome3? I'll likely do a VM
install of FC16 fairly soon and test building roxterm there.
Somehow I missed (in the above package list) the vte-devel-0.26.1 package that
is installed/available, so libvte-dev probably equals vte-devel on FC/RedHat?
Output from yum search vte
================================ Matched: vte ================================ evtest.i686 : Event device test program libvte-java.i686 : Wrapper library for GNOME VTE libvte-java-devel.i686 : Compressed Java source files for libvte-java libvtemm.i686 : C++ interface for VTE (a GTK2 terminal emulator widget) libvtemm-devel.i686 : Headers for developing programs that will use libvtemm libvtemm-docs.i686 : Documentation for libvtemm, includes full API docs ruby-vte.i686 : Ruby binding of VTE ruby-vte-devel.i686 : Development libraries and header files for ruby-vte rubygem-vte.i686 : Ruby binding of vte rubygem-vte-devel.i686 : Ruby/VTE development environment rubygem-vte-doc.i686 : Documentation for rubygem-vte vte-devel.i686 : Files needed for developing applications which use vte lxterminal.i686 : Desktop-independent VTE-based terminal emulator sakura.i686 : Terminal emulator based on GTK and VTE termit.i686 : Simple terminal emulator based on vte library vte.i686 : A terminal emulator gnome-sharp.i686 : GTK+ and GNOME bindings for Mono lilyterm.i686 : Light and easy to use X Terminal Emulator roxterm.i686 : A fast terminal emulator slashem.i686 : Super Lotsa Added Stuff Hack - Extended Magic sugar-terminal.noarch : Terminal for Sugar
I got it to successfully compile and build using maitch on FC16 with
vte3-devel (n/a in FC14) and python-lockfile, but python ./mscript.py install
copies all files to ./roxterm-2.3.1/build/usr/ as opposed to /usr.
Oddly, I had no trouble building it after resolving the dependencies using
rpmbuild on FC14 (Fusion Linux) but when attempting on FC14 and FC16 (Fedora)
it would immediately exit with: error: Package already exists: %package
debuginfo.
Adding:
%define debug_package %{nil}
to the roxterm.spec.in file fixed this issue but the subsequent attempt ended
with:
error: line 62: second %install
which is clearly commented out...strange, as the syntax appears to be fine in
vim. Removing the % character from the comment fixed it and the rpm build
succeeded.
Perhaps because Fusion is a heavily modified Fedora/RedHat based distro, the
debugging for rpm creation has been disabled somehow (looking into that
still).
A minor issue:
configure: WARNING: autoconf is deprecated for roxterm. Please use maitch instead. See INSTALL.ReadFirst
but INSTALL.ReadFirst is missing and there is no mention of maitch in the
INSTALL or REAME files.
TL;DR: I managed to build the roxterm-2.3.1 rpm package on both Fedora 14 and
16 by:
running
perl -pi -e 's/0.15~g6b2ffed/1/g'
on configure and configure.ac
modifying roxterm.spec.in in vim with
:%s/Copyright/License/g
, adding
%define debug_package %{nil}
and removing the % symbol from the comment on line 62.
I'm in the deb camp rather than rpm so I never really supported the spec file;
it just got created with the autoconf utility for setting up a project, but I
thought as it was there I'd do what I could without really understanding it.
So it's not surprising it didn't work properly. I've tried to correct the
problems you found and also to get it to work with maitch.
Do you have to edit the binary dependencies manually in spec files? The Debian
packager works out library dependencies automatically. They are:
libc6 (>= 2.3), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 0.78), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.24.0), libice6 (>= 1:1.0.0), libpango1.0-0 (>= 1.14.0), libsm6, libx11-6, librsvg2-common
and
libgtk-3-0 (>= 3.0.0), libvte-2.90-9 (>= 1:0.27.2)
or
libgtk2.0-0 (>= 2.24.0), libvte9 (>= 1:0.24.0)
python ./mscript.py install copies all files to ./roxterm-2.3.1/build/usr/
as opposed to /usr.
Did you accidentally miss off the leading slash ie use '--prefix=usr' instead
of '--prefix=/usr'? (By the way, you can use PREFIX=... instead of
--prefix=...). I forgot to include INSTALL.ReadFirst in the tarball, but the
most useful info is from
./mscript.py help
.
favicon.ico, logo_text.png and roxterm_logo.png
They should be built by make (or maitch) if imagemagick is installed. For some
reason make doesn't raise a fatal error if it can't build them.
Do you have to edit the binary dependencies manually in spec files?
I'm no expert in either coding or compiling on any level so I don't know how
to answer this. Starting from: http://fedoraproject.org/wiki/Packaging:Guidel
ines#File_Dependencies might give you the answer.
The inclusion of Copyright as opposed to License probably means this is a very
old spec file. I checked out the FC14 source rpm for roxterm-1.18.5 and the
spec file was pretty much the same, if not exact.
Did you accidentally miss off the leading slash ie use '--prefix=usr'
instead of '--prefix=/usr'?
I only used:
python ./mscript.py configure
etc. without any added prefixes.
They should be built by make (or maitch) if imagemagick is installed. For
some reason make doesn't raise a fatal error if it can't build them.
I know ImageMagick is installed but perhaps the -devel package is not. I will
check (have to reboot into FC14 OS first). It was failing to complete the
build on my end. In that case I am betting that ImageMagick-devel will fix it.
I was wrong. The images were not generated with ImageMagick-devel installed.
Log in to post a comment.