X-Original-To: alpine-devel@lists.alpinelinux.org
Delivered-To: alpine-devel@mail.alpinelinux.org
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44])
	(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
	(No client certificate requested)
	by mail.alpinelinux.org (Postfix) with ESMTPS id EB542DC00F5
	for <alpine-devel@lists.alpinelinux.org>; Mon, 17 Jun 2013 08:52:44 +0000 (UTC)
Received: by mail-ee0-f44.google.com with SMTP id c13so1620907eek.17
        for <alpine-devel@lists.alpinelinux.org>; Mon, 17 Jun 2013 01:52:43 -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=gQXTPBrsvRUFWWSJBANWRNtNyCOf3FaWG1YQNJYvWvM=;
        b=lrUGRAc3JsG8ZTCAg4jXrdcQBvkXXcxT+4iuFz/M4NheYyCxSAxaUBb3HoOQIcWdZI
         UTJavPIxfVYWVs2XpwZbYL99VssnvOeIUKwAyxkC/ldXs2klpDkGgKJqaM7SGr3tOac2
         tbt51QaDWHVgc/r29pmup5K6xjtz8O7Nyj30pZC8wIXKVEgggFA3uVxnpJ/BB0pyGM4Q
         hV68GqMixgMXydB8LyiAqo48UObcsSIg04E68DGCN1bsnIbWQqygY1wjLZsGAqdVNW6k
         GuMUAjevIAhoX7vDANNcRetm3wnqefsI7mwhabAyUF7xMmd2TII0evoDW5/O/SIFddVC
         1V7w==
X-Received: by 10.14.7.2 with SMTP id 2mr15729680eeo.145.1371459163334;
        Mon, 17 Jun 2013 01:52:43 -0700 (PDT)
Received: from vostro ([83.145.235.194])
        by mx.google.com with ESMTPSA id cg12sm9397420eeb.7.2013.06.17.01.52.42
        for <multiple recipients>
        (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
        Mon, 17 Jun 2013 01:52:43 -0700 (PDT)
Sender: =?UTF-8?Q?Timo_Ter=C3=A4s?= <timo.teras@gmail.com>
Date: Mon, 17 Jun 2013 11:52:46 +0300
From: Timo Teras <timo.teras@iki.fi>
To: Dubiousjim <lists+alpine-devel@jimpryor.net>
Cc: Alpine <alpine-devel@lists.alpinelinux.org>
Subject: Re: [alpine-devel] Can't build apk-tools
Message-ID: <20130617115246.03ea7b89@vostro>
In-Reply-To: <1371430042.8931.140661244660849.588C3DA9@webmail.messagingengine.com>
References: <1371430042.8931.140661244660849.588C3DA9@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 Sun, 16 Jun 2013 20:47:22 -0400
Dubiousjim <lists+alpine-devel@jimpryor.net> 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 ago, I noticed that the aports/abuild method would work but
> doing "make" in a git repo wouldn't. I made sure to invoke make using
> the same CFLAGS and LDFLAGS that are set in my /etc/abuild.conf:
> 
> CARCH=x86
> CBUILD=i486-alpine-linux-uclibc
> CHOST=$CBUILD
> CTARGET=$CHOST
> export CFLAGS="-Os -fomit-frame-pointer"
> export CXXFLAGS="$CFLAGS"
> export CPPFLAGS="$CFLAGS"
> export LDFLAGS="-Wl,--as-needed"
> 
> 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'".
> Googling suggested that the problem may be connected to the fact that
> LD is set to "ld" in apk-tools' Make.rules file, rather than to
> "gcc". It also suggested disabling stash-smashing protection with
> -fno-stack-protector. That didn't seem to be the right final
> solution, but by using one of these or the other, I was able to build
> from a git repo. As I said, at this point going to main/apk-tools in
> an aports tree and saying "abuild -r" worked fine.

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?



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