Subject: Re: [alpine-devel] Bunch of questions about Alpine's gcc package

From: Dubiousjim <[email-masked]>
Date: Sun, 19 May 2013 09:48:56 -0400

On Sun, May 19, 2013 at 01:08:29PM +0200, Natanael Copa wrote:
> On Fri, 17 May 2013 13:07:20 -0400
> Dubiousjim <[email-masked]> wrote:
> 
> I'll try answer some of the more questions you had...

Thanks Natanael for these prompt, careful, and very helpful replies.

It helps me understand some things better, and I'll make some changes to
my cross-compiling instructions. Maybe I'll wait until buildroot-2013.05
final is released (currently at rc2), and update everything then.

The instructions I've used so far are now live in the wiki, here:

http://wiki.alpinelinux.org/wiki/ArchLinux_install_inside_an_Alpine_chroot
http://wiki.alpinelinux.org/wiki/Cross-Compiler_targeting_Alpine

I'm still writing up the instructions for actually cross-compiling GHC.

> I could mention that when we did the NPTL bootstrapping we used
> crosstool-ng rather than buildroot. Main reason was that buildroot does
> (did?) not provide us with a native gcc.

Right, buildroot still doesn't put a native gcc or development headers
and the like into the images. I'm just using the cross-compiling
toolchain it constructs, and ignoring the images. (That is, I'm just
using the stuff underneath $buildroot_dir/output/host, not the stuff
under the other directories in output/.)

I had tried crosstools-ng initially, but got stymied by something. That
was too many iterations ago to remember what it was. I don't even
remember if I got the cross-compiler to work, but then had trouble using
it to build GHC, or didn't even get the first step completed.

Perhaps now that I understand Alpine's native toolchain better, and have
more experience setting up a cross-compiler, I'd be able to use
crosstools-ng more successfully.

-- 
[email-masked]

---
Unsubscribe:  [email-masked]
Help:         [email-masked]
---