From owner-freebsd-ports Sat May 16 19:51:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18536 for freebsd-ports-outgoing; Sat, 16 May 1998 19:51:14 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18510 for ; Sat, 16 May 1998 19:51:01 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id UAA18727; Sat, 16 May 1998 20:26:27 -0400 (EDT) Date: Sat, 16 May 1998 20:26:27 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@localhost To: Peter Haight cc: freebsd-ports@FreeBSD.ORG Subject: Re: Autoconf macro for finding include subdirectories In-Reply-To: <199805162143.OAA25724@wartch.rih.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 16 May 1998, Peter Haight wrote: > > >You can easily check where they install, by inspecting each port's > >pkg/PLIST. Usually, the installed directory is the one the library > >intends as a default, so other software that uses those libraries finds > >it easily. The installation is conditioned against the user's setting > >of PREFIX, because not everyone wants to use /usr/local. The only ports > >I've had problems with are the tcl ones, for reasons that are very well > >known. > > > >All ports that use those libraries are already set up to find the > >required libraries correctly, with no modifications at all, irregardless > >of local PREFIX settings, as long as those settings are stable on any > >particular machine. > > Ahh. The problem is not with other ports. The problem occurs when I'm > compiling something that is not in the port system. Also, I would like the > macro so I can send it to the authors of the program so that they can > include it in the next release. If that happens, then it is easier to > maintain the port since it will need less patches. >From what I've seen of configure scripts, they're all over the place (I mean they don't follow a standard too closely), usually with significant amounts of purely custom code in them. I don't know of a single macro that can be used in all situations (including significant amounts of custom code) to find whatever you want. I've done what you're referring to myself, but on a one by one basis. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message