From owner-freebsd-ports@FreeBSD.ORG Wed May 15 04:55:17 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 40C04FE8 for ; Wed, 15 May 2013 04:55:17 +0000 (UTC) (envelope-from dirk.meyer@dinoex.sub.org) Received: from uucp.dinoex.sub.de (smtp3.dinoex.sub.de [IPv6:2001:1440:5001:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9BBD48AD for ; Wed, 15 May 2013 04:55:16 +0000 (UTC) Received: from uucp.dinoex.sub.de (dinoex@uucp.dinoex.sub.de [194.45.71.2]) by uucp.dinoex.sub.de (8.14.5/8.14.5) with ESMTP id r4F4t2v6088812 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 15 May 2013 06:55:02 +0200 (CEST) (envelope-from dirk.meyer@dinoex.sub.org) X-MDaemon-Deliver-To: Received: from build8.dinoex.sub.de (dinoex@localhost) by uucp.dinoex.sub.de (8.14.5/8.14.5/Submit) with BSMTP id r4F4t2so088774 for ; Wed, 15 May 2013 06:55:02 +0200 (CEST) (envelope-from dirk.meyer@dinoex.sub.org) To: freebsd-ports@freebsd.org Message-ID: From: dirk.meyer@dinoex.sub.org (Dirk Meyer) Organization: privat Subject: Re: error on fvwm startup on 9.1-RELEASE Date: Wed, 15 May 2013 06:53:47 +0200 X-Mailer: Dinoex 1.79 References: <201305150023.r4F0MwVw046360@fire.js.berklix.net> X-Gateway: ZCONNECT build8.dinoex.sub.de [UNIX/Connect 0.94] X-PGP-Fingerprint: 44 16 EC 0A D3 3A 4F 28 8A 8A 47 93 F1 CF 2F 12 X-Copyright: (C) Copyright 2001 by Dirk Meyer -- All rights reserved. X-PGP-Key-Avail: mailto:pgp-public-keys@keys.de.pgp.net Subject:GET 0x331CDA5D X-ZC-VIA: 20130515000000S+2@dinoex.sub.org X-Milter: Spamilter (Reciever: uucp.dinoex.sub.de; Sender-ip: 194.45.71.2; Sender-helo: uucp.dinoex.sub.de; ) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (uucp.dinoex.sub.de [194.45.71.2]); Wed, 15 May 2013 06:55:03 +0200 (CEST) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2013 04:55:17 -0000 Hallo Julian H. Stacey, > Nor me either, I tried all this to narrow it down: > { > I tried fvwm -debug & ls -ltr /var/log > & tinkering with original RC file, & patching out bits of system.fvwmrc, > assuming something failing around It fails even with a very plain setup. > but no luck, I didn't persevere, as I noted: > cd /usr/ports/x11-wm/fvwm/files/ ; /bin/ls -1 | wc -l # 41 > cd /usr/ports/x11-wm/fvwm2/files/ ; /bin/ls -1 | wc -l # 2 > so wondered if you'd had problems feeding back to fvwm.org, & if I should > just move to fvwm2 & customise from there ? > > The buildlog doesn't differ enought. > Differ from what ? another earlier that works ? Buildlog on 8.3 (working) and 9.1 > The amd64 laptop I'm testing on has 3 boot partitions with 9.1-RELEASE, > 9.0-RELEASE & 8.3-RELEASE I just re-installed Version 1.24r on all > 3, & starting with both default /usr/local/lib/X11/fvwm/system.fvwmrc & > my customised system.fvwmrc, I am seeing the same problem on all 6 > combinations of 3 x OS-version x 2 x RC files : It may be a regression in some depedency ? USE_XORG= xbitmaps xpm xext x11 xmu As I don't have a problem on my FreeBSD 8.3 box with older X. > I took a quick look at various bits of http://fvwm.org/ > Should we ask there ? Or would answer just be "Try 2.x" Yes, 1.x ist "not supported" for some long time. kind regards Dirk - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany