From owner-freebsd-ports  Sun Jan 12 18:04:39 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id SAA10965
          for ports-outgoing; Sun, 12 Jan 1997 18:04:39 -0800 (PST)
Received: from dfw-ix9.ix.netcom.com (dfw-ix9.ix.netcom.com [206.214.98.9])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA10960
          for <freebsd-ports@freebsd.org>; Sun, 12 Jan 1997 18:04:35 -0800 (PST)
Received: from baloon.mimi.com (sjx-ca80-02.ix.netcom.com [206.214.107.34]) by dfw-ix9.ix.netcom.com (8.6.13/8.6.12) with ESMTP id SAA22508; Sun, 12 Jan 1997 18:03:52 -0800
Received: (from asami@localhost) by baloon.mimi.com (8.8.4/8.6.12) id SAA03901; Sun, 12 Jan 1997 18:03:24 -0800 (PST)
Date: Sun, 12 Jan 1997 18:03:24 -0800 (PST)
Message-Id: <199701130203.SAA03901@baloon.mimi.com>
To: adam@veda.is
CC: freebsd-ports@freebsd.org
In-reply-to: <199701121444.OAA13704@veda.is> (message from Adam David on Sun, 12 Jan 1997 14:44:01 +0000 (GMT))
Subject: Re: x11/XFree86 install barfs
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * More to the point, if some port installed /usr/local/include/X.h recently
 * and this is in error, then it would be worth fixing if not already.

I'm not sure about this (it's ImageMagick btw), X include files are
usually referenced as <X11/*.h>, so it shouldn't cause a problem.  The 
X build is broken (I agree with your other mail), it shouldn't put
-I/usr/local/include in front of its own include dir anyway.

We need someone to filter these things back to the XFree86 people.
Any takers?

I just wish you looked at the error message you're sending in a little 
more so I don't have to point out the obvious to start the
conversation. :)

Satoshi