| View previous topic :: View next topic |
| Author |
Message |
mcc2
n00b
Joined: 06 Sep 2012
Posts: 25
|
 Posted: Thu Nov 29, 2012 7:16 pm Post subject: Beaglebone: Cross-eix-sync...how? |
 |
|
Hi,
setting up a crosscompiling toolchain, with which it is possible
to crosscompile software and to emerge software for the NFS-mounted
rootfs of my beaglebone was successful.
But there is one thing left:
Since I still have to natively eix-sync on my beagle, I want to know:
How can I cross-emerge-sync with this setup?
Thank you very much in advance for any help!
Best regards,
mcc |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54209
Location: 56N 3W
|
| Posted: Thu Nov 29, 2012 8:22 pm Post subject: |
|
|
mcc2,
You share /usr/portage over NFS too.
My Raspberry Pi has the following /etc/fstab | Code: | # <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/mmcblk0p1 /boot vfat noauto,noatime 1 2
192.168.10.30:/var/armv6j / nfs noatime 0 0
192.168.10.30:/usr/portage /usr/portage nfs noatime 0 0
/dev/mmcblk0p2 none swap sw 0 0
/dev/mmcblk0p3 /home ext2 noatime,nodev 0 0
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0
#/dev/fd0 /mnt/floppy auto noauto 0 0
devpts /dev/pts devpts defaults 0 0 |
The NFS host has the following /etc/exports
| Code: | # /etc/exports: NFS file systems being exported. See exports(5).
#/usr/armv6j-hardfloat-linux-gnueabi 192.168.100.0/24(rw,no_root_squash,no_all_squash,async,no_subtree_check)
# root fs for Raspberry Pi
/var/armv6j 192.168.10.0/24(rw,no_root_squash,no_all_squash,async,no_subtree_check)
# shared portage and distfiles between host and Raspberry Pi
# packages is in /usr/packages to avoid arch collisions
/usr/portage 192.168.10.0/24(rw,no_root_squash,no_all_squash,async,no_subtree_check) |
So far so good /usr/portage is the same filesystem on both the Pi (ARM) and the NFS host (amd64). But you need to take care with /usr/portage/packages. That must not be shared, as You won't want a mix of host and target binary packages there. On both systems you must move /usr/portage/packages out of /usr/portage. The are some statements in make.conf to do that.
Now when youon either system, the portage tree is updated for them both.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gentoo on Alternative Architectures
