Date: Fri, 12 Jun 2020 21:08:06 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 247212] net/openmpi: make pkgconfig files accessible Message-ID: <bug-247212-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D247212 Bug ID: 247212 Summary: net/openmpi: make pkgconfig files accessible Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Keywords: easy, patch, patch-ready Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: danilo@FreeBSD.org Reporter: cmt@freebsd.org Flags: maintainer-feedback?(danilo@FreeBSD.org) Assignee: danilo@FreeBSD.org Created attachment 215496 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D215496&action= =3Dedit move openmpi pkgconfig files in standard location currently (net/openmpi 4.3.0) the whole port, including pkgconfig (.pc) fil= es, is installed under /usr/local/mpi/openmpi/. This makes the pkgconfig files (/usr/local/mpi/openmpi/libdata/pkgconfig/*.pc) hard to access (standard pkgconfig needs fiddling with environment variables, with cmake this feels hackish). As proof I present the ports which are not using pkgconfig but are passing openmpi libs and other paths as variables from the port Makefile. By simply moving the .pc files to their standard location (/usr/local/libdata/pkgconfig/) correct usage of openmpi gets much easier. Attached patch fixes that, passes poudriere and the results have been verif= ied against cad/freecad (I can drop the mpi path fiddling from freecad). Consum= ers of openmpi do not have to change right now - the actual openmpi software and locations haven't been changed. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-247212-7788>