DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:from:to:cc:in-reply-to:references:content-type:date
         :message-id:mime-version:x-mailer:content-transfer-encoding;
        b=vsrmFeq90L6ypiLehC+zEw+9m+OYEJa7lFkP/yrL2dxGrzIecA3WOEngsGEuDFEC3e
         brI8bMqTHjwF//dA4sfT+1dB1zFTccjU76pfJWdlJunrB/noD63vdHI5fO4ylYjXsjwx
         Mythdbdqqahl1dmbmBq5Hc6bp82LSfom+d9gk=
Subject: Re: [alpine-devel] Attempting x86_64 build
From: Natanael Copa <natanael.copa@gmail.com>
To: Mark Constable <markc@renta.net>
Cc: Timo =?ISO-8859-1?Q?Ter=E4s?= <timo.teras@iki.fi>,  alpine-devel@lists.alpinelinux.org
In-Reply-To: <4A76AD4A.4040700@renta.net>
References: <4A73EA4D.7030204@renta.net>
	 <1249119848.19561.1282.camel@localhost.localdomain>
	 <4A743B8E.4090309@renta.net> <4A745D80.6090005@iki.fi>
	 <4A74B26C.9060708@renta.net> <4A7544F9.8030602@iki.fi>
	 <4A76AD4A.4040700@renta.net>
Content-Type: text/plain
Date: Mon, 03 Aug 2009 11:49:39 +0200
Message-Id: <1249292979.12941.9.camel@localhost.localdomain>
Precedence: list
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Mon, 2009-08-03 at 19:26 +1000, Mark Constable wrote:
> After another 48 hours of hair pulling I managed to compile openssl
> then abuild and now apk-tools.

wow! cool!

> root@br_x86_64 ~/main/apk-tools/apk-tools-2.0_pre17 make
>   CC      src/add.o
>   CC      src/apk.o
>   CC      src/archive.o
> src/archive.c:50: error: expected specifier-qualifier-list before 'uint16_t'
...
> Adding stdint.h to src/archive.c seemed to fix the above, also,
> this is a from apk-tools too (fwiw)...

Committed that upstream (the apk-tools git repo)


> gcc -std=gnu99  -march=x86-64 -mtune=generic -O2 -pipe  -Wl,--as-needed -o tar buffer.o checkpoint.o compare.o create.o delete.o extract.o xheader.o incremen.o list.o misc.o names.o sparse.o suffix.o system.o tar.o transform.o update.o utf8.o ../lib/libtar.a /usr/lib/libintl.a /usr/lib/libc.so -Wl,-rpath -Wl,/usr/lib
> ../lib/libtar.a(utimens.o): In function `gl_futimens':
> utimens.c:(.text+0x6c): warning: the use of LEGACY `utimes' is discouraged, use `utime'
> ../lib/libtar.a(close-stream.o): In function `close_stream':
> close-stream.c:(.text+0x17): warning: This version of __fpending returns bytes remaining in buffer for both narrow and wide streams.  glibc's version returns wide chars in buffer for the wide stream case.
> 
> ***
> 
> To get openssl to compile I resorted to adding the missing ftime()
> (a googled hack, not the real thing) directly to apps/speed.c...
> 
> int ftime(struct timeb *tp)
> {
>   time_t fix;
>   time(&fix);
>   tp->time=fix;
>   tp->millitm=tp->timezone=tp->dstflag=0;
> 
>   return 0;
> }

probably a uclibc config opt.

> 
> ***
> 
> Now, I'm still getting some segfaults but it seems I can start to use
> the apk/abuild tools to *start* installing some packages. A question
> though is what should be the first most important, say, 2 dozen packages
> and in what order should I try to build them?

the toolchain (binutils, gcc, linux-headers, uclibc)

tools that help you build stuff:
diffutils, make, bison, flex, perl, autoconf, automake, pax-utils (used
by abuild to trace dynamic deps), file, busybox*, apk-tools, alpine-*,
openrc

Then you should have a working vserver (bootable system without kernel)
that can build stuff for you.


thanks!

-nc



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---