Using crosstool-0.27

[Daniel Kegel]

Tim Connors wrote:
> As per the request in the crosstool-howto, here is a note stating that
> I've successfully used crosstool to create an arm cross toolchain.
> 
> I'm sure this has been done many times.  I wouldn't have posted
> here except that, in my case, I also built with the java frontend.
> I'd like to report that java works in addition to c and c++.

Excellent!  Ever since reading that recent essay about the future of Gnome,
I've been meaning to add gcj support to crosstool, thanks for the
nudge.

> Java wouldn't compile with the straight binutils-2.14.  I googled the
> error message and found that binutils-2.14.90.0.5 would fix the
> problem. 

Arm in general doesn't like binutils-2.14; crosstool-0.28-pre1 already
reverted to 2.14.90.0.5 as you suggest.

> Note the addition of BUILD_JAVA=yes.  To use this flag, I also changed
> crosstool.sh to modify the "--enable-languages" option of configure.

I'll probably just give the user total control over the languages
in a single variable, rather than using a special variable for Java...


> To further accommodate java, I also hacked mkjail.sh.  Note addition
> of libgcj in list.
> 
> 	$ diff mkjail.sh mkjail.sh.org
> 	39c39
> 	<  ld libBrokenLocale libSegFault libanl libc libcrypt libdl libgcc_s libgcc_s_nof libgcj libm \
> 	---
> 	>  ld libBrokenLocale libSegFault libanl libc libcrypt libdl libgcc_s libgcc_s_nof libm \

OK, thanks.

> Experiences:
> 
> As usual, wget (from getandpatch.sh) won't work through a firewall 
> without a proxy.  It might be nice to remind users that
> 	$ export http_proxy=<proxy_host>:<port>
> will fix this.  Or maybe work it into the scripts or .dat files.

Will do, thanks.

> Since I don't have rcp nor rsh available on my REMOTE, crosstest.sh
> wouldn't work.  But it did show me the recipe to manually create,
> transfer and install the chroot environment.

I've never had a target that came with rcp or rsh, either, so I always
build 'em myself.
doc/chroot-login-howto.html does documents how to set up rsh,
and contrib/testsetup/pkg-rsh.sh is a working script I used in the past
to actually cross-build an rsh and rcp for the target.

> I was initially confused while studying crosstest.sh.  In order to run
> mkjail.sh you need the argument jail_etc_passwd.  That argument seems
> to be acquired from root@REMOTE:/jail/etc/passwd.  Yet the directory
> root@REMOTE:/jail/ (let along any file in it) won't even exist till
> after initjail.sh is run on REMOTE.  That doesn't happen until later
> in crosstest.sh.  If you already have a jail on REMOTE, it works, but
> the first time around I'm not sure.

Indeed, it only works if you've already set up the jail directory
containing the passord file.  This kind of made sense since
you really have to test the remote jail by hand while setting it up,
and crosstest.sh kind of assumes you've done that and made sure the
remote jail is working.

Are you actually trying the regression tests?  Cool!
- Dan

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com