Documentation on Crossdev

[freshy98]

I got a second (though very small, literally) desktop a while a go, and emerged crossdev on it.
Now I only know the "old" crossdev and knew how to use that one, but the new version seems te work differently.

I tried looking for documentation on how to use it's command lines to build a kernel crossdev, but I can't figure out how.

Can anyone tell me where to find documentation, or at least tell me how to built a kernel creator?
This way I can finally start testing out my O2 RM7000 with recent kernels again.
Also, my Qube2 could use an upgrade on it's kernel I think...

Anyways, thanks in advance!

[egberts]

It should easy as doing

Code: Select all

# cd /usr/portage/sys-devel/gcc
# ebuild /usr/portage/sys-devel/gcc-x.x.x.x.ebuild compile
# cd /var/tmp/portage/gcc-x.x.x/work/gcc-x.x.x
# ./configure --target=mips-rm7000-linux-gnu
# make
# make install

Check your /usr/local/bin for mips-rm7000-linux-gnu-gcc

You may want to check Dan Kegel's crosscompile website...

[egberts]

Sorry for the last post... for KERNEL build, you will need to download a MIPS-tweaked linux tarball.

Then just use

Code: Select all

#make menuconfig

to select the specific MIPS platform.

Sometime, you can edit the Makefile and force the ARCH=mips and set the CROSSCOMPILE=mips-rm7000-linux-gnu

[freshy98]

I know about getting a MIPS linux tarball etc, but I need to know how to built the toolchain using crossdev.
Sorry about the confusion there.

With the older version it was something like:

Code: Select all

crossdev --arch=mips --kernel --gcc-version=something etc etc

I was missing most of the options in the resent version.

[egberts]

I use ptxdist-0.10 to get all my cross-environment needs (root file system, toolchains, kernels and applications).

It is not yet gentoo... but it is arguably the closest thing one can get up and quick for a complete cross-compile build environment.

[Redhatter]

I got a second (though very small, literally) desktop a while a go, and emerged crossdev on it.
Now I only know the "old" crossdev and knew how to use that one, but the new version seems te work differently.

I tried looking for documentation on how to use it's command lines to build a kernel crossdev, but I can't figure out how.

Can anyone tell me where to find documentation, or at least tell me how to built a kernel creator?
This way I can finally start testing out my O2 RM7000 with recent kernels again.
Also, my Qube2 could use an upgrade on it's kernel I think...

Anyways, thanks in advance!

crossdev --help tells all.

Code: Select all

beast ~ # crossdev --help
Usage: crossdev [options] --target TARGET

Options:
    --b, --binutils ver   Specify version of binutils to use
    --g, --gcc ver        Specify version of gcc to use
    --k, --kernel ver     Specify version of kernel headers to use
    --l, --libc ver       Specify version of libc to use
    -C, --clean target    Uninstall specified target
    -b, -d, -p, -v, -q    Options to pass to emerge (see emerge(1))
Stage Options:
    -s0, --stage0         Build just binutils
    -s1, --stage1         Also build a C compiler (no libc/C++)
    -s2, --stage2         Also build kernel headers
    -s3, --stage3         Also build the C library (no C++)
    -s4, --stage4         Also build a C++ compiler [default]
Extra Fun (must be run after above stages):
    --ex-only             Skip the stage steps above
    --ex-gcc              Build extra gcc targets (gcj/ada/etc...)
    --ex-gdb              Build a cross gdb

Target (-t):   takes the form: ARCH-VENDOR-OS-LIBC
    Run 'crossdev -t help' for examples

So in other words... you're after... crossdev -s1 -t mips64-unknown-linux-gnu for your O2's cross compiler, and crossdev -s1 -t mipsel-unknown-linux-gnu for your Qube2's cross compiler (or mips64el... 64-bit works too).

For the Qube2, if you want to save yourself some time updating the kernel, I have a binary for 2.6.16.4 on my devspace -- see my site below. I've also got an R5000 O2 kernel there, but I'm not sure how compatable that is with RM7000 (being the rare beasts that they are).

[freshy98]

Then that's what changed. No longer a --kernel but a -s1 for a C compiler etc.

I will build the RM7K kernel myself. Got some config files for it here somewhere...
The Qube2 is my firewall, so I need to make lots of changes probably. I also got a config for that one ofcourse.
Not sure what the binary gives me here. Don't use Linux too much.

The R5K kernel won't work on RM7K at all. Been there, done that.
I just wanna see if SCSI finally work, since that was what the main problem was about 1.5 years ago.