From owner-freebsd-questions Sun Apr 23 12:55:42 2000 Delivered-To: freebsd-questions@freebsd.org Received: from corinth.bossig.com (mail.dohboys.com [208.26.253.10]) by hub.freebsd.org (Postfix) with ESMTP id BD69137B90D for ; Sun, 23 Apr 2000 12:55:38 -0700 (PDT) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (unverified [208.26.241.252]) by corinth.bossig.com (Rockliffe SMTPRA 4.2.1) with ESMTP id ; Sun, 23 Apr 2000 12:59:52 -0700 Message-ID: <39035533.DFA9C453@3-cities.com> Date: Sun, 23 Apr 2000 12:55:31 -0700 From: Kent Stewart Organization: Columbia Basin Virtual Community Project X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Trevor Johnson Cc: Walter Brameld , freebsd-questions@FreeBSD.ORG Subject: Re: how to burn References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Trevor Johnson wrote: > > > I just tried building cd-write from the ports collection which was > > cvsup-ed before I started, and main.cc says it can't find the include > > file c++tk.h. Any clues as to where this can be? > > One of these might turn it up: > > % grep c++tk.h /usr/ports/x11-toolkits/*/pkg/PLIST > % locate c++tk.h > % find /usr/include/ /usr/local/include/ -name c++tk.h This is a documentation problem. There was always an example on find that had something like {}\; that would do a find and then execute a command. You could start at / and look for '-name "*.h*"' and then do your grep. I don't have this documented in "man find" and there are times when I need to do this. Find won't look in a tarball and there are times when you would like to do that. This is probably one of them. I couldn't find the file on my system either. I also looked at /usr/X11R6 because it is a X11 gui cd-burner. I'm assuming there is a x11-toolkit that such as tk-8.2.3 that hasn't linked their includes properly at this point. > > If the fileis provided by another port, then the cd-write port should > depend on that other, and the maintainer of the cd-write port would > probably like to know about the problem. I have found a few of these lately. It is amazing what happens when you forget to add things that everyone already has on their system. Bison is a new one at 4.0 but everyone usually has automake and autoconf on their system. Code Crusade has problems this way and so did LessTif but it was fixed by a recent commit. They don't get fixed unless we pass the problems on to the maintainer. Kent -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message