LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-04-2010, 09:55 AM   #1
Auzern
Member
 
Registered: Jul 2010
Posts: 44

Rep: Reputation: 0
Exclamation Window Manager Installation


I have been trying to install a different window manager on Slackware.
I have downloaded from here --> http://www.slackbuilds.com/repository/13.1/

And I have followed this guide to install wmii --> http://www.slackbuilds.com/howto/

Now when I follow the same patter, I get this error:
Quote:
root@sslf:/home/sslf/Essential# ./wmii
bash: ./wmii: is a directory
root@sslf:/home/sslf/Essential# ./wmii/wmii.SlackBuild
tar: /home/sslf/Essential/wmii-3.6.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
root@sslf:/home/sslf/Essential#
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 10-04-2010, 10:21 AM   #2
patostevens
Member
 
Registered: Dec 2007
Location: Kennewick,WA
Distribution: Slackware 14
Posts: 170

Rep: Reputation: 21
Following the Slackbuilds directions, you should have a directory named wmii that holds several files including wmii.Slackbuild. Now type at the prompt the following:
cd /path/to/wmii
chmod +x wmii.Slackbuild
./wmii.Slackbuild

This should begin the compiling, etc. When done the final package will be stored in /tmp (the default location). Then type the following:
installpkg /tmp/wmii-rest-of-package-name.

That should give you an installed package. Be sure to read all of the documentation on how to set your window manager.

Good Luck.

Last edited by patostevens; 10-04-2010 at 10:22 AM. Reason: bad typing
 
1 members found this post helpful.
Old 10-04-2010, 10:27 AM   #3
Auzern
Member
 
Registered: Jul 2010
Posts: 44

Original Poster
Rep: Reputation: 0
Thanks for the reply, patostevens.
Here it is:
Quote:
root@sslf:/home/sslf/Essential# ls -a
./ ../ wmii/ wmii.tar.gz
root@sslf:/home/sslf/Essential# chmod +x wmii.Slackbuild
chmod: cannot access `wmii.Slackbuild': No such file or directory
root@sslf:/home/sslf/Essential# chmod +x wmii.SlackBuild
chmod: cannot access `wmii.SlackBuild': No such file or directory
root@sslf:/home/sslf/Essential# cd wmii
root@sslf:/home/sslf/Essential/wmii# chmod +x wmii.SlackBuild
root@sslf:/home/sslf/Essential/wmii# chmod +x wmii.SlackBuild
root@sslf:/home/sslf/Essential/wmii# chmod +x wmii.Slackbuild
chmod: cannot access `wmii.Slackbuild': No such file or directory
root@sslf:/home/sslf/Essential/wmii# ./wmii.SlackBuild
tar: /home/sslf/Essential/wmii/wmii-3.6.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
root@sslf:/home/sslf/Essential/wmii# ls -a
./ ../ README doinst.sh slack-desc wmii-3.6-config_mk.diff wmii.SlackBuild* wmii.info xinitrc.wmii
root@sslf:/home/sslf/Essential/wmii# installpkg doinst.sh
Cannot install doinst.sh: file does not end in .tgz, .tbz, .tlz, or .txz
root@sslf:/home/sslf/Essential/wmii# doinst.sh
bash: doinst.sh: command not found
root@sslf:/home/sslf/Essential/wmii# installpkg wmii.SlackBuild
Cannot install wmii.SlackBuild: file does not end in .tgz, .tbz, .tlz, or .txz
root@sslf:/home/sslf/Essential/wmii# sslf:/home/sslf/Essential# cd wmii
bash: sslf:/home/sslf/Essential#: No such file or directory
root@sslf:/home/sslf/Essential/wmii# root@sslf:/home/sslf/Essential/wmii# chmod +x wmii.SlackBuild
bash: root@sslf:/home/sslf/Essential/wmii#: No such file or directory
root@sslf:/home/sslf/Essential/wmii# root@sslf:/home/sslf/Essential/wmii# chmod +x wmii.SlackBuild
bash: root@sslf:/home/sslf/Essential/wmii#: No such file or directory
root@sslf:/home/sslf/Essential/wmii# root@sslf:/home/sslf/Essential/wmii# chmod +x wmii.Slackbuild
bash: root@sslf:/home/sslf/Essential/wmii#: No such file or directory
root@sslf:/home/sslf/Essential/wmii# chmod: cannot access `wmii.Slackbuild': No such file or directory
> root@sslf:/home/sslf/Essential/wmii# ./wmii.SlackBuild
> tar: /home/sslf/Essential/wmii/wmii-3.6.tar.gz: Cannot open: No such file or directory
> tar: Error is not recoverable: exiting now
> root@sslf:/home/sslf/Essential/wmii# ls -a
> ./ ../ README doinst.sh slack-desc wmii-3.6-config_mk.diff wmii.SlackBuild* wmii.info xinitrc.wmii
> root@sslf:/home/sslf/Essential/wmii# installpkg doinst.sh
> Cannot install doinst.sh: file does not end in .tgz, .tbz, .tlz, or .txz
> root@sslf:/home/sslf/Essential/wmii# doinst.sh
> bash: doinst.sh: command not found
> root@sslf:/home/sslf/Essential/wmii# installpkg wmii.SlackBuild
> Cannot install wmii.SlackBuild: file does not end in .tgz,
I'm still unable to install
 
