Subject: =?UTF-8?Q?Re:_[alpine-devel]_Ad=c3=a9lie_on_Alpine=2c_two_months_la?=
 =?UTF-8?Q?ter?=
To: alpine-devel@lists.alpinelinux.org
References: <5975E0C0.1030008@adelielinux.org>
 <57A1A151-0352-40DA-BC91-52980CEE99C3@shiz.me>
 <20170725090742.61793ff2@vostro> <597739E9.9080006@adelielinux.org>
From: Breno Leitao <brenohl@br.ibm.com>
Date: Tue, 25 Jul 2017 12:10:34 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
Precedence: list
MIME-Version: 1.0
In-Reply-To: <597739E9.9080006@adelielinux.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Message-Id: <498c3b7f-0363-8236-ee97-625d4a0993c3@br.ibm.com>

Hello,

On 07/25/2017 09:30 AM, A. Wilcox wrote:
> How does one bootstrap a new distro?  Especially one with a slightly
> different triplet (i486-*, powerpc64-*, etc) than Alpine's, not to
> mention different configuration options?  Should I just build a new
> GCC and install it over the current one?
> 
> I figured running bootstrap.sh would be the quickest / easiest way to
> do that.  But maybe I was wrong.

That is what I found during the ppc64le bootstrap.

During the ppc64le bootstrap time, I tried two different strategies:

1) Cross-distro compile Alpine packages from Debian/ppc64le. This strategy
seemed better at that time, because I could have delayed or even avoid GCC
bootstrap. I.e, I was using Debian's GCC to compile Alpine's package, and I
would like to have compiled GCC from the inside an already created Alpine
rootfs, without doing the GCC bootstrap process.

Since Debian had Musl, it would not be a problem, I thought.

2) Use the bootstrap script and start on Alpine/x86 and starting build from
the begining, i.e, doing GCC bootstrap and moving up.

What I found later is that it was quite hard to avoid GLIBC contamination
during the cross-distro compilation process. I was never able to get rid of
the GLIBC symbols using the first strategy.

When I switched to the second strategy, it was much easier to find the
problem and solve them, seeing progress at every new bug.

Anyway, this was my personal experience, and, as you should expect, your
mileage may vary.



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---