From owner-freebsd-current Tue Feb 22 1:41:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 518E437B5F0; Tue, 22 Feb 2000 01:41:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA33904; Tue, 22 Feb 2000 01:41:05 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Martin Cracauer Cc: jdp@FreeBSD.ORG, peter@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: "Interesting" failure mode for static linking with shared libs. In-reply-to: Your message of "Tue, 22 Feb 2000 09:01:42 +0100." <20000222090142.A29249@cons.org> Date: Tue, 22 Feb 2000 01:41:05 -0800 Message-ID: <33901.951212465@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As a workaround for a static binary, you should be able to use > -Xlinker -Bstatic > instead of > -static Actually, it appears that just -Xlinker is necessary; it works fine in conjunction with -static. Thanks for this most helpful tip! I can see a *lot* of scenarios where I'll be using -Xlinker in the future. I didn't even know about that flag. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message