Date: Thu, 03 Feb 2011 19:07:23 +0100 From: Rainer Hurling <rhurlin@gwdg.de> To: thierry@FreeBSD.org Cc: freebsd-ports@freebsd.org Subject: Re: net/mpich2: libraries with many 'undefined symbols' Message-ID: <4D4AEEDB.6030700@gwdg.de> In-Reply-To: <20110203151156.24668evn6vl9o434@graf.pompo.net> References: <4D49C48A.7080604@gwdg.de> <20110202212907.GC29365@graf.pompo.net> <4D4A9559.2010502@gwdg.de> <20110203133557.33003e7j1xacsls0@graf.pompo.net> <4D4AAB54.9030001@gwdg.de> <20110203151156.24668evn6vl9o434@graf.pompo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03.02.2011 15:11 (UTC+1), thierry@FreeBSD.org wrote: > Selon Rainer Hurling <rhurlin@gwdg.de> le jeu 3 fév 14:19:16 2011 : > >> Ok, so I usually have to take care to link libraries like libmpl, >> libopa etc. in addition to libmpich (or using the wrappers if 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 >> --enable-lib-depend? Would dependencies like libmpl be more 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. Ahh, ok. I had assumed that. Since it is experimental until now I think it is a bit risky to use it. Thank again. > Remark: these explanations come from the authors.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D4AEEDB.6030700>