Arm Packaging Release 0.3

Finding a package to build hasn’t been easy these last couple of weeks. Mostly due to the fact that a majority of the failed packages rely on a handful of difficult packages. Packages such as: lucene, octave, ecj … Just to name a few. Although there has been little progress in the failed package building department this last week, I thought I’d make sort of a list of commands used throughout the semester I personally used to help me build packages for ARM.

Command                     |                  Short Description
—————————————————————-
yum info package -           displays information regarding a certain package.

yum provides file -           displays what package will provide that specific file

yumdownloader –source [package]” – downloads the src.rpm(source) of a specific package.

rpmdev-setuptree -                     sets up the the directory structure to build RPMs.

rpmdev-wipetree  -                      removes all the files from the rpmbuild directory structure.

yum groupinstall “Fedora Packager”-              Ensures you have the proper utilitys to build packages installed on your system(rpmlint,yum).

rpm -i package.src.rpm -                installs the package(I would usually use this in the SRPMS directory in rpmbuild structure. Produces files which include the spec of the package also).

mock -r package.src.rpm -    Does a mock build of the src.rpm package using the version of fedora that your system is. (Used for testing purposes)

rpmdev-bumpspec  -                Used to bump a version of a spec file after updating it.

koji –latest-pkg –dist13 package.src.rpm-    Searches the koji database for the latest version of the package being asked for(can also specify for which Fedora distribution).

arm-koji –latest-pkg –dist13 package.src.rpm – Same as the previous command. Instead it shows the latest version of a specific packages, but from the ARM Koji database.

arm-koji build dist-f13 –scratch package.fc13.src.rpm –  Makes a scratch build of a package for the ARM architecture. You are able to specify which distribution you wish to target.

rpmbuild -bs file.spec  — Builds a package.src.rpm from a spec file file.

Additional Info:
http://zenit.senecac.on.ca/wiki/index.php/Fedora-ARM_Package_Building_and_Troubleshooting
http://zenit.senecac.on.ca/wiki/index.php/Fedora_ARM_Secondary_Architecture

Packaging Globus for arm

I’ve been looking through the hundreds  of failed packages for arm. A lot of them are dependent on other packages that are very difficult to build and require someone with a little more expertise then I have to look at them(see my last post). Eg: OpenSceneGraph, libvirt. So, I’ve moved on from those particular packages in search of something I can actually build…

While going through the failed packages in alphabetical order, I stumbled upon a number of failed packages that are related to “globus”.
Globus–>The Globus Toolkit is a set of libraries and tools used as building blocks for grid computing applications. The toolkit is developed and maintained by the Globus Alliance.

I noticed that a lot of the globus packages were failing due to missing a dependency package:   globus-xio-gsi-driver-devel

 

 

 

Why not? lets try building globus-xio-gsi-driver-devel.

 

Success.

Release 0.2

By now the process of building packages is pretty much second nature to me. The hard part lately has been finding the best way to get some of these difficult packages built or thinking about whether I should build them at all.
Some of these failed packages might not be necessary in an arm machine. Also, sometimes having to carefully exclude certain parts of a spec file, in order to get the package to build without breaking it. There has been a handful of packages that I’ve been looking at:

The flightGear: packages require the OpenSceneGraph package to be built first.
I’ve been looking into building the OpenSceneGraph package. which I explain further down..

OpenSceneGraph is an OpenSource, cross platform graphics toolkit for the
development of high performance graphics applications such as flight
simulators, games, virtual reality and scientific visualization.

Since building OpenSceneGraph for  the arm arch has been no easy task, I’ve been taking on other packages in order to have something else to look at.

So, i’ve started looking into the libvirt package which also has difficulties building.
libvirt is a virtualization management framework and toolkit.
libvirt seems to heavily rely on the qemu package as its dependancy, but im seeking advice on IRC and in person on how I should work around these dependencies.

Packages I am working on:

globus-xio-gsi-driver-0.6-5.fc13.src.rpm, armv5tel

