Date: Thu, 12 Jan 2006 12:35:33 +0100 (CET) From: Harti Brandt <hartmut.brandt@dlr.de> To: Peter Carah <pete@altadena.net> Cc: current@freebsd.org Subject: Re: Problem building new bsnmpd import on amd64 Message-ID: <20060112123435.B35349@beagle.kn.op.dlr.de> In-Reply-To: <43C625C2.2030208@altadena.net> References: <43C60A57.3040405@altadena.net> <20060112085736.L34596@beagle.kn.op.dlr.de> <43C625C2.2030208@altadena.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 12 Jan 2006, Peter Carah wrote: PC>Harti Brandt wrote: PC>> This should been fixed now (by building a shareable libdisk). PC>> PC>> harti PC>> PC> PC>I waited several days before sending this query, just in case a fix came in. PC>It didn't until late today (I cvsup'd this morning and it didn't come yet). PC> PC>Then why did it build just fine on i386, and fail (on my only 2 samples) only PC>on amd64. (I have a sparc64 but at the moment it doesn't run fbsd so I can't PC>tell if it matters there or not...) Perhaps the 32-bit arch only supports PC>relocations that are common between shared and not? Or that gcc doesn't try to PC>get too fancy? PC> PC>I do understand the fix and all, just curious as to why it didn't PC>matter on i386. It seems that amd64 relocation is different from, for example, sparc64 and doesn't allow to link non-pic static libraries into a shared object. harti
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060112123435.B35349>