On 10/29/14 08:32, Phil Muldoon wrote:
On 29/10/14 14:26, Phil Muldoon wrote:
On 29/10/14 11:24, Phil Muldoon wrote:
On 29/10/14 10:31, 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"
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.
Could something like following work? Phil, can you try that?
Perhaps some toplevel Makefile* changes would be needed too.
>From a point of view of GDB, as long as in all scenarios above the .so
is available in the finished produce that is fine. I will test your
patch and report back.
I built with bootstrap enabled, and also disabled with this patch. In
both cases the .so is available. So it looks good. I also ran GDB
compile testcases against both .so's and all looks good there too.
Cheers
Phil
I forgot to ask, I am fine with this patch. I concur with Jakub that
building libcc1 as part of bootstrap is not needed. Does anyone else
object to removing libcc1.so from bootstrap?
Not at all... To a large degree libcc1 is driven by your needs, so if
you don't need the bootstrap, then let's remove it from bootstrap.
jeff
