🚀 go-pugleaf

I think GCC_EXEC_PATH is not used reasonably when cccp (version 2.1) is
searching for include files. Suppose I have compiled gcc for a few
different targets. I have not changed the default built-in paths as I'll
probably install the compilers and related files there later. For the
moment I have, however, installed them for testing under my home
directory.

The stuff is in directories $HOME/lib/gcc-lib/<target>/<version>, which
contain the compiler proper, c preprocessor, gcc library and include
directory. To compile programs for different targets I set
GCC_EXEC_PREFIX to $HOME/lib/gcc-lib and use the -b switch to specify
the target architecture for gcc. This works fine, except for cpp.

gcc adds <target>/<version> to the GCC_EXEC_PREFIX, so the right
utilities and libraries are used. However, cpp just modifies the normal
include directories from the default

   /usr/local/lib/gcc-lib/<target>/<version>/include

to

   $GCC_EXEC_PREFIX/include

and all the include files for different targets are searched for from
the same location. Wouldn't it be more useful to transform the default
path(s) to something like

   $GCC_EXEC_PREFIX/<target>/<version>/include?

I can circumvent this problem by setting C_INCLUDE_PATH to
$HOME/<target>/<version>/include, but it's a bit annoying to change that
every time you want to compile for a different target. And obviously
GCC_EXEC_PREFIX is intented just for this.

Would it be reasonable to change the behaviour of cccp? Has anyone done
it yet (patches, newer version)? Or have I set up my system poorly?

-- 
                                                               no sig today