Date: Tue, 15 Oct 1996 22:38:56 -0500 (CDT) From: Rich Murphey <rich@rich.isdn.bcm.tmc.edu> To: chuckr@glue.umd.edu Cc: asami@FreeBSD.org, torstenb@FreeBSD.org, ports@FreeBSD.org Subject: Re: xpm static library Message-ID: <199610160338.WAA25404@richc.isdn.bcm.tmc.edu> In-Reply-To: <Pine.OSF.3.95.961015225609.8007B-100000@modem.eng.umd.edu> (message from Chuck Robey on Tue, 15 Oct 1996 23:00:04 -0400 (EDT))
next in thread | previous in thread | raw e-mail | index | archive | help
|Date: Tue, 15 Oct 1996 23:00:04 -0400 (EDT) |From: Chuck Robey <chuckr@glue.umd.edu> |cc: torstenb@FreeBSD.org, rich@FreeBSD.org, ports@FreeBSD.org | |On Tue, 15 Oct 1996, Satoshi Asami wrote: | |> Remember I complained a while back that the xpm port didn't build |> static the static library anymore? I found out that it's because |> config/bsdLib.rules in XFree86-3.1.2 betas don't define ForceNormalLib |> to YES anymore. |> |> Rich, is this going to be a permanent change? If so, we need to |> adjust the ports accordingly. | |Just let me jump in here a moment. All that stuff is controlled by |FreeBSD.cf, which we really ought to get some chance to tweak, you know. |Before it becomes a regular part of a distribution is the right time to |consider it. | |One possibility is to ask that a site.def file be sited in OUR |/usr/share/mk directory, so we could get our own meathooks on part of the |config. Yep, FreeBSD.cf would be the ideal place to '#define ForceNormalLib YES' specificly for FreeBSD. Would that fix it? Rich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610160338.WAA25404>