Re: Using the cross built toolchain

[Thomas Schwinge]

Hello!

On Mon, Nov 26, 2007 at 11:15:24PM +0530, Shakthi Kannan wrote:
> 1. I have copied the built toolchain to /usr/local/hurd (without the
> src/ directory), and have been able to build simple hello world file
> with the toolchain using a standalone Makefile.

Ah, we can simply copy the whole tree to another location and it'll
continue to work?  That's fabulous!  This means that there are no
hard-coded (absolute) paths inside GCC and friends?


> The Makefile is available here:
> http://shakthimaan.com/downloads/hurd/toolchain/Makefile
> 
> Kindly upload the Makefile to the wiki.

I will have a look at that during the next days.

> Can the toolchain be made
> available at the wiki site for others to try it?

Not from the wiki site, but I just saw that I (and other people) got
permission to host such things from GCC-project-privided development
machines, where I have an account on.  I will set-up an automatic
toolchain builder upon there and have the results be downloadable as
`tar.gz's.  Or even as `dpkg' (for GNU/Linux) packages, if someone
teaches me the needed Debian magic.


> 2. The same toolchain has been used to build an autotools source code
> package (gnumach), using the following steps from the sources
> top-level directory:
> 
>     export CC=/usr/local/hurd/bin/i586-pc-gnu-gc
>     export LDFLAGS=-L/usr/local/hurd/sys_root/lib
>     ./configure --host=i586-pc-gnu
>     make

Is explicitly setting `LDFLAGS' really needed?  Also, setting `CC'
shouldn't be needed if `i586-pc-gnu-gcc' can be found in `$PATH'.


> 3. To test the built target files, I used Debian GNU Hurd image with
> qemu. Follow this tutorial to build the image:
> http://eyeside.net/hurd/Hurd-on-QEMU.html
> http://www.bddebian.com/~wiki/hurd/running/qemu/

> You can transfer the files to the image by mounting it locally:

What I use in such cases is QEMU's facility to create FAT file systems
on-the-fly: ``qemu [...] -hdc fat:[somewhere]''.  The Hurd `fatfs'
translator is read-only, but for testing executables (etc.) that is
enough.  And it is much easier than loop-mounting the file systems
images.  (Also you don't need `root' rights.)

This would also be worth adding to some wiki page, I'd say.


Regards,
 Thomas

signature.asc
Description: Digital signature