On 10/29/2014 11:31 AM, Jakub Jelinek wrote:
> It would be nice to have libcc1 built just once, not bootstrap it, but
> it is a build module, is that possible?
> In toplevel configure.ac I'm seeing:
> host_tools="texinfo flex bison binutils gas ld fixincludes gcc cgen sid sim
> gdb gprof etc expect dejagnu m4 utils guile fastjar gnattools libcc1"
Stuff such as texinfo and flex is in host_tools just as a relic of the
old Cygnus tree.
fixincludes is in there for running it after installation.
The ones that matter in the common case are biuntils, gas, ld, gcc, gdb,
gnattools and of course libcc1.
> shouldn't libcc1 be in build_tools instead?
> I mean, it is a library meant to be dlopened by gdb and gcc
> plugin that uses that library, so in canadian-cross should be
> for the build target, where the resulting compiler will be run
> and where gdb will be run.
That is host, not build. Build is the system you are on.
Say you're cross-building a native mingw compiler and debugger:
build = i686-pc-linux-gnu
host = i686-pc-mingw (or whatever they use these days)
target = i686-pc-mingw
You cannot link build-libcc1 (for i686-pc-linux-gnu) into host-gcc or
host-gdb.
But you surely know this, so perhaps it's me who is missing something.
