names crossdev instance

Pipeng · Tux's lil' helper Joined: 23 Jul 2013 Posts: 117

Hi all! I has been looking how to do multiple corssdev instances, for the same arch, but I want to change some optimization params to create a binhost, the idea is support several devices, all of them x86_64-pc-linux-gnu but with different compiler and cpu options, but in the docs we can only found a way to create a instance using the objetive architecture as name, so following that I can't found how to create two instances of the same arch.....

Some one has any idea how to create a crossdev instance with a custom name?

Thx!

NeddySeagoon · Posted: Tue Jul 02, 2024 7:03 pm Post subject:

Pipeng,

What arch are you building on and what arch are you building for?

Are you sure you need crossdev?
That's for using arch A to build for arch B.
e.g. Using a big hairy amd64 box to build for a Raspberry Pi, which as arm/arm64

You may want multiple chroot instances.

They can all share the same $PACKAGES dir as long as you are careful with the FEATURES settings.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

Pipeng · Tux's lil' helper Joined: 23 Jul 2013 Posts: 117

mm, I could use it, I just does not want to depends on chroot for this, if I want to create a new onw for Raspeberry or ARM, be able to know how to do it, is also for fun.

I know I does not needs crossdev, I could just do it with just chroot.

Still want to play with crossdev!

rn to achieve this I has two issues, one as I wrote, is be able to create crossdev names instances.
Second, how to build and install the kernel from the server.

NeddySeagoon · Posted: Wed Jul 03, 2024 7:47 am Post subject:

Pipeng,

You may not use crossdev to build for the host arch it will run on.
In that case, the cross compiler would overwrite pieces of the native compiler and nothing would work.

There is a small wart here.
If your build host is amd64 with a /no-multilib/ install, you can use crossdev to build 32 bit x86 code
That works as amd64 /no-multilib/ cannot build 32 bit code, so you don't break your host install.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

Pipeng · Tux's lil' helper Joined: 23 Jul 2013 Posts: 117

I thought corssdev has a way to isolate each space to work.

If is possible to break the host with it, seems it not the case.....

Also I tryied to create a env for the same host, the result was just an error saying we can't do that, we can only create different instances to the current host.

NeddySeagoon · Posted: Wed Jul 03, 2024 6:43 pm Post subject:

Pipeng,

Crossdev builds cross toolchains that run on the <HOST> and emit code for the <TARGET>
It creates 'empty' target root directories of the name /usr/<tuple>, like /usr/aarch64-unknown-linux-gnu, /usr/armv6j-unknown-linux-gnueabihf and so on.

Toolchains where <HOST> == <TARGET> are not permitted.
Crossdev checks and will not let you destroy your HOST toolchain. That's a chroot case.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.