Problems recompiling WindowMaker from original slackbuild
 

Hello,
I was trying to recompile WindowMaker to apply the single click patch, and found out that using the slackbuild provided on the Slack source disks (Disk 5), I couldn't even compile an unmodified WindowMaker properly. Specifically the WPrefs.app utility fails to compile.

Any suggestions as to why this might be, or how to fix it? I'm using GCC 3.4.6, which AFAIK is the default for Slackware. I'm also sure I've got the fontconfig package installed.

Thanks,
Garron

relevant error log below:

Do you have fontconfig installed ? Try reinstalling that.

This is the critical error here:
from searching my '/var/log/packages' I get

Are you running Dropline? Dropline puts fontconfig here:
If that is the case perhaps try linking usr/X11R6/include/fontconfig/ to /usr/include/fontconfig/

Fontconfig is installed, I tried reinstalling it but no change.

No dropline (or any Gnome) on the system.

For the moment I've just copied the old WPrefs.app into the new package, and edited the windowmaker preferences by hand to enable single-click. Which works fine. Still, I'm quite curious as to what's causing the error.

Thanks for the suggestions so far.

OK, looking at the WindowMaker Makefile, I see the line "includedir = ${prefix}/include", where ${prefix} is /usr. So I symlinked /usr/X11/include/fontconfig to /usr/include, and everything compiled.

So now my question is, is this a bug, or is my system somehow misconfigured? Is anyone else able to compile WindowMaker using the provided slackbuild?

Have a look in my WindowMaker area. I have a large collection of patches and accessories there. I use a patched version which provides a history list to the run-box among other fixes. I added the single-click patch to the list and recompiled. (See the wmaker-0.92.0 dir) there's also a src2pkg build script which you can use to compile from source if you have src2pkg installed. Or just have a good look at what the script does and use those command as suggestions.

http://distro.ibiblio.org/pub/linux/...s/WindowMaker/

The main problem you are having is probably from not running autogen.sh.
Try doing that before running configure.
If that doesn't do it try running 'autoreconf -if' -the best kept secret in ages...

There on my site you can also find the wdm display manager(with xpenguins!), the sound server for WindowMaker and over 50 DockApps which are upgraded to work best with the new WindowMaker.

Hey, thanks. I did actually get a working version, but run-box history would be useful. I'll give it a shot.

All that I'm doing is copying the files from /source/xap/windowmaker/ on the Slackware 11 source disk to my hard drive, and running the windowmaker.SlackBuild script. It was my understanding that these SlackBuild scripts are recreations of the steps Pat Volkerding uses to make the package that comes with the Slack CD?

As a sidenote, though, I don't see an autogen.sh anywhere in the Windowmaker sources. The SlackBuild certainly doesn't make any mention of one.

Okay you are using the Slackware tarball, right? Note that the Slackware current binary package is from Jul 21 2005, which means it's a Slackware-10.1 package compiled against xorg-6.8.2.
If you don#t know how to pick your way throught the code of the script, you can still update the source config files.
Just unpack the original archive, cd into the sources and run 'autoreconf -if' and then repack the sources and run the script.
Building and packaging WindowMaker is not usually as straightforward as most programs.

A lot of the patches and config stuff that I use come from the ALT/Sysiphus Linux distribution which is maintained by a long-time collaborator/contributor to WindowMaker project.

The package I uploaded has the history list and single-click already activated(the single-click option is in the Prefs Expert section).
The history list is activated simply changing this:
%a(Run,Type command to run:)
to this:
%A(Run,Type command to run:)
in the Prefs options for the 'Run...' desktop menu item.
But I install default menus and config files that set all that up by default.

Ah, that looks like the answer there.
Thanks!