Date: Thu, 18 Mar 2004 09:36:53 +0100 From: Burkard Meyendriesch <bm@malepartus.de> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-ports@freebsd.org Subject: Re: amd64 -CURRENT: portinstall x11/kde3 fails, missing shared libraries Message-ID: <20040318093653.4a9d0356.bm@malepartus.de> In-Reply-To: <20040318070424.GA77223@xor.obsecurity.org> References: <20040318075835.6a2618bd.bm@malepartus.de> <20040318070424.GA77223@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 17 Mar 2004 23:04:24 -0800 Kris Kennaway wrote: > On Thu, Mar 18, 2004 at 07:58:35AM +0100, Burkard Meyendriesch wrote: > > > Are there any differences in making ports between i386 STABLE and > > amd64 CURRENT? What is going wrong? What can I do to solve this? > > Compare the build logs of the openldap port from i386 and amd64; it's > possible the build is turning off shared library support because of a > buggy configure script, or something. > I have got the same problem with several other libraries on my amd64 box. Here is the relevant difference in config.log between Grimbart (i386 STABLE) and Reineke (amd64 CURRENT) when making libiconv: --- config.log (Reineke) --- LIBICONV='/usr/local/lib/libiconf.a' --- config.log (Grimbart) --- LIBICONV='/usr/local/lib/libiconf.so -Wl, -rpath -Wl, /usr/local/lib' I think this difference is the problem on Reineke. How is LIBICONV generated during the make process? Which part of Reinekes configuration is the reason that it does not make the shared libraries? Burkard -- Burkard Meyendriesch Stevern 2 D-48301 Nottuln
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040318093653.4a9d0356.bm>