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 95F0D5C4152 for ; Fri, 1 Jul 2016 23:57:41 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1467417460; s=default; d=flatglobe.org; i=tmhoang@flatglobe.org; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; l=1759; bh=QwKHZfuciFbSJMCaQpkovJwwS5yBdtNG3Vp04qCXN8I=; b=AOrSudLWxZzA0jvAnnOFvDu3A2f42jh8kyIJS+DDGcaV3iMVDbPjtpBsKR2jLWxv 6B6mMbHa6DM0odCHiXM/AxawA+ZclUAjJMkeMrEXwJYaWM5VKhySjFkH5UJ3b+pDD00 v9FQt/V4SM5KVtqxWoDUxlXXSHzj7rYW6GWQIOJQ= Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1467417460138542.5889297277864; Fri, 1 Jul 2016 16:57:40 -0700 (PDT) Date: Sat, 02 Jul 2016 06:57:40 +0700 From: "Tuan M. Hoang" To: "alpine-devel" Message-ID: <155a8e57d76.f37920c130996.6728092923369604578@flatglobe.org> Subject: [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, 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 ---