I spotted the embedded profile in portage recently and decided to give it a try with crossdev. So I ran crossdev -t x86_64-gentoo-linux-uclibc -S and made /usr/x86_64-gentoo-linux-uclibc/etc/make.profile a symlink to /portage/portage.d/profiles/embedded .

In the meantime, I've relocated most of portage tree and components to /portage, just as follows:

The thing is I get this warning message everytime I compile a package for crossdev:

x86_64-gentoo-linux-uclibc-emerge dropbear:

!!! /usr/x86_64-gentoo-linux-uclibc/etc/make.profile is not a symlink and will probably prevent most merges.
!!! It should point into a profile within /portage/portage.d/profiles/
!!! (You can safely ignore this message when syncing. It's harmless.)

The error message doesn't actually reflect the condition that is checked:

Code:

profile_broken = not self.profile_path or \
not os.path.exists(os.path.join(self.profile_path, "parent")) and \
os.path.exists(os.path.join(self["PORTDIR"], "profiles"))

In this case the second condition is the problem: the embedded profile contains no "parent" entry, I assume it wasn't inteded to be used directly. Also checking the commit history I wouldn't expect that this profile is maintained anymore, the last real updates were about three years ago.

Aaaaah, Ok, now it sounds clear. Thanks Genone. Does that mean I can do whatever I want with that profile? Can I even create myself a profile for my embedded purposes?_________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root”

Thanks anyway Genone. Will try to figure it out on my own as much as I can._________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root”