Date: Sat, 02 Feb 2002 16:39:10 -0800 From: Andy Sparrow <spadger@best.com> To: "Vance Shipley" <vances@motivity.ca> Cc: wm-user@windowmaker.org, stable@freebsd.org Subject: Re: [wm-user] wdm Message-ID: <20020203003910.143283E22@CRWdog.demon.co.uk> In-Reply-To: Your message of "Sat, 02 Feb 2002 16:58:12 EST." <PDEDKJGEMCIGOPBCALMFAEDBCFAA.vances@motivity.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
>
> Has anyone been able to get wdm-120 working with FreeBSD 4.5-STABLE
> and windowmaker-0.80.0?
Yes, using it right now:
andy@omni[191]-> pkg_info | grep wdm
wdm-1.20 WINGs Display Manager; an xdm replacement
andy@omni[192]-> pkg_info | grep windowmaker
windowmaker-0.80.0 GNUStep-compliant NeXTStep window manager clone
andy@omni[193]-> uname -a
FreeBSD omni.geek4food.org 4.5-RC FreeBSD 4.5-RC #75: Sun Jan 20 01:49:17 PST
2002 root@omni.geek4food.org:/usr/src/sys/compile/tureg i386
> One thing I found was that wdm-1.20 was being linked against
> libPropList. I removed that as from what I see it only needs
> to be linked against libWINGS. That removed this error message
> in the xdm-error.log:
>
> wdmLogin error: could not open domain file /root/GNUstep/Defaults/wdmLogin
> for reading: no such file or directory
>
> I am still getting:
>
> Caught signal 11.
>
> Server aborting
>
> I slo get this message on the console:
>
> sigreturn: eflags = 0x13207
Ahhh. Now I've seen this (or something very similar, couldn't swear to the
exact hex sigreturn) a couple of times myself, and I never found out quite
what caused it.
Searching the FreeBSD archives never turned up anything (which is why I just
cross-posted the reply, in case someone else goes looking).
However, I did find out that it was basically caused by something in the
system being out-of-date. Which, as I cvsup all the time and don't necessarily
re-build the ports, isn't too surprising...
In one instance, rebuilding WindowMaker, WDM & all the ports that it depended
on sorted it out. Another time, I had to completely rebuild *all* the ports
(doing the above plus X and a whole bunch of other stuff didn't sort it out,
so I did a pkg_delete `pkg_info | awk '{print $1}'` and started again).
I can only assume that something was stale in the system, and this was causing
the problem.
> Any help would be greatly appreciated.
Vance, 'portupgrade' is your friend, if you've not looked at it, I can
heartily recommend it. It rocks.
My advice would be to pick a good moment to CVSup the complete source tree,
ports and all, go through the regular 'buildworld', 'buildkernel',
'mergemaster' cycle, and, having freshly rebooted into a good, clean, running
system, install 'portupgrade' if you don't have it already, fix up your ports
database and rebuild the whole lot.
At the end, the whole system will be squeaky clean, and every single port on
the system will be rebuilt with the new binaries, libraries, updated to the
latest versions etc. All that remains would be to rebuild any ports you happen
to prefer to build with custom options, and you're all done.
Works for me, every time.
HTH.
Cheers,
AS
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: Exmh version 2.5 07/13/2001
iD8DBQE8XIatPHh895bDXeQRAkkQAJ4/rrgNVAFkZIKOJHu5Gn9dcpg89ACglna4
5ztftQBVZkNkAv89rwV24/I=
=Ankh
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020203003910.143283E22>