Date: Thu, 03 Feb 2011 15:11:56 +0100 From: thierry@FreeBSD.org To: Rainer Hurling <rhurlin@gwdg.de> Cc: freebsd-ports@freebsd.org Subject: Re: net/mpich2: libraries with many 'undefined symbols' Message-ID: <20110203151156.24668evn6vl9o434@graf.pompo.net> In-Reply-To: <4D4AAB54.9030001@gwdg.de> References: <4D49C48A.7080604@gwdg.de> <20110202212907.GC29365@graf.pompo.net> <4D4A9559.2010502@gwdg.de> <20110203133557.33003e7j1xacsls0@graf.pompo.net> <4D4AAB54.9030001@gwdg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Selon Rainer Hurling <rhurlin@gwdg.de> le jeu 3 f=E9v 14:19:16 2011 : > Ok, so I usually have to take care to link libraries like libmpl, =20 > libopa etc. in addition to libmpich (or using the wrappers if =20 > possible). Yes, this is the idea. Note: libopa is rarely needed. >>>> Yet another solution could be to configure mpich2 with >>>> --enable-lib-depend, but this is experimental... > > What would be the consequence of configuring mpich2 with =20 > --enable-lib-depend? Would dependencies like libmpl be more =20 > integrated in libmpich? This is based on inter-library dependencies. This is experimental and only for shared library builds at this time. It causes libmpich.so to depend on libmpl.so and libopa.so. Once you do that, you can just link to libmpich.so, and it'll automatically pick the remaining libraries as needed. Remark: these explanations come from the authors. --=20 Th. Thomas.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110203151156.24668evn6vl9o434>