Date: Sat, 28 Jul 2001 11:10:57 -0400 (EDT) From: Sung Nae Cho <sucho2@quasar.phys.vt.edu> To: Eric Rivas <the_sawmill@worldnet.att.net> Cc: Gary Kline <kline@ns1.thought.org>, <stable@FreeBSD.ORG> Subject: Re: New windowmaker install bombs... Message-ID: <Pine.LNX.4.33.0107281023160.8125-100000@quasar.phys.vt.edu> In-Reply-To: <20010728100143.6ce1c06a.the_sawmill@worldnet.att.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Have you tried installing the traditional way? For example: Get the source tarball from where FreeBSD ports usually gets from, i.e., either go to ftp site and download the tarball yourself or simply do #make fetch unzip it Now, the tallball I received for Window Maker happers to be in bzip2 format. So, you'll do # bzip2 -cd WindowMaker-0.65.1.tar.bz2 | tar xvf - If you didn't know, this character above "|" is generated by pressing "SHIFT" + "\" You may have different keyboard! Now go into the unzipped directory and do this: #cd /home/distfiles/WindowMaker-0.65.1 #./configure && gmake && gmake install && gmake clean && gmake distclean Everything should be installed in /usr/local You are done! If you've never done this before, see ./configure options by typing #.configure -help If you want to place WindowMaker where the ports actually installs, then just go to the ports directory for WindowMaker and look at the Makefile. It specifies where the WindowMake dependencies are installed. In this case, you would do: #./configure --prefix=/usr/X11R6 --with-nlsdir=/usr/X11R6/share/locale --blah blah blah ------ you get the point! #gmake && gmake install && gmake clean && gmake distclean I normally use options in ./configure to disable things like native language support (nls) etc. You're done A note of caution for those wanting to install other windowmanagers like XFCE this way rather than using ports! This was is more advantageous when new version of XFCE is already out but the port isn't: Somehow, don't ask me why, FreeBSD places some crucial configuration files in odd locations (rather than that of traditional places) and renamed them. For example, the gtk-config and glib-config files. When you run the ./configure, it will get stuck when searching for gtk-config and glib-config file since FreeBSD renamed it as gtk12-config and glib12-config. So, create a link. gtk12-config is located in /usr/X11R6/bin/gtk12-config glib12-config is located in /usr/local/bin/glib12-config make link that way traditional ./configure understands where they are and give them the correct name, i.e., #ln -s /usr/X11R6/bin/gtk12-config /usr/X11R6/bin/gtk-config #ln -s /usr/local/bin/glib12-config /usr/local/bin/glib-config Hope this helps. Regards, Sung N. Cho, Saturday, July 28, 2001. Dept. of Physics, Virginia Polytechnic Institute & State University. On Sat, 28 Jul 2001, Eric Rivas wrote: > On Fri, 27 Jul 2001 20:55:48 -0700 > Gary Kline <kline@tao.thought.org> wrote: > > > On Fri, Jul 27, 2001 at 10:12:01PM -0400, Eric Rivas wrote: > > > On Fri, 27 Jul 2001 17:44:18 -0700 (PDT) > > > Gary Kline <kline@tao.thought.org> wrote: > > > > > > > > > > > Please excuse the slight OT note, but this is to > > > > whomever put up the latest windowmaker version. Because > > > > I'm going to run it on my DNS server--outside my firewall--I > > > > dropped in the new port virtually at once. It builds, but > > > > bombs with the make install. Maybe a bad patch... (?) > > > > > > > > Anyway, this heads-up to anyone who is considering up- > > > > revving. > > > > > > Take a look at PR 29224, is this what you are talking about? > > > > What do I use to look up|trac a bug? ...Can't seem to > > find the right utility. > > PR 29224: > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=29224 > > > > > > > > > Filed it the other day when I did a fresh install of FreeBSD. It > > > sucks since I'm reduced down to using the old package. > > > > > > > > > > > At any rate, I don't think this is what I was referring to, > > Something this afternoon (PDT) there was a posting to > > -security about a potentially dangerous bug in windowmaker. > > Plus a fix dated just today (27jul01). I cvsup's my ports' > > tree and retrieved the newest fixed version. > > Actually both the regular and i18n versions were fixed on Tuesday. > > > > > The new version builds without any serious err, but fails > > to install in the languages */*.po directory. I spent > > a few minutes trying to hack out the internationalization > > stuff. Failed; then send this note. (Only I flubbed and > > missent to -stable rather than -security.) > > > > Yeah that's exactly what I had. If you look at the pr, I have a snip > of the install output where it failed. I tried to track down the > error, but couldn't find it. > > Now at least I know it wasn't my fault it failed. > > > gary > > > > > > > > -- > > Gary D. Kline kline@thought.org www.thought.org Public > service Unix > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.33.0107281023160.8125-100000>