Old 10-04-2010, 11:20 AM   #4
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
SHORT VERSION:

1) create a directory to work in. I call mine BIGROOT.
2) Download small archive from SBO. It contains the slackbuild script, and README file, and other stuff.
3) Put the above archive into BIGROOT directory.
4) Extract above archive so the contents end up in the same BIGROOT directory.
NOTE: Thanks to catkin's next post for the reminder, here's an adjustment: IF you downloaded the small archive from SBO, it will create its own folder INSIDE BIGROOT when you extract it. Therefore, when you next download the actual source-code archive (step 5+6), place it INSIDE the subdirectory that the above archive created.
5) Download the wmii archive from where the SBO link sends you.
6) Do not extract that one - just put it into BIGROOT (inside the subdirectory mentioned above) with the other stuff.
6b) Enter the subdirectory where the slackbuild script and all the other files are.
7) chmod a+x the slackbuild script.
8) execute the slackbuild script.
9) do the `installpkg` step. You're done!

IMPORTANT: The key is to have ALL the pieces in one place before running the slackbuild.

LONG VERSION:

You've got two directories on the go from the looks of things, but it appears that neither of them contains the compressed source-code archive of the wmii that you're trying to install, as well as the other components from SBO..

You want ONE directory; name it whatever you want - in my example below, I use the name BIGROOT. Into that directory, you are to place ALL the files that you download from slackbuilds.org, AND the wmii-3.6.tar.gz archive, which you download from wherever the link on slackbuilds.org sends you to get it. Do not extract the source archive of wmii itself, ONLY the archive you got from SBO.

IMPORTANT: we must distinguish between the "source code archive", and the "archive from SBO", as I believe you are being confused by these two.

>> This archive, if you download the SBO files in this single archive, you DO extract, so the contents end up in your BIGROOT directory: http://slackbuilds.org/slackbuilds/1...op/wmii.tar.gz
The above archive holds all the little slackbuild pieces you need, EXCEPT the source-code for wmii.

>> This archive: http://code.suckless.org/dl/wmii/wmii-3.6.tar.gz
is the source-code for wmii itself. You DO NOT unpack that one; put the whole thing directly into the BIGROOT directory you created earlier, alongside the little pieces that should already be there from extracting the archive from SBO.

Now: With all that stuff in the one directory (we called it BIGROOT), you enter that BIGROOT directory, and chmod +x your slackbuild script if it is not yet executable. Now run the slackbuild script.


NOTES: It appears that you're very new to this. Congratulations on giving it a shot; it can be pretty confusing at first.
But, you have to understand that blindly executing commands as you have been above, despite the repeated errors being thrown back, will not end you up with a working package, and even if it does, you will have no idea what exactly you did to get it, so doing it again will be a repeat of this situation.
Take your time, not only to read the instructions at SBO, but to understand what the commands are doing, or supposed to do. The errors are telling you important things, so please pay attention to what they say - ignoring them and running even more commands will not help.

I do not mean to be harsh, so please don't take that impression away from what I say. I was where you are too a few years ago, just like we all were at one point. But you must take your time, and understand what you're doing, in order to be able to diagnose what should be rather small problems you're encountering, and easily fix the problem.
Before you know it, you'll be downloading and building Slackbuilds in matters of minutes!

