From owner-freebsd-ports  Thu Sep 10 12:38:26 1998
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA07342
          for freebsd-ports-outgoing; Thu, 10 Sep 1998 12:38:26 -0700 (PDT)
          (envelope-from owner-freebsd-ports@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07290;
          Thu, 10 Sep 1998 12:38:17 -0700 (PDT)
          (envelope-from gj@FreeBSD.org)
From: Gary Jennejohn <gj@FreeBSD.ORG>
Received: (from gj@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id MAA21938;
	Thu, 10 Sep 1998 12:38:16 -0700 (PDT)
Date: Thu, 10 Sep 1998 12:38:16 -0700 (PDT)
Message-Id: <199809101938.MAA21938@freefall.freebsd.org>
To: sfarrell@healthquiz.com, gj@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG
Subject: Re: ports/7861
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: xemacs20 port fails to build

State-Changed-From-To: analyzed-closed
State-Changed-By: gj
State-Changed-When: Thu Sep 10 12:36:43 PDT 1998
State-Changed-Why: 
Quoting Steve Farrel:
(whoops, that's Farrell !)

I think this has to do with lesstif, actually.  If I config w/o motif
(--with-dialogs=athena), then all ok... i think lesstif-0.86.0 was
built with gcc28 inadvertantly, and that this is causing the problem
(though xscreensaver uses the new lesstif w/o any problems, so
??)--this is just a hunch.

no reason to leave this open.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message