Date: Sun, 19 May 2019 17:47:29 -0400 From: Ed Maste <emaste@freebsd.org> To: Yuri <yuri@rawbw.com> Cc: current <current@freebsd.org> Subject: Re: /usr/lib/libomp.so that was added in 13-CURRENT causes port failures and might conflict with libomp.so provided by devel/openmp Message-ID: <CAPyFy2AK60juP9kGvg3Z_%2B_SGjYo7nvp1y0GvDbFBTAFFJ92WQ@mail.gmail.com> In-Reply-To: <20781ff0-dc6c-de30-e286-f18e181077c3@rawbw.com> References: <20781ff0-dc6c-de30-e286-f18e181077c3@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 18 May 2019 at 22:23, Yuri <yuri@rawbw.com> wrote: > > Why was /usr/lib/libomp.so added to the base? It was added to the base because it's a runtime library required to support a feature provided by the base system compiler. Do you have an example of a failing port?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2AK60juP9kGvg3Z_%2B_SGjYo7nvp1y0GvDbFBTAFFJ92WQ>