[SOLVED] Cannot install from Slackbuilds. Package not put in /tmp.

Randicus Draco Albus · 07-24-2014, 04:53 AM

I have run into a problem trying to install Openbox from Slackbuilds. I tried it on my previous installation and succeeded in installing it, but even though I set Openbox-session as the default GUI, Xfce was loaded. I only mention this to demonstrate that I have been through the process before, although not entirely successfully. The main problem is that I have no aptitude with computers, so anything remotely resembling installing from source is difficult to wrap my brain around.

I have been following these steps, graciously provided by someone who is familiar with Slackware.

Code:

# cd sbo
# wget http://slackbuilds.org/slackbuilds/14.1/desktop/openbox.tar.gz
# tar xvf openbox.tar.gz
# cd openbox
# wget http://openbox.org/dist/openbox/openbox-3.5.0.tar.gz
# ./openbox.SlackBuild
# installpkg /tmp/openbox-3.5.0-i486-1_SBo.tgz

Everything goes well until ./openbox.Slackbuild. The result is

Code:

tar: /root/sbo/openbox/openbox-3.5.2.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

A /tmp/SBo/package-openbox directory has been created, but it is empty. Whatever the simple problem is, it is to much for my brain to figure out. The last time I did this, the procedure worked. What little thing is my computer-incompetent brain overlooking?

jstg · 07-24-2014, 05:00 AM

Quote:

Originally Posted by Randicus Draco Albus

I have been following these steps, graciously provided by someone who is familiar with Slackware.

Code:

# cd sbo
# wget http://slackbuilds.org/slackbuilds/14.1/desktop/openbox.tar.gz
# tar xvf openbox.tar.gz
# cd openbox
# wget http://openbox.org/dist/openbox/openbox-3.5.0.tar.gz
# ./openbox.SlackBuild
# installpkg /tmp/openbox-3.5.0-i486-1_SBo.tgz

Everything goes well until ./openbox.Slackbuild. The result is

Code:

tar: /root/sbo/openbox/openbox-3.5.2.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

A /tmp/SBo/package-openbox directory has been created, but it is empty. Whatever the simple problem is, it is to much for my brain to figure out. The last time I did this, the procedure worked. What little thing is my computer-incompetent brain overlooking?

If you are following the above steps exactly as they are written you are downloading the source for Openbox 3.5.0. The SlackBuild script is looking for the 3.5.2 source.
Changing

Code:

wget http://openbox.org/dist/openbox/openbox-3.5.0.tar.gz

to

Code:

wget http://openbox.org/dist/openbox/openbox-3.5.2.tar.gz

Should get you the correct sources.

Didier Spaier · 07-24-2014, 05:01 AM

As stated on this page the script openbox.SlackBuild expects a source tarball named openbox-3.5.2.tar.gz, not openbox-3.5.0.tar.gz.

You'd do yourself a big favor reading the HOWTO instead of blindly applying receipts.

PS Just late again, but my advice remains.

brianL · 07-24-2014, 05:16 AM

I usually do this:
Download the SlackBuild & source archives to ~/Downloads.
After moving the source to the SlackBuild directory, as root (using su -) cd to there, run the script, then:

Code:

installpkg /tmp/whatever

Works every time.
Or get sbopkg, and use queuefiles for anything that needs a few dependencies.
http://www.sbopkg.org/

Randicus Draco Albus · 07-24-2014, 05:28 AM

That was quick. Thanks. That was why I had better luck last time. I was manually typing the package names. This time I copied-and-pasted and obviously did not look closely enough. (Appropriate image included at bottom of post.)

Although all is not well. Running ./openbox.SlackBuild resulted in this error.

Code:

