X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id F3255DC00F5 for ; Mon, 17 Jun 2013 17:24:16 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 381C520CEE for ; Mon, 17 Jun 2013 13:24:16 -0400 (EDT) Received: from web3.nyi.mail.srv.osa ([10.202.2.213]) by compute3.internal (MEProxy); Mon, 17 Jun 2013 13:24:16 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date; s=smtpout; bh=2JFLqBh1qJ9KZIgGZEbo5/8xfWI=; b=tWH/OoKTmoWhx8xEMRN7z4X8gJvA lQi+KHacjMCmaNEFJjTDEWwhI+b/Gh5sRFvawrBHfybzgeFTQjWu6oCnBY6ipi7q gWYLgahveqp+bxc4P/CmSS3IkX2w+M5XD6sd8XkrPNgUeYb+mXJhtA3vYVyCanDI macNL48A/4S20OI= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 102B6B00E7F; Mon, 17 Jun 2013 13:24:16 -0400 (EDT) Message-Id: <1371489856.6397.140661244965361.6D282B28@webmail.messagingengine.com> X-Sasl-Enc: OKWm+NZKvoXvzEM9cyGdNCm++pJawn77ZVXCWz7LG7zh 1371489856 From: Dubiousjim To: Alpine X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - html Subject: Re: [alpine-devel] Can't build apk-tools Date: Mon, 17 Jun 2013 13:24:16 -0400 On Mon, Jun 17, 2013 at 03:55:44PM +0200, Natanael Copa wrote: > On Sun, 16 Jun 2013 20:47:22 -0400 > Dubiousjim wrote: > > > I'm a bit perplexed how to build apk-tools by hand, either using > > aports/abuild, or using git://git.alpinelinux.org/apk-tools. Some months > > ... > > > but that didn't seem to be enough. I'd still get a bunch of linking > > errors about "undefined reference to `__stack_chk_fail_local'". > > I would guess this comes from that your libc does not have SSP enabled > and your gcc is hardened. Yeah, that's a natural hypothesis. But I didn't custom build that libc, it's straight from the edge/x86 repo. And indeed: $ nm -D /lib/libc.so | fgrep stack_chk 0000bc15 T __stack_chk_fail I'm guessing this shows that the libc has ssp, though perhaps I'm wrong. --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---