From owner-freebsd-questions@FreeBSD.ORG Sun Apr 15 16:23:24 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EAC3C16A401 for ; Sun, 15 Apr 2007 16:23:24 +0000 (UTC) (envelope-from odilist@sonic.net) Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by mx1.freebsd.org (Postfix) with ESMTP id D801813C48A for ; Sun, 15 Apr 2007 16:23:24 +0000 (UTC) (envelope-from odilist@sonic.net) Received: from [192.168.1.2] (69-12-157-6.dsl.dynamic.sonic.net [69.12.157.6]) by a.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id l3FGNOiT025192 for ; Sun, 15 Apr 2007 09:23:24 -0700 From: Oliver Iberien To: freebsd-questions@freebsd.org Date: Sun, 15 Apr 2007 09:23:25 -0700 User-Agent: KMail/1.9.5 References: <200704080930.14965.odilist@sonic.net> <20070409042415.GA2530@xor.obsecurity.org> In-Reply-To: <20070409042415.GA2530@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704150923.25792.odilist@sonic.net> Subject: Grep and --exclude? or, finding a text string that might be anywhere X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Apr 2007 16:23:25 -0000 I need to find a reference to an obscure delete port that is in some file somewhere (in /usr/ports/? somewhere in /usr?) as it is messing up make and, among other things, preventing me from running the gnome upgrade script. So, I do what little I know to do: grep -R /usr/* "any2dvd" This brings out a few valid discoveries (mostly in mailfiles when I posted about this) and lots of "operation not supported" and "No such file or directory" errors before grep spits out a "memory exhausted" error. If I could at least stop it from looking at */tmp/* and ~/.kde it might have a chance to get somewhere, but I can't figure out how --exclude or --exclude-dir work, despite googling over and over for examples. Can this be made to work? Or is there a better way? Thanks, Oliver Previous post about the weird make error follows: On Sunday 08 April 2007 21:24, you wrote: > On Sun, Apr 08, 2007 at 09:30:14AM -0700, Oliver Iberien wrote: > > I seem to have messed something up somewhere, and peculiar instructions > > seem to have found their way in. An example is below: > > > > ---> Checking for the latest package of 'devel/gettext' > > ---> Fetching the package(s) for 'gettext-0.16.1' (devel/gettext) > > ---> Fetching gettext-0.16.1 > > /var/tmp/portupgradeJwjg3x7H/gettext-0.16.1.tb100% of 2093 kB 248 kBps > > ---> Downloaded as gettext-0.16.1.tbz > > ---> Identifying the package > > /var/tmp/portupgradeJwjg3x7H/gettext-0.16.1.tbz ---> Saved as > > /usr/ports/packages/All/gettext-0.16.1.tbz > > ---> Skipping libiconv-1.9.2_2 (already installed) > > ---> Found a package > > of 'devel/gettext': /usr/ports/packages/All/gettext-0.16.1.tbz > > (gettext-0.16.1) > > ---> Located a package version 0.16.1 > > (/usr/ports/packages/All/gettext-0.16.1.tbz) > > ---> Upgrading 'gettext-0.14.5_2' to 'gettext-0.16.1' (devel/gettext) > > using a package > > cd: can't cd to /usr/ports/multimedia/any2dvd > > "Makefile", line 54: Could not > > find /usr/ports/print/cups-lpr/../../print/cups/Makefile.common > > make: fatal errors encountered -- cannot continue > > ^C---> Backing up the old version > > ---> Uninstalling the old version > > > > The section > > > > cd: can't cd to /usr/ports/multimedia/any2dvd > > "Makefile", line 54: Could not > > find /usr/ports/print/cups-lpr/../../print/cups/Makefile.common > > > > appears often when installing both from packages and ports. I just stop > > it and the install continues. What could be going on here? > > Check carefully for local changes you made referring to this file (in > /usr/ports or /etc/make.conf, maybe elsewhere_. It no longer exists > in the ports tree so it is unreferenced in a standard install of it. > > Kris