X-Original-To: alpine-devel@lists.alpinelinux.org
Delivered-To: alpine-devel@mail.alpinelinux.org
Received: from mail-ea0-f173.google.com (mail-ea0-f173.google.com [209.85.215.173])
	(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
	(No client certificate requested)
	by mail.alpinelinux.org (Postfix) with ESMTPS id AE606DC0150
	for <alpine-devel@lists.alpinelinux.org>; Tue, 18 Jun 2013 05:53:55 +0000 (UTC)
Received: by mail-ea0-f173.google.com with SMTP id g15so2302204eak.4
        for <alpine-devel@lists.alpinelinux.org>; Mon, 17 Jun 2013 22:53:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=sender:date:from:to:cc:subject:message-id:in-reply-to:references
         :x-mailer:mime-version:content-type:content-transfer-encoding;
        bh=l+wtd1ZcX3laXvXSx7E/jOO99BmULBYUJEIjArHvR64=;
        b=IC/TM+hKTvrWjPXIte4M+GRCKLK9/h6BQLzDdnjFLSHWBqvaomrB5sqilZmab+jwOo
         3zYZ6Fa1H4SRRimb4uGSsIgkXanZtVpXopKdjW3MbSRtJTdBna7oXuE83B5Lp9KmJqhp
         s73CxZR6x8abym5LQQr9svBgLRBCmpYoNu2ePlj0MTRxxbNTb7SkzGHwRMmdpUSVOlpz
         oC9aYJu7yj3gqyV1pNSeiePrPC+7KHeBxwJ19DVPaF3nt496+XUUkNOsSXnf3WttUW13
         yJe1or50nO4wFpBFPrCVPAGfO2+cqcaBKgMkDrmN/H1PMZMfn+Xfd+eVjR7iisM2Ae/p
         okeA==
X-Received: by 10.14.215.197 with SMTP id e45mr20708986eep.130.1371534834049;
        Mon, 17 Jun 2013 22:53:54 -0700 (PDT)
Received: from vostro ([2001:1bc8:101:f402:21c:23ff:fefc:bf0b])
        by mx.google.com with ESMTPSA id p49sm5312218eeu.2.2013.06.17.22.53.53
        for <multiple recipients>
        (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
        Mon, 17 Jun 2013 22:53:53 -0700 (PDT)
Sender: =?UTF-8?Q?Timo_Ter=C3=A4s?= <timo.teras@gmail.com>
Date: Tue, 18 Jun 2013 08:53:59 +0300
From: Timo Teras <timo.teras@iki.fi>
To: Jim Pryor <dubiousjim@gmail.com>
Cc: Alpine <alpine-devel@lists.alpinelinux.org>
Subject: Re: [alpine-devel] Can't build apk-tools
Message-ID: <20130618085359.78d9215d@vostro>
In-Reply-To: <1371469130.31289.140661244826657.5DE65BF9@webmail.messagingengine.com>
References: <1371469130.31289.140661244826657.5DE65BF9@webmail.messagingengine.com>
X-Mailer: Claws Mail 3.9.1 (GTK+ 2.24.17; i686-pc-linux-gnu)
X-Mailinglist: alpine-devel
Precedence: list
List-Id: Alpine Development <alpine-devel.lists.alpinelinux.org>
List-Unsubscribe: 
	<mailto:alpine-devel+unsubscribe@lists.alpinelinux.org?subject=unsubscribe>
List-Post: <mailto:alpine-devel@lists.alpinelinux.org>
List-Help: <mailto:alpine-devel+help@lists.alpinelinux.org?subject=help>
List-Subscribe: 
	<mailto:alpine-devel+subscribe@lists.alpinelinux.org?subject=subscribe>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Mon, 17 Jun 2013 07:38:50 -0400
Jim Pryor <dubiousjim@gmail.com> wrote:

> On Mon, Jun 17, 2013 at 11:52:46AM +0300, Timo Teras wrote:
> > That's weird. Works here nicely. What gcc/libc you are using?
> > 
> > It might be due to using 'ld' and not 'gcc' for link. Or mixing
> > object files built with different gcc flags. Or gcc spec file
> > mismatching the libc build options.
> > 
> > Is your libc standard, or self-built with different config?
> 
> Thanks Timo.
> 
> I would have suspected a self-built toolchain and called it out. No,
> I'm using the gcc-4.7.3-r6 and libc-0.9.33.2-r22 binary packages from
> edge x86.
> 
> The only self-built packages I'm aware of on this machine (that are
> otherwise available on edge) are:
> 
>     busybox
>     cryptsetup
>     getmail
>     less
>     lynx
>     msmtp
>     mutt
>     ncurses
>     procmail
>     rxvt-unicode
>     syslinux
>     vim
>     xkeyboard-config
> 
> I can confirm that when I ssh to a pretty vanilla system (tracking
> alpine
> 2.6/x86_64), and do:
> 
>     $ git clone git://git.alpinelinux.org/apk-tools
>     $ cd apk-tools/
>     $ sudo apk add -t apk-make openssl-dev zlib-dev lua-dev
>     $ make clean
>     $ . /etc/abuild.conf
>     $ make
> 
> that does work fine, no errors. Wonder what the breaking difference
> is.
> 
> Well, if I figure it out, I'll report. If you have any
> ideas/suggestions, I welcome them.
> 
> On the problematic machine, changing LD to gcc in the Make.rules file
> no longer suffices to fix the issue. I think it used to do so, but
> I'm not sure of that---it's been a while since I last did this
> successfully.

How about uclibc-dev? Is that upstream or left broken from older
install?

The thing is that __stack_chk_fail_local is a special kind of symbol
that gcc inserts, and is expected to be linked in with the executable
(most _not_ be in a .so). Thus you will not find it
in /lib/libc.so.0.9.32 (or glibc .so either for that matter).

Instead, if you look at "/usr/lib/libc.so", it's a linker script
telling to link with the real .so and a set of nonshared static
objects, with uclibc, namely uclibc_nonshared.a. You should find
__stack_chk_fail_local in /usr/lib/uclibc_nonshared.a.

You might want to check that /usr/lib/uclibc_nonshared.a
and /usr/lib/libc.so come from uclibc-dev matching the libc0.9.32
installed. You could try "apk audit --system /usr/lib/*libc*" and/or
"apk fix uclibc-dev".

- Timo


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---