Kövesdi György wrote:
I have rebuilt both binutils and gcc with this option, but the difference
is only that the building procedure requires the /opt directory on the host
machine with some system files, while the target does the same.
In addition, gcc does not find the system include files on the target machine.
This option seems to be bad. :-(
Maybe you should elaborate WHY you DON'T want to produce a normal native
GCC using configuration options like the :
--prefix=/usr
This is the assumed $prefix for a normal native GCC. The value you
give as $prefix has nothing to do with your "cross host", only with
the native (target) host on which you are going to install the produced
GCC.
Ok, a normal native GCC searches the normal '/lib', '/usr/include' and
'/usr/lib' for the "target C library", but whether a "custom" one like
yours will do that, is unclear... That $host = $target, should be the
only requirement for searching the "native places" but maybe some extra
options like '--with-as=' and '--with-ld=' can override this... But
every GCC searches also the '$prefix/$target' aka '$tooldir', the 'bin',
'include' and 'lib' there, so a custom GCC which DOESN'T want to use
the normal native places, could put its custom things there...
