From owner-freebsd-ports@FreeBSD.ORG Thu Feb 3 18:07:26 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08F93106566B; Thu, 3 Feb 2011 18:07:26 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by mx1.freebsd.org (Postfix) with ESMTP id B89AE8FC17; Thu, 3 Feb 2011 18:07:25 +0000 (UTC) Received: from p57918d94.dip.t-dialin.net ([87.145.141.148] helo=krabat.raven.hur) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Pl3aW-0001J1-3Y; Thu, 03 Feb 2011 19:07:24 +0100 Message-ID: <4D4AEEDB.6030700@gwdg.de> Date: Thu, 03 Feb 2011 19:07:23 +0100 From: Rainer Hurling User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; de-DE; rv:1.9.2.13) Gecko/20101218 Thunderbird/3.1.7 MIME-Version: 1.0 To: thierry@FreeBSD.org 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> In-Reply-To: <20110203151156.24668evn6vl9o434@graf.pompo.net> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: freebsd-ports@freebsd.org Subject: Re: net/mpich2: libraries with many 'undefined symbols' X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2011 18:07:26 -0000 On 03.02.2011 15:11 (UTC+1), thierry@FreeBSD.org wrote: > Selon Rainer Hurling 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.