Never attempted–Needed for: globus-gridftp-server-control & globus-io-6.3-4.fc13.src.rpm

ANDREW

FlightGear-Atlas-0.4.0-0.5.cvs20100226.fc13,armv5tel	mock exited with status 10.– needs dependencies(SimGear-devel, OpenSceneGraph-devel)	ANDREW — https://fedorahosted.org/arm/ticket/28
FlightGear-2.0.0-1.fc13.src.rpm,armv5tel	mock exited with status 10.– needs dependencies(SimGear-devel, OpenSceneGraph-devel)	ANDREW — https://fedorahosted.org/arm/ticket/26#preview
OpenSceneGraph-2.8.2-6.fc13.src.rpm,armv5tel	c++: Internal error	ANDREW — https://fedorahosted.org/arm/ticket/32
libvirt-0.8.2-1.fc13.src.rpm	REQUIRES: qemu-img, numactl-devel	ANDREW — https://fedorahosted.org/arm/ticket/33

Arm Packaging Glom

Now that the libgda and libgdamm packages have been successfully built, it opens up the doors for other packages to be built…
Glom-1.14.4-1.fc13.armv5tel package for example has yet to be built for arm because it required libgdamm to be built first.
So I performed the arm-koji build command on glom, here were the results:

glom –> Success.
I’ve also been trying to build some other packages on this nice quiet Sunday afternoon, lets see how it goes…

Arm Packaging Release 0.1

Okay here are a few packages  that I and a group of others have been working on as our short term (0.1 release) goal.
http://zenit.senecac.on.ca/wiki/index.php/Fedora-ARM_Package_Building_and_Troubleshooting/Problems
We chose to start with these packages and gradually we’ve added more packages as we progressed.

However, at times we would run into dependency issues. Packages that we were trying to build were requiring libraries that weren’t yet built for arm; In which case we would add the dependency package to our growing list of problem packages.

Personally, I started off attempting to build the glom-1.13.4-1.fc13.armv5tel which failed due to dependency issues(needs libgdamm-3.99.19-1.fc13.armv5tel).
When I tried to resolve the libgdamm dependency, I ran into another dependency problem,
(libgda-4.1.4-1.fc13.src.rpm, armv5tel)  which brings me to where i am now…

I’ve been getting great feedback on possible fixes from community members through IRC and in person on how libgda-4.1.4 should be packaged for arm.  Also, there has been useful feedback and help I’ve gotten through ticketing systems:

https://fedorahosted.org/arm/ticket/7

https://bugzilla.redhat.com/show_bug.cgi?id=682515

All in all, progress is being made. baby steps but forward steps…

Packaging Graphviz for arm

My lost post had me attempting to build libgda-4.1.4. Unfortunately, the build ended up being unsuccessful. Back to the drawing board…

In the build.log for libgda-4.1.4, it mentioned it couldn’t find the graphviz-devel package.
“No package found: graphviz-devel >= 2.26.0″.

I used the “yum provides” to view which package provides the graphviz-devel package.
output:
graphviz-2.26.3-2.fc13.x86_64 : Graph Visualization Tools
Repo        : updates
Matched from:

“yumdownloader –source graphviz-devel” –> downloaded the graphviz-2.26.3-2.fc13.src.rpm

I set up the graphviz-2.26.3-2.fc13.src.rpm in the rpmbuild tree and the ran
arm-koji build command…

graphviz built successfully… hopefully libgda will now work. Stay tuned!

Packaging libgda for arm

Now that I sort of have a good feeling of a how packaging works, I have started packaging my first couple of builds
-libgda-4.1.4-1
-libgda–4.1.6-1

For some reason, its displaying someone else name (rjjimenez) as the owner, a minor issue that i need to fix.

So they are in the process of building. So far I’ve been waiting for about 2 hours for these two to finish building. I’ll make another post when these two are complete which will include some steps i took.

Edit: Both of those builds failed, I’m going to try some different options.