X-Original-To: alpine-devel@lists.alpinelinux.org Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) by lists.alpinelinux.org (Postfix) with ESMTP id D09C25C4154 for ; Sun, 3 Jul 2016 08:31:44 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1467534702; s=default; d=flatglobe.org; i=tmhoang@flatglobe.org; h=Date:From:To:Cc:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; l=2345; bh=QSWMSKBb7z9kwsVnCRQSBWhvMWwPEJxzZUz8kOdDZHQ=; b=U/ZKYiMfaCJbBdufPvaykB2rrFvaEMXINDxGuul1QGqixzeMwNtPfEZz/RII4wrr 8p8KHh3alZx3DrUzjLJEufFK98jhsrWkzJXM0v6oUJ773gD1knlyw+vdETRAdkaxz2Q fe0psh9sCkZ/xNotMbjTotSRZvHqQEdt1FVu8fbI= Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1467534702206563.901830921039; Sun, 3 Jul 2016 01:31:42 -0700 (PDT) Date: Sun, 03 Jul 2016 15:31:42 +0700 From: "Tuan M. Hoang" To: "Justin Cormack" Cc: "Alpine Devel List" Message-ID: <155afe2764a.10cb9409959067.3829969527295319337@flatglobe.org> In-Reply-To: References: <155a8e57d76.f37920c130996.6728092923369604578@flatglobe.org> Subject: Re: [alpine-devel] Porting Alpine scripts X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail Hi, The experimental Musl s390x port is at : https://github.com/koorogi/musl/tree/s390x Tuan ---- On Sun, 03 Jul 2016 12:41:20 +0700 Justin Cormack wrote ---- > I was not aware of a Musl s390x port, is there one? > Justin > > On 1 Jul 2016 4:57 p.m., "Tuan M. Hoang" wrote: > Hi, > > I am trying to create a Docker image of Alpine targeting s390x architecture. > > Natanael suggested me Timo's previous work at : http://dev.alpinelinux.org/~tteras/bootstrap/ to bootstrap Alpine on new arch. > > I have 2 questions related to this, hope you could shed some light. > > Q1: > Running createcross-toolchain.sh, at step 5, building gcc pass 2 : (experimenting with targeting x86) > > $ ABUILD_CONF=$ABUILD_CREATECROSS_CONF BOOTSTRAP=nolibc CTARGET_LIBC=musl abuild -r || return 1 > (this makes sure --disable-shared is passed to configure script) > > Then at step 6, it introduces a conflict between host's gcc and newly installed/built gcc-pass2-$CTARGET > > ERROR: unsatisfiable constraints: > gcc-5.3.0-r0: > conflicts: gcc-pass2-i486-alpine-linux-musl-5.2.0-r0[so:libcc1.so.0=0.0.0] > satisfies: g++-5.3.0-r0[gcc=5.3.0-r0] build-base-0.4-r1[gcc] > gcc-pass2-i486-alpine-linux-musl-5.2.0-r0: > conflicts: gcc-5.3.0-r0[so:libcc1.so.0=0.0.0] > satisfies: world[gcc-pass2-i486-alpine-linux-musl] > > How could I solve this? Should I build gcc-pass-2 with different prefix than /usr/ to avoid conflict dynamic libs? If I do so, will it be any different than a manually/traditionally built cross-toolchain ? (mentioned below) > > > Q2: > I have built a cross toolchains targeting s390x (gcc, musl, binutils, busybox, apk-tools), based on Gregor Richards's musl-cross with some patches. > If I specifies this cross toolchains in the crossbuild-alpine-bootstrap.sh , rather than doing > ${SUDO_APK} --repository $REPODEST_HOST/main add gcc-$CTARGET g++-$CTARGET gcc-gnat-$CTARGET || return 1 > > then will there be any differences ? I have not try this (havent have cross-built gnat yet) and just want to know what you think about it. > > Thank you, > Tuan > > > > --- > Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org > Help: alpine-devel+help@lists.alpinelinux.org > --- > > --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---