On Wed, Dec 12, 2012 at 12:59 AM, Etienne Le Sueur elesu...@vmware.com wrote:
Hi Richard,
Thanks for your reply.
The sysroot of /dev/null is basically to force the user or build system to
pass a valid --sysroot argument. This helps us to ensure that we only link
against known libraries
Hi Richard,
Thanks for your reply.
The sysroot of /dev/null is basically to force the user or build system to pass a valid --sysroot argument. This helps us to ensure that we only
link against known libraries (that are in a specific location) and there isn't any leakage from the host system.
On Mon, Dec 3, 2012 at 9:03 PM, Etienne Le Sueur elesu...@vmware.com wrote:
First ping... anyone?
A sysroot of /dev/null does not sound like something that we should support.
If we do the semantics of this setting should be documented somewhere.
Richard.
On 28/11/12 1:21 PM, Etienne Le Sueur
First ping... anyone?
On 28/11/12 1:21 PM, Etienne Le Sueur wrote:
Hi,
With a sysroot of /dev/null, passing a .i file to cc1plus causes it to attempt to open /dev/null/usr/include, which fails. This causes
problems for ccache and distcc. There is an open bugzilla ticket at [1].
The patch
Hi,
With a sysroot of /dev/null, passing a .i file to cc1plus causes it to attempt to open /dev/null/usr/include, which fails. This causes problems
for ccache and distcc. There is an open bugzilla ticket at [1].
The patch below applies on to 4.6.3, but it appears the bug is still present in
