Message-ID: <4A74B26C.9060708@renta.net>
Date: Sun, 02 Aug 2009 07:23:56 +1000
From: Mark Constable <markc@renta.net>
User-Agent: Thunderbird 2.0.0.22 (X11/20090719)
Precedence: list
MIME-Version: 1.0
To: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] Attempting x86_64 build
References: <4A73EA4D.7030204@renta.net> <1249119848.19561.1282.camel@localhost.localdomain> <4A743B8E.4090309@renta.net> <4A745D80.6090005@iki.fi>
In-Reply-To: <4A745D80.6090005@iki.fi>
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable

Timo Ter=E4s wrote:
> I'm still thinking that bootstrapping should be doable without
> apk-tools. It is generally used by abuild for checking build
> dependencies and updating the index. Neither should be needed
> while bootstrapping the tool chain.

Yes, checking not yet existing apk dependencies and indexes
just makes it that much harder.

> "make static" and you should get apk.static binary in src directory.

Too easy, thanks, that probably saved me quite a bit of googling.

> Abuild is just scripts so that should be ok.

Except it depends on openssl which I'm having trouble building...

 cc -o abuild-tar -lssl -lcrypto -ldl -lz   abuild-tar.c
 abuild-tar.c:19:25: error: openssl/evp.h: No such file or directory

> No test system yet (except an oldish amd64 desktop machine). However,
> a script to produce it would be of high interest for me.

 git clone git://git.buildroot.net/buildroot
 cd buildroot
 make menuconfig
 make

When I get a working .config I'll make an APKBUILD but it may
require a "real" glibc based build chain which is, FWIW, why I
am putting effort into x86_64 first, so I can install a "real"
system if need be and more easily use the likes of buildroot to
bootstrap ARM (then perhaps PPC and MIPs, if I don't go crazy).

--markc


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---