On 20 June 2016 at 23:15, Joel Holdsworth
wrote:
> Even so, there is still the issue of the other glibc environment variables -
> see my LANG= example of the parent-guest wanting to run a child-guest
> Japanese, but the child-qemu should still run in English.
That particular example is easy in th
On 20/06/16 22:40, Peter Maydell wrote:
On 20 June 2016 at 22:27, Joel Holdsworth
wrote:
The current behaviour was quite unexpected to me - there were no warnings,
and the need to link qemu statically isn't documented anywhere. If you
really believe that static linking is the best answer here,
On 20 June 2016 at 22:27, Joel Holdsworth
wrote:
> The current behaviour was quite unexpected to me - there were no warnings,
> and the need to link qemu statically isn't documented anywhere. If you
> really believe that static linking is the best answer here, then shouldn't
> the shared library o
On 20/06/16 21:29, Laurent Vivier wrote:
Le 20/06/2016 à 21:51, Joel Holdsworth a écrit :
On 15/06/16 20:59, Laurent Vivier wrote:
Le 14/06/2016 à 21:26, Joel Holdsworth a écrit :
Previously, when emulating execve(2), qemu would execute a child
instance of the emulator with the environment va
Le 20/06/2016 à 21:51, Joel Holdsworth a écrit :
> On 15/06/16 20:59, Laurent Vivier wrote:
>>
>> Le 14/06/2016 à 21:26, Joel Holdsworth a écrit :
>>> Previously, when emulating execve(2), qemu would execute a child
>>> instance of the emulator with the environment variables provided by
>>> the p
20.6.2016 22.51 Joel Holdsworth
kirjoitti:
>
> On 15/06/16 20:59, Laurent Vivier wrote:
> >
> > Le 14/06/2016 `a 21:26, Joel Holdsworth a ecrit :
> >> Previously, when emulating execve(2), qemu would execute a child
> >> instance of the emulator with the environment variabl
On 15/06/16 20:59, Laurent Vivier wrote:
Le 14/06/2016 à 21:26, Joel Holdsworth a écrit :
Previously, when emulating execve(2), qemu would execute a child
instance of the emulator with the environment variables provided by
the parent process. This caused problems with qemu if any of the
variabl
Le 14/06/2016 à 21:26, Joel Holdsworth a écrit :
> Previously, when emulating execve(2), qemu would execute a child
> instance of the emulator with the environment variables provided by
> the parent process. This caused problems with qemu if any of the
> variables affected the child emulator's be
Previously, when emulating execve(2), qemu would execute a child
instance of the emulator with the environment variables provided by
the parent process. This caused problems with qemu if any of the
variables affected the child emulator's behaviour e.g.
LD_LIBRARY_PATH.
This patch solves this issue