If you run into more troubles, don't hesitate to show us what's going on and ask for more help! We'll try our best.

Last edited by GrapefruiTgirl; 10-04-2010 at 11:32 AM. Reason: added notes about subdirectory.
 
3 members found this post helpful.
Old 10-04-2010, 11:21 AM   #5
catkin
LQ 5k Club
 
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Debian
Posts: 8,577
Blog Entries: 31

Rep: Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195
The first step is to unpack the SlackBuild archive; normally this creates the wmii (or whatever) directory; the unpacking command is tar -zxvf wmii.tar.gz
 
1 members found this post helpful.
Old 10-05-2010, 08:25 AM   #6
Auzern
Member
 
Registered: Jul 2010
Posts: 44

Original Poster
Rep: Reputation: 0
Thanks a lot for the reply, GrapefruiTgirl and catking.
Very well written and very helpful too. Now I have read them properly and tried to execute the command. But now I get this error:
Quote:
root@sslf:/home/sslf/Essential/wmii# chmod +x wmii.SlackBuild
root@sslf:/home/sslf/Essential/wmii# ./wmii.SlackBuild
wmii-3.6/
wmii-3.6/DISTRIBUTORS
wmii-3.6/LICENSE
wmii-3.6/Makefile
wmii-3.6/NOTES
wmii-3.6/README
wmii-3.6/TODO
wmii-3.6/cmd/
wmii-3.6/cmd/Makefile
wmii-3.6/cmd/util.c
wmii-3.6/cmd/wmii/
wmii-3.6/cmd/wmii/Makefile
wmii-3.6/cmd/wmii/area.c
wmii-3.6/cmd/wmii/bar.c
wmii-3.6/cmd/wmii/client.c
wmii-3.6/cmd/wmii/column.c
wmii-3.6/cmd/wmii/dat.h
wmii-3.6/cmd/wmii/event.c
wmii-3.6/cmd/wmii/fns.h
wmii-3.6/cmd/wmii/frame.c
wmii-3.6/cmd/wmii/fs.c
wmii-3.6/cmd/wmii/geom.c
wmii-3.6/cmd/wmii/key.c
wmii-3.6/cmd/wmii/main.c
wmii-3.6/cmd/wmii/map.c
wmii-3.6/cmd/wmii/message.c
wmii-3.6/cmd/wmii/mouse.c
wmii-3.6/cmd/wmii/printevent.c
wmii-3.6/cmd/wmii/printevent.h
wmii-3.6/cmd/wmii/rule.c
wmii-3.6/cmd/wmii/utf.c
wmii-3.6/cmd/wmii/view.c
wmii-3.6/cmd/wmii/x11.c
wmii-3.6/cmd/wmii/x11.h
wmii-3.6/cmd/wmii9menu.c
wmii-3.6/cmd/wmii9rc.sh
wmii-3.6/cmd/wmiiloop.sh
wmii-3.6/cmd/wmiir.c
wmii-3.6/cmd/wmiistartrc.sh
wmii-3.6/config.mk
wmii-3.6/debian/
wmii-3.6/debian/changelog
wmii-3.6/debian/control
wmii-3.6/debian/copyright
wmii-3.6/debian/docs
wmii-3.6/debian/file/
wmii-3.6/debian/file/wmii.desktop
wmii-3.6/debian/patches/
wmii-3.6/debian/patches/unx-terminal-emulater.awk
wmii-3.6/debian/patches/x-terminal-emulater.ed
wmii-3.6/debian/patches/x-terminal-emulater.list
wmii-3.6/debian/rules
wmii-3.6/debian/watch
wmii-3.6/debian/wmii.menu
wmii-3.6/debian/wmii.wm
wmii-3.6/img/
wmii-3.6/img/icon.png
wmii-3.6/img/mkfile
wmii-3.6/img/wmii.eps
wmii-3.6/img/wmii.mp
wmii-3.6/img/wmii.png
wmii-3.6/include/
wmii-3.6/include/Makefile
wmii-3.6/include/bio.h
wmii-3.6/include/fmt.h
wmii-3.6/include/plan9.h
wmii-3.6/include/regcomp.h
wmii-3.6/include/regexp9.h
wmii-3.6/include/utf.h
wmii-3.6/include/util.h
wmii-3.6/libbio/
wmii-3.6/libbio/Makefile
wmii-3.6/libbio/NOTICE
wmii-3.6/libbio/README
wmii-3.6/libbio/bbuffered.c
wmii-3.6/libbio/bcat.c
wmii-3.6/libbio/bfildes.c
wmii-3.6/libbio/bflush.c
wmii-3.6/libbio/bgetc.c
wmii-3.6/libbio/bgetd.c
wmii-3.6/libbio/bgetrune.c
wmii-3.6/libbio/binit.c
wmii-3.6/libbio/bio.3
wmii-3.6/libbio/boffset.c
wmii-3.6/libbio/bprint.c
wmii-3.6/libbio/bputc.c
wmii-3.6/libbio/bputrune.c
wmii-3.6/libbio/brdline.c
wmii-3.6/libbio/brdstr.c
wmii-3.6/libbio/bread.c
wmii-3.6/libbio/bseek.c
wmii-3.6/libbio/bvprint.c
wmii-3.6/libbio/bwrite.c
wmii-3.6/libfmt/
wmii-3.6/libfmt/Makefile
wmii-3.6/libfmt/NOTICE
wmii-3.6/libfmt/README
wmii-3.6/libfmt/charstod.c
wmii-3.6/libfmt/dofmt.c
wmii-3.6/libfmt/dorfmt.c
wmii-3.6/libfmt/errfmt.c
wmii-3.6/libfmt/fltfmt.c
wmii-3.6/libfmt/fmt.c
wmii-3.6/libfmt/fmtdef.h
wmii-3.6/libfmt/fmtfd.c
wmii-3.6/libfmt/fmtfdflush.c
wmii-3.6/libfmt/fmtinstall.3
wmii-3.6/libfmt/fmtlock.c
wmii-3.6/libfmt/fmtprint.c
wmii-3.6/libfmt/fmtquote.c
wmii-3.6/libfmt/fmtrune.c
wmii-3.6/libfmt/fmtstr.c
wmii-3.6/libfmt/fmtvprint.c
wmii-3.6/libfmt/fprint.c
wmii-3.6/libfmt/libfmt.a
wmii-3.6/libfmt/nan64.c
wmii-3.6/libfmt/pow10.c
wmii-3.6/libfmt/print.3
wmii-3.6/libfmt/print.c
wmii-3.6/libfmt/runefmtstr.c
wmii-3.6/libfmt/runeseprint.c
wmii-3.6/libfmt/runesmprint.c
wmii-3.6/libfmt/runesnprint.c
wmii-3.6/libfmt/runesprint.c
wmii-3.6/libfmt/runevseprint.c
wmii-3.6/libfmt/runevsmprint.c
wmii-3.6/libfmt/runevsnprint.c
wmii-3.6/libfmt/seprint.c
wmii-3.6/libfmt/smprint.c
wmii-3.6/libfmt/snprint.c
wmii-3.6/libfmt/sprint.c
wmii-3.6/libfmt/strtod.c
wmii-3.6/libfmt/test.c
wmii-3.6/libfmt/test2.c
wmii-3.6/libfmt/test3.c
wmii-3.6/libfmt/vfprint.c
wmii-3.6/libfmt/vseprint.c
wmii-3.6/libfmt/vsmprint.c
wmii-3.6/libfmt/vsnprint.c
wmii-3.6/libregexp/
wmii-3.6/libregexp/Makefile
wmii-3.6/libregexp/NOTICE
wmii-3.6/libregexp/README
wmii-3.6/libregexp/regaux.c
wmii-3.6/libregexp/regcomp.c
wmii-3.6/libregexp/regerror.c
wmii-3.6/libregexp/regexec.c
wmii-3.6/libregexp/regexp9.3
wmii-3.6/libregexp/regexp9.7
wmii-3.6/libregexp/regsub.c
wmii-3.6/libregexp/rregexec.c
wmii-3.6/libregexp/rregsub.c
wmii-3.6/libregexp/test.c
wmii-3.6/libregexp/test2.c
wmii-3.6/libutf/
wmii-3.6/libutf/Makefile
wmii-3.6/libutf/NOTICE
wmii-3.6/libutf/README
wmii-3.6/libutf/isalpharune.3
wmii-3.6/libutf/libutf.a
wmii-3.6/libutf/rune.3
wmii-3.6/libutf/rune.c
wmii-3.6/libutf/runestrcat.3
wmii-3.6/libutf/runestrcat.c
wmii-3.6/libutf/runestrchr.c
wmii-3.6/libutf/runestrcmp.c
wmii-3.6/libutf/runestrcpy.c
wmii-3.6/libutf/runestrdup.c
wmii-3.6/libutf/runestrecpy.c
wmii-3.6/libutf/runestrlen.c
wmii-3.6/libutf/runestrncat.c
wmii-3.6/libutf/runestrncmp.c
wmii-3.6/libutf/runestrncpy.c
wmii-3.6/libutf/runestrrchr.c
wmii-3.6/libutf/runestrstr.c
wmii-3.6/libutf/runetype.c
wmii-3.6/libutf/utf.7
wmii-3.6/libutf/utfecpy.c
wmii-3.6/libutf/utflen.c
wmii-3.6/libutf/utfnlen.c
wmii-3.6/libutf/utfrrune.c
wmii-3.6/libutf/utfrune.c
wmii-3.6/libutf/utfutf.c
wmii-3.6/man/
wmii-3.6/man/Makefile
wmii-3.6/man/mkfile
wmii-3.6/man/wmii.1
wmii-3.6/man/wmii.tex
wmii-3.6/man/wmiiloop.1
wmii-3.6/man/wmiiloop.tex
wmii-3.6/man/wmiir.1
wmii-3.6/mk/
wmii-3.6/mk/common.mk
wmii-3.6/mk/dir.mk
wmii-3.6/mk/gcc.mk
wmii-3.6/mk/hdr.mk
wmii-3.6/mk/lib.mk
wmii-3.6/mk/man.mk
wmii-3.6/mk/many.mk
wmii-3.6/mk/one.mk
wmii-3.6/mk/wmii.mk
wmii-3.6/rc/
wmii-3.6/rc/Makefile
wmii-3.6/rc/rc.wmii.rc
wmii-3.6/rc/sh.wmii
wmii-3.6/rc/welcome.sh
wmii-3.6/rc/wmiirc.sh
wmii-3.6/test/
wmii-3.6/test/event
wmii-3.6/test/event.b
wmii-3.6/test/mkfile
wmii-3.6/util/
wmii-3.6/util/cleanname
wmii-3.6/util/compile
wmii-3.6/util/genconfig
wmii-3.6/util/link
patching file config.mk
MAKE all libutf/
CC libutf/rune.o
CC libutf/runestrcat.o
CC libutf/runestrchr.o
CC libutf/runestrcmp.o
CC libutf/runestrcpy.o
CC libutf/runestrdup.o
CC libutf/runestrlen.o
CC libutf/runestrecpy.o
CC libutf/runestrncat.o
CC libutf/runestrncmp.o
CC libutf/runestrncpy.o
CC libutf/runestrrchr.o
CC libutf/runestrstr.o
CC libutf/runetype.o
CC libutf/utfecpy.o
libutf/utfecpy.c:26: warning: implicit declaration of function 'memccpy'
libutf/utfecpy.c:26: warning: assignment makes pointer from integer without a cast
CC libutf/utflen.o
CC libutf/utfnlen.o
CC libutf/utfrrune.o
CC libutf/utfrune.o
CC libutf/utfutf.o
AR lib/libutf.a
MAKE all libfmt/
CC libfmt/dofmt.o
CC libfmt/dorfmt.o
CC libfmt/errfmt.o
CC libfmt/fltfmt.o
CC libfmt/fmt.o
CC libfmt/fmtfd.o
CC libfmt/fmtfdflush.o
CC libfmt/fmtlock.o
CC libfmt/fmtprint.o
CC libfmt/fmtquote.o
CC libfmt/fmtrune.o
CC libfmt/fmtstr.o
CC libfmt/fmtvprint.o
CC libfmt/fprint.o
CC libfmt/print.o
CC libfmt/runefmtstr.o
CC libfmt/runeseprint.o
CC libfmt/runesmprint.o
CC libfmt/runesnprint.o
CC libfmt/runesprint.o
CC libfmt/runevseprint.o
CC libfmt/runevsmprint.o
CC libfmt/runevsnprint.o
CC libfmt/seprint.o
CC libfmt/smprint.o
CC libfmt/snprint.o
CC libfmt/sprint.o
CC libfmt/strtod.o
CC libfmt/vfprint.o
CC libfmt/vseprint.o
CC libfmt/vsmprint.o
CC libfmt/vsnprint.o
CC libfmt/charstod.o
CC libfmt/pow10.o
CC libfmt/nan64.o
AR lib/libfmt.a
MAKE all libbio/
CC libbio/bbuffered.o
CC libbio/bfildes.o
CC libbio/bflush.o
CC libbio/bgetc.o
CC libbio/bgetd.o
CC libbio/bgetrune.o
CC libbio/binit.o
CC libbio/boffset.o
CC libbio/bprint.o
CC libbio/bvprint.o
CC libbio/bputc.o
CC libbio/bputrune.o
CC libbio/brdline.o
CC libbio/brdstr.o
CC libbio/bread.o
CC libbio/bseek.o
CC libbio/bwrite.o
AR lib/libbio.a
MAKE all libregexp/
CC libregexp/regcomp.o
CC libregexp/regerror.o
CC libregexp/regexec.o
CC libregexp/regsub.o
CC libregexp/regaux.o
CC libregexp/rregexec.o
CC libregexp/rregsub.o
AR lib/libregexp9.a
MAKE all cmd/
CC cmd/util.o
cmd/util.c:100: warning: implicit declaration of function 'strdup'
cmd/util.c:100: warning: initialization makes pointer from integer without a cast
CC cmd/wmii9menu.o
LD cmd/wmii9menu.O
FILTER cmd/wmii9rc.sh
FILTER cmd/wmiiloop.sh
CC cmd/wmiir.o
cmd/wmiir.c:11:17: error: ixp.h: No such file or directory
cmd/wmiir.c:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
cmd/wmiir.c:28: warning: implicit declaration of function 'ixp_errbuf'
cmd/wmiir.c:28: warning: passing argument 2 of 'fmtstrcpy' makes pointer from integer without a cast
../include/fmt.h:120: note: expected 'const char *' but argument is of type 'int'
cmd/wmiir.c:33: error: expected ')' before '*' token
cmd/wmiir.c:49: error: 'Stat' undeclared
cmd/wmiir.c:49: error: 'st1' undeclared
cmd/wmiir.c:49: error: 'st2' undeclared
cmd/wmiir.c:49: warning: left-hand operand of comma expression has no effect
cmd/wmiir.c:51: error: expected expression before ')' token
cmd/wmiir.c:52: error: expected expression before ')' token
cmd/wmiir.c:71: error: 'P9_DMDIR' undeclared
cmd/wmiir.c:85: warning: implicit declaration of function 'ctime_r'
cmd/wmiir.c:91: error: expected ')' before '*' token
cmd/wmiir.c:107: error: 'IxpCFid' undeclared
cmd/wmiir.c:107: error: 'fid' undeclared
cmd/wmiir.c:116: warning: implicit declaration of function 'ixp_open'
cmd/wmiir.c:116: error: 'client' undeclared
cmd/wmiir.c:116: error: 'P9_OWRITE' undeclared
cmd/wmiir.c:120: warning: implicit declaration of function 'write_data'
cmd/wmiir.c:121: warning: implicit declaration of function 'ixp_close'
cmd/wmiir.c:127: error: 'IxpCFid' undeclared
cmd/wmiir.c:127: error: 'fid' undeclared
cmd/wmiir.c:137: error: 'client' undeclared
cmd/wmiir.c:137: error: 'P9_OWRITE' undeclared
cmd/wmiir.c:157: warning: implicit declaration of function 'ixp_write'
cmd/wmiir.c:166: error: 'IxpCFid' undeclared
cmd/wmiir.c:166: error: 'fid' undeclared
cmd/wmiir.c:175: warning: implicit declaration of function 'ixp_create'
cmd/wmiir.c:175: error: 'client' undeclared
cmd/wmiir.c:175: error: 'P9_OWRITE' undeclared
cmd/wmiir.c:179: error: 'P9_DMDIR' undeclared
cmd/wmiir.c:195: warning: implicit declaration of function 'ixp_remove'
cmd/wmiir.c:195: error: 'client' undeclared
cmd/wmiir.c:202: error: 'IxpCFid' undeclared
cmd/wmiir.c:202: error: 'fid' undeclared
cmd/wmiir.c:212: error: 'client' undeclared
cmd/wmiir.c:212: error: 'P9_OREAD' undeclared
cmd/wmiir.c:217: warning: implicit declaration of function 'ixp_read'
cmd/wmiir.c:229: error: 'IxpMsg' undeclared
cmd/wmiir.c:229: error: expected ';' before 'm'
cmd/wmiir.c:230: error: 'Stat' undeclared
cmd/wmiir.c:230: error: 'stat' undeclared
cmd/wmiir.c:231: error: 'IxpCFid' undeclared
cmd/wmiir.c:231: error: 'fid' undeclared
cmd/wmiir.c:251: warning: implicit declaration of function 'ixp_stat'
cmd/wmiir.c:251: error: 'client' undeclared
cmd/wmiir.c:255: error: 'P9_DMDIR' undeclared
cmd/wmiir.c:256: warning: implicit declaration of function 'print_stat'
cmd/wmiir.c:257: warning: implicit declaration of function 'ixp_freestat'
cmd/wmiir.c:262: error: 'P9_OREAD' undeclared
cmd/wmiir.c:271: error: 'm' undeclared
cmd/wmiir.c:271: warning: implicit declaration of function 'ixp_message'
cmd/wmiir.c:271: error: 'MsgUnpack' undeclared
cmd/wmiir.c:277: warning: implicit declaration of function 'ixp_pstat'
cmd/wmiir.c:335: error: 'client' undeclared
cmd/wmiir.c:335: warning: implicit declaration of function 'ixp_mount'
cmd/wmiir.c:346: warning: implicit declaration of function 'ixp_unmount'
make[1]: *** [wmiir.o] Error 1
make: *** [dall] Error 2
 
Old 10-05-2010, 08:48 AM   #7
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.2
Posts: 7,808
Blog Entries: 58

Rep: Reputation: Disabled
Looks like you haven't installed its dependencies, from the README:
Quote:
This requires libixp, plan9port, and dmenu.
To make things easier when having to install a few SlackBuilds, get sbopkg:
http://www.sbopkg.org/
 
1 members found this post helpful.
Old 10-05-2010, 10:16 AM   #8
Auzern
Member
 
Registered: Jul 2010
Posts: 44

Original Poster
Rep: Reputation: 0
Thanks a lot, brianL. I got it installed.
When I type exec wmii after logging out, I get wmii could not be displayed.
Why is that?

Last edited by Auzern; 10-05-2010 at 10:19 AM.
 
Old 10-05-2010, 10:30 AM   #9
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
You may wish to use `xwmconfig` to select wmii to start up when you run `startx`. This will require that wmii brought with it a xinitrc file for the /etc/X11/xinit directory (there's another directory that it might be but offhand I don't remember what it is) or that you create one.

Also, since you have dmenu installed, here's a tip that you might be interested in (or maybe not ):

Dmenu contains a file called /usr/bin/dmenu_path which contains some simple code for locating all the executables in your $PATH so it can display them. Unfortunately this can include some junk that you wouldn't want to run anyways. The bold code below I added to my /usr/bin/dmenu_path script to filter out some of the unwanted stuff:
Code:
cat "$CACHE" | sed -e '/\.old$\|\.OLD$/ d' \
                   -e '/\.bak$\|\.BAK$/ d' \
                   -e '/\.orig$\|\.ORIG$/ d' \
                   -e '/\.new$\|\.NEW$/ d' \
                   -e '/\~$\|^\[$/ d'
So adding the pipe (|) and those sed commands, you filter out a few odds and ends that might be in your $PATH which you don't want or need in your dmenu output.
 
Old 10-05-2010, 10:39 AM   #10
Auzern
Member
 
Registered: Jul 2010
Posts: 44

Original Poster
Rep: Reputation: 0
Thanks for the advice, GrapefruiTgirl. But I still get the error:
wmii : fatal. Can't be displayed. when I type in
Quote:
exec wmii
both as user and root
 
Old 10-05-2010, 10:44 AM   #11
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
That's probably because X is not running, most likely. The purpose of xinitrc files is so that when X starts (first), then your window manager is started second, after X is running. The `exec wmii` command is normally added to a xinitrc file.
If you're just trying to run wmii from the commandline it should not work.
Here's what I have on my system (I don't have wmii installed):
Code:
root@reactor: cd /etc/X11/xinit
root@reactor: ls -l
total 36
-rw-r--r-- 1 root root  321 Mar 16  2003 README.Xmodmap
lrwxrwxrwx 1 root root   10 Mar 22  2010 xinitrc -> xinitrc.i3
-rwxr-xr-x 1 root root  530 Feb  7  2010 xinitrc.blackbox
-rwxr-xr-x 1 root root  534 Feb 11  2010 xinitrc.fluxbox
-rwxr-xr-x 1 root root  539 Oct 25  2008 xinitrc.fvwm2
-rwxr-xr-x 1 root root 6087 Mar 14  2010 xinitrc.i3
-rwxr-xr-x 1 root root  627 Sep  3 05:33 xinitrc.kde
-rwxr-xr-x 1 root root  725 Dec  1  2009 xinitrc.twm
-rwxr-xr-x 1 root root  768 Feb 11  2010 xinitrc.wmaker
root@reactor:
so, there's a file for each window manager or DE on the system. The one that's a symlink, points to the one that belongs to the window manager you wish to start when you run `startx`.

