[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: native vs emulated configuration

On Sat, 9 Jul 2011 11:17:58 +0200
Johannes Schauer <j.schauer@email.de> 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
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

Attachment: pgp0bcz3hGxrC.pgp
Description: PGP signature

Reply to: