Rich Felker

Oh, I missed that we already have it there and you just changed it. Uhg. I don't like having that at all, but at least the old version was just...

Maybe something like ``` find obj_kernel_headers/usr/include -name '*.h' -exec sh -c 'for i ; do f=${i#obj_kernel_headers/usr/} && mkdir -p obj_kernel_headers/staged/${f%/*} && cp "$i" obj_kernel_headers/staged/"$f" ; done' {} + ```

That's a good question. The original intent was that you could use relative paths, but I don't think it works right now. I guess I should either find a way...

You would use `--with-sysroot` not `--with-build-sysroot` for this, but I don't have any idea if it will work - mcm is not setup to be installed like that, and it's...

> I attempted to compile with `--with-sysroot` however to no avail; the target directory was still present in the output directory. Is there any other option which can possibly build...

Yes, mcm can also cross-compile native compilers for your target, and in this case they don't have the cross directory structure you're unhappy with. You need to already have the...

`NATIVE=y` is not part of `COMMON_CONFIG`. The latter is a variable containing gcc/binutils configure options. It's its own make variable. Just add a line `NATIVE=y` in `config.mak` or put it...

Are you using a weird shell or shell config that affects non-interactive shells? I'm not sure where this is coming from but it looks like it might be from an...

It's intended that you can control these variables from the command line or environment, so scrubbing them would be breaking.

Yeah, I was just thinking the same - we should probably document the env/make vars that are used.