obrender/image.c:516:5: error: unknown type name 'cairo_surface_t'
obrender/image.c: In function 'LoadWithRsvg':
obrender/image.c:557:9: error: 'CAIRO_FORMAT_ARGB32' undeclared (first use in this function)
obrender/image.c:557:9: note: each undeclared identifier is reported only once for each function it appears in
obrender/image.c:559:5: error: unknown type name 'cairo_t'
obrender/image.c:559:24: warning: initialization makes pointer from integer without a cast [enabled by default]
obrender/image.c:585:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
make[1]: *** [obrender/obrender_libobrender_la-image.lo] Error 1
make[1]: Leaving directory `/tmp/SBo/openbox-3.5.2'
make: *** [all-recursive] Error 1

I am booting into my Debian system for the rest of the day and shall return to this mess tomorrow.

Quote:

You'd do yourself a big favor reading the HOWTO instead of blindly applying receipts.

I have read it several times and it confused me more than clarifying things. That is why I needed someone's help to get as far as I have gotten. I am the kind of person who should be using a "beginner's" distro, but am stupid enough to want to use a real system.

Quote:

Or get sbopkg

Not an option for me. I can only access the home page. Probably because of my location. It locks me out of many sites.

perbh · 07-24-2014, 07:32 AM

Quote:

Originally Posted by Randicus Draco Albus

I can only access the home page. Probably because of my location. It locks me out of many sites.

*chuckles*
According to your 'particulars', your location is: "Sitting in front of my computer"
I fail to see how that will affect your access rights ...

Sorry, couldn't help myself!!

Richard Cranium · 07-24-2014, 08:05 AM

Which version of Slackware are you running? Slackware 14.1 or Slackware64 14.1?

Randicus Draco Albus · 07-24-2014, 08:21 AM

Quote:

Originally Posted by perbh

Sorry, couldn't help myself!!

I currently reside in China. Internet usage can be a pain in the butt.

Quote:

Richard Cranium
Which version of Slackware are you running? Slackware 14.1 or Slackware64 14.1?

64-bit.

Richard Cranium · 07-24-2014, 08:46 AM

Did you install everything or omit some packages?

Slackbuilds assumes that you have a full slackware installation. That header should be in the cairo-1.12.16-x86_64-1_slack14.1 package.

Randicus Draco Albus · 07-24-2014, 08:03 PM

Quote:

Originally Posted by Richard Cranium

Did you install everything or omit some packages? Slackbuilds assumes that you have a full slackware installation.

Yes, I installed everything. Is it possible that a package is missing in either the SlackBuild or the source .tar.gz at the moment? The error message is

Code:

make[1]: ***  [obrender/obrender_libobrender_la-image.lo] Error 1

, but the obrender_liborender_la-image.lo file is not in the obrender directory. There are .lo files for button, colour, fount and gradient, but not image. At first glance it seems to be that one file is missing, but I do not have any experience with such things to know if files are occasionally missing in the source packages.

Apparently I am not as big a dunderhead as I thought. I just installed Conky from SlackBuilds. It was quick, painless and worked perfectly. So I do not know if the problem is with that particular SlackBuild or if I am screwing up somehow.

The good news is I have successfully installed a SlackBuild. So there is hope I can "master" Slackware. The real test will come when I try to install something from elsewhere.

Richard Cranium · 07-24-2014, 09:56 PM

No, the error is

Code:

obrender/image.c:516:5: error: unknown type name 'cairo_surface_t'

That type is provided as part of the cairo package that I had mentioned.

What is the result of running the command

Code:

ls /var/log/packages/cairo-*

..?

If that command returned something like /var/log/packages/cairo-1.12.16-x86_64-1_slack14.1, then what is the result of the command

Code:

ls -l /usr/include/cairo/cairo.h

..? If that command indicates that the cairo.h file isn't empty, then what is the result of the command

Code:

grep cairo_surface_t /usr/include/cairo/cairo.h

..? (That one can be pretty long.)

Randicus Draco Albus · 07-25-2014, 04:24 AM

Code:

# ls /var/log/packages/cairo-*
/var/log/packages/cairo-1.10.2-x86_64-2

# ls -l /usr/include/cairo/cairo.h
-rw-r--r-- 1 root root 93134 Mar 20  2011 /usr/include/cairo/cairo.h

I am not familiar with Slackware's notation. I am used to using apt-cache. So I do not know if the lack of _64-1_slack14.1 at the end is significant. I cannot tell if these are descriptions of what the package is and where it would be if it was installed, or if this shows the package as being installed.

Code:

# grep cairo_surface_t /usr/include/cairo/cairo.h
 * cairo_surface_t:
 * A #cairo_surface_t represents an image, either as the destination
 * surface.  To draw to a #cairo_surface_t, create a cairo context
 * There are different subtypes of #cairo_surface_t for
 * and asks cairo to wrap that in a #cairo_surface_t, then the contents are
 * Memory management of #cairo_surface_t is done with
typedef struct _cairo_surface cairo_surface_t;
 * operations to a #cairo_surface_t.  There are different subtypes of
cairo_create (cairo_surface_t *target);
              cairo_surface_t *surface,
            cairo_surface_t *surface,
cairo_public cairo_surface_t *
cairo_public cairo_surface_t *
cairo_public cairo_surface_t *
cairo_surface_create_similar (cairo_surface_t  *other,
cairo_public cairo_surface_t *
cairo_surface_create_for_rectangle (cairo_surface_t    *target,
cairo_public cairo_surface_t *
cairo_surface_reference (cairo_surface_t *surface);
cairo_surface_finish (cairo_surface_t *surface);
cairo_surface_destroy (cairo_surface_t *surface);
cairo_surface_get_device (cairo_surface_t *surface);
cairo_surface_get_reference_count (cairo_surface_t *surface);
cairo_surface_status (cairo_surface_t *surface);
 * cairo_surface_type_t:
 * #cairo_surface_type_t is used to describe the type of a given
 * The various #cairo_surface_t functions can be used with surfaces of
typedef enum _cairo_surface_type {
} cairo_surface_type_t;
cairo_public cairo_surface_type_t
cairo_surface_get_type (cairo_surface_t *surface);
cairo_surface_get_content (cairo_surface_t *surface);
cairo_surface_write_to_png (cairo_surface_t    *surface,
cairo_surface_write_to_png_stream (cairo_surface_t    *surface,
cairo_surface_get_user_data (cairo_surface_t         *surface,
cairo_surface_set_user_data (cairo_surface_t         *surface,
cairo_surface_get_mime_data (cairo_surface_t        *surface,
cairo_surface_set_mime_data (cairo_surface_t        *surface,
cairo_surface_get_font_options (cairo_surface_t      *surface,
cairo_surface_flush (cairo_surface_t *surface);
cairo_surface_mark_dirty (cairo_surface_t *surface);
cairo_surface_mark_dirty_rectangle (cairo_surface_t *surface,
cairo_surface_set_device_offset (cairo_surface_t *surface,
cairo_surface_get_device_offset (cairo_surface_t *surface,
cairo_surface_set_fallback_resolution (cairo_surface_t    *surface,
cairo_surface_get_fallback_resolution (cairo_surface_t    *surface,
cairo_surface_copy_page (cairo_surface_t *surface);
cairo_surface_show_page (cairo_surface_t *surface);
cairo_surface_has_show_text_glyphs (cairo_surface_t *surface);
cairo_public cairo_surface_t *
cairo_public cairo_surface_t *
cairo_image_surface_get_data (cairo_surface_t *surface);
cairo_image_surface_get_format (cairo_surface_t *surface);
cairo_image_surface_get_width (cairo_surface_t *surface);
cairo_image_surface_get_height (cairo_surface_t *surface);
cairo_image_surface_get_stride (cairo_surface_t *surface);
cairo_public cairo_surface_t *
cairo_public cairo_surface_t *
cairo_public cairo_surface_t *
cairo_recording_surface_ink_extents (cairo_surface_t *surface,
cairo_pattern_create_for_surface (cairo_surface_t *surface);
               cairo_surface_t **surface);

Didier Spaier · 07-25-2014, 04:49 AM

I don't think that the issue be caused by a missing cairo as I checked that even without it openbox can be build.

Let's check the integrity of the source tarball.

Go to the directory where you downloaded it and type:

Code:

md5sum openbox-3.5.2.tar.gz

Check that the answer be exactly this one:

Code:

93df606606053b7e8578a5c116afb8ec  openbox-3.5.2.tar.gz

If not, download the source tarball again and check again its integrity.

PS the reason why the record in /var/log/packages doesn't end in _64-1_slack14.1 is that you didn't upgrade cairo following this change noted in the ChangeLog:

Code:

Sat Feb 1 00:56:38 UTC 2014
patches/packages/cairo-1.12.16-x86_64-1_slack14.1.txz: Upgraded.
       This is a bugfix update that was tested in -current and found to resolve
       some outstanding issues with the package that shipped in Slackware 14.1.
       Removed --enable-xcb-shm (may cause instability with GTK+3).
       Removed --enable-xlib-xcb (causes GIMP slowdown).
       Added --enable-ft and --enable-gl.

IMO it's better to upgrade at least when there is a security fix (not the case here). But as openbox doesn't need cairo to be built that is not the issue in this case.

PPS As others have noted after I did hit the "Save" button, anyhow you don't have a cairo version shipped in Slackware version 14.1. So your whole system is not consistent. this could very well be the source of your issue. Whether you made a fresh installation of Slackware64-14.1 or upgraded it from a previous version, something went wrong during an upgrade. So what did you do exactly?

saulgoode · 07-25-2014, 04:55 AM

Quote:

Originally Posted by Randicus Draco Albus

Code:

# ls /var/log/packages/cairo-*
/var/log/packages/cairo-1.10.2-x86_64-2

This suggests that you have Slackware 14.0 installed, not 14.1. The 14.0 Openbox SlackBuilds are available here.

EDIT: You might even have SW 13.37 installed since it also shipped with Cairo 1.10.2. Nonetheless, the same Openbox SlackBuild was used for both 13.37 and 14.0 . To find out which version of SW you have, look in /etc/slackware-version

Richard Cranium · 07-25-2014, 04:58 AM

Ah.

Slackware's package database is pretty much the contents of the directory /var/log/packages. Each file in that directory is added by the installpkg or upgradepkg and contains a list of the files added/updated by the package manager (with the leading "/" omitted from the path).

In your case, you have cairo-1.10.2-x86_64-2 installed. That's the "cairo" package, version 1.10.2, for an x86_64 system, build #2.

My machine has cairo-1.12.16-x86_64-1_slack14.1 installed. "cairo" package, version 1.12.16, for an x86_64 system, build #1, specifically for slackware 14.1.

Please check your local Slackware mirror for package upgrades, which would be in the slackware-14.1/patches/packages/ directory of the mirror site. The cairo update may be significant, but you should apply them all via downloading the .txz files and using "upgradepkg <filename>" as root to upgrade them. Unless you really are running Slackware64 14.0, instead. In that case, follow saulgoode's advice in the previous post.