Date: Wed, 20 Jan 1999 19:02:45 -0800 From: Mike Smith <mike@smith.net.au> To: "Marco van Hylckama Vlieg" <marco@windowmaker.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD include paths Message-ID: <199901210302.TAA05424@dingo.cdrom.com> In-Reply-To: Your message of "Thu, 21 Jan 1999 05:08:07 %2B0100." <199901210408.FAA10116@pc2-c804.uibk.ac.at>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hello all, > > I got a nagging question... > Very often when trying to compile packages I find myself editing > makefiles and having to add really obvious include paths like > /usr/local/include or /usr/X11R6/include in order to get the > package installed. > Now I wonder, why doesn't the system itself have these include paths > "enabled" by default? > Is there a way to fix these ever occuring annoyances when compiling > programs? You are probably building sources from Linux developers. The "correct" fix is to edit the Makefiles as you are doing, and point out to the package authors that it is not correct to assume that the system includes will be spammed with installed packages. > -- > QQWT!"^""9QQQ ------------------------------------------------ > QP' _%7? WindowMaker, the choice of a GNUstep Generation. Please trim your oversized and offensive signature file. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901210302.TAA05424>