[SOLVED] -current: cannot compile SlackBuilds using imake anymore

lems · 09-01-2014, 09:59 AM

Hello,

since switching my machine to -current, programs using imake fail to build. This is what I get trying to compile tightvnc (from SlackBuilds.org):

Code:

mv -f Makefile Makefile.bak
imake -DUseInstalled -I/usr/lib64/X11/config
In file included from /usr/lib64/X11/config/Imake.tmpl:47:0,
                 from Imakefile.c:34:
/usr/lib64/X11/config/site.def:44:0: fatal error: host.def: No such file or directory
 #include <host.def>
 ^
compilation terminated.
imake: Exit code 1.
  Stop.

This seems to happen with all programs using imake/xmkmf. I know for certain that I compiled imake-using programs on 14.1. This also happens with t/xfig. Any idea how to fix this?

On this machine, I'm running Slackware64 with multilib, in case it matters.

lems

keefaz · 09-01-2014, 10:10 AM

No host.def in /usr/lib64/X11/config?

lems · 09-01-2014, 10:13 AM

Yes, but why? Touching host.def in the source directory fixes this for some programs (xfig seemed to build, for example), but this cannot be the solution, can it? Is this a local problem with my installation?

keefaz · 09-01-2014, 10:17 AM

Not your install problem, host.def was installed by lesstif package which has been replaced by motif in current

ponce · 09-01-2014, 10:25 AM

have you, by any chance, installed a version of CDE?

lems · 09-01-2014, 10:41 AM

Thanks, keefaz, I copied config/cf/host.def from motif's source tarball to /usr/lib64/X11/config and was able to at least start compiling some programs, though SlackBuilds still fail, some (like root-tail) because the find command cannot access $PKG/usr/man, for example:

Code:

+ mkdir -p /tmp/SBo/package-root-tail/usr/X11R6/man/man1
install -c -m 0644 root-tail._man /tmp/SBo/package-root-tail/usr/X11R6/man/man1/root-tail.1x
install.man in . done
find: `/tmp/SBo/package-root-tail/usr/man': No such file or directory

@ponce: CDE is not installed, no. This is basically a fairly new installation with few SBo packages and some third-party binary packages (mostly multilib, ktown and some from alien's sbrepos).

PS: I succeeded building unclutter, though, which uses xmkmf.

keefaz · 09-01-2014, 10:46 AM

Just modify the Slackbuild script for root-tail so it searches in usr/X11R6/man rather than in usr/man

Code:

...
find $PKG/usr/X11R6/man -type f -exec gzip -9 {} \;
..

lems · 09-01-2014, 10:53 AM

Yes, I did that, I guess this is the best it gets currently. Thanks so far.

volkerdi · 09-01-2014, 03:15 PM

Quote:

Originally Posted by lems

Yes, but why? Touching host.def in the source directory fixes this for some programs (xfig seemed to build, for example), but this cannot be the solution, can it? Is this a local problem with my installation?

It is the solution. If you look at the install script for the xorg-cf-files package, you'll see that it touches that file if it doesn't already exist. The LessTif package used to add some stuff to it, but removing that should not have removed the file. It might have left a bit of cruft, but how the file would have vanished is a mystery, since no (official) package claims it. Perhaps some unofficial package does?

Reinstalling xorg-cf-files would touch the file, exactly as you have done.

allend · 09-01-2014, 07:41 PM

Quote:

The LessTif package used to add some stuff to it, but removing that should not have removed the file.

Removal of the lesstif package does delete the host.def file as no other package claims it. From "grep 'config/host.def' /var/log/removed_packages/*".

Quote:

/var/log/removed_packages/lesstif-0.95.2-i486-1:usr/lib/X11/config/host.def

lems · 09-02-2014, 12:07 AM

So I guess what happened was that I first upgraded all packages to -current, and then removed the lesstiff package that claimed the host.def file? I just reinstalled xorg-cf-files and it indeed created an empty host.def file. Thanks for your answers, I think this fixes it. So in the future, I better remove obsolete packages first, and then do the upgrade?

allend · 09-02-2014, 06:03 AM

You came across an unusual corner case that can occur when following Slackware-current. If you had done a fresh install of Slackware-current, then the host.def file would have been created during the installation of the xorg-cf-files package, so your compilation issue would not have arisen.
Here, when doing the upgrade, the removepkg script has done exactly what is expected. It has checked whether a file in the package being removed is in use by any other package. As no such package was found, then the file was assumed to be safe to delete.

Quote:

So in the future, I better remove obsolete packages first, and then do the upgrade?

In this corner case, that strategy would have made no difference. I would stick with upgrading then removing obsolete packages.