NOTE: If you're using a login manager such as KDM, it should also have a drop-down menu where you can select what type of session you wish to run. wmii should be one of the selections if all is well.
 
Old 10-05-2010, 10:49 AM   #12
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Another idea (not sure it'll work though):

If you're already logged in and running a desktop or window manager, you *might* be able to do:
Code:
exec wmii -- :1

or 

exec wmii :1

or

DISPLAY=:1 exec wmii
or something like that, to start a second X session on another VT (if I remember right, usually it will start on VT8 or CTRL-ALT-F8). You would run the command NOT as root.

Last edited by GrapefruiTgirl; 10-05-2010 at 10:50 AM. Reason: added another possibility
 
Old 10-05-2010, 11:09 AM   #13
Auzern
Member
 
Registered: Jul 2010
Posts: 44

Original Poster
Rep: Reputation: 0
Thanks a lot for your support GrapefruiTgirl,
I tried the new commands that you wrote up and it did not work again.

Now I understood about the xinitrc file. So I cannot run a different window manager without making it my default but whereas with KDM Login Manager I can select a different one. Where can I get this then? I tried searching on sbopkg but no hope.
 
Old 10-05-2010, 11:24 AM   #14
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
To start a different window manager other than the one you're running, on a different display, may or may not work - I don't really know. I guess it's possible for them to fight over resources, but I really don't know. I do know that I have started both KDE and XFCE simultaneously on different displays and the results were VERY strange as I had parts of both things on both displays! It was really weird and mixed up.

To get KDM, you need to install (a large chunk of) KDE, which comes with Slackware already. You should have KDE if you did a full install or installed it initially. KDM is the KDE login manager. I haven't used that now for a long time, but by default, KDM gets started by /etc/rc.d/rc.4 if you choose to boot into runlevel 4.
 
Old 10-05-2010, 11:34 AM   #15
Auzern
Member
 
Registered: Jul 2010
Posts: 44

Original Poster
Rep: Reputation: 0
Oh I see. I guess you were lucky to have both running then

I have done a full install of Slackware with KDE4. But when I boot into Slackware, I just see the terminal, not the KDM. I want the KDM to show up but all I see is the terminal in which the processess start up and I have to type the login and password and then type startx.
What is this runlevel4 that you are talking about and how do I get my KDM to work so I can log in like a normal KDE user.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Window Maker - Your NeXT window manager LXer Syndicated Linux News 0 12-03-2009 08:50 AM
Beryl Window Manager / Emerald Theme Manager Not Changing With ATi Drivers. Z3R0o Linux - Desktop 2 01-07-2007 12:23 AM
What's the best X-Window System window manager in your opinion? t3gah Linux - Software 9 12-16-2006 11:10 PM
Change/add window manager to login manager kunalagon Debian 3 06-04-2006 04:33 AM
changing desktop manager and window manager Tux Red Hat 4 04-04-2006 02:56 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:48 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration