Re: native vs emulated configuration

On Sat, 9 Jul 2011 11:17:58 +0200
Johannes Schauer <[email protected]> wrote:

> It is because of fakechroot. A symlink you create like this:
> 
> sudo chroot mychroot ln -s /foo bar

Have you tried:

ln s /foo ./bar
or 
ln -s ./foo ./bar

?

Alternatively, skip the chroot command completely and create the
symlink from outside. A simple chdir(); ln -s ./foo ./bar

That is eminently solvable - multistrap already does something similar
for the guard_lib64 routine.


> This problem is of course not showing up with multistrap tarball
> creation, as a real chroot call is used to configure the rootfs on
> native architectures.

Multistrap creates tarballs for any architecture, independent of
whether any configuration has taken place.

-- 


Neil Williams
=============
http://www.linux.codehelp.co.uk/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk4YIKMACgkQiAEJSii8s+MgXgCfRI0Rap6YFdHPHSEh2gOFqFXU
ILAAoOE7URCnC1B8sLw669WTHUcYi0Mu
=CaCa
-----END PGP SIGNATURE-----