This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH, CFT] Fix bootstrap with in-tree ISL

On 1 April 2015 at 17:55, Bernhard Reutner-Fischer
<> wrote:
> On 1 April 2015 at 17:53, Tobias Grosser <> wrote:
>> On 04/01/2015 05:09 PM, Bernhard Reutner-Fischer wrote:
>>> Hi,
>>> Trying to build for current trunk.
>>> The box is a stable debian (7.8 it seems) so the OS' ISL is too old
>>> thus i was attempting to use in-tree ISL.
>>> When using an in-tree ISL gcc attempts to determine if it is recent
>>> enough and AFAIU fails to do so since the system's ISL (which we will not
>>> use)
>>> might be too old and the in-tree ISL is not yet built.
>>> set and thus compilation of graphite-isl-ast-to-gimple.c fails with
>>> "template with C linkage".
>>> The attached seems to get me past compilation of
>>> graphite-isl-ast-to-gimple.c with for e.g.
>>> alpha-linux-gnu
>>> I'm scheduling a proper regstrap on x86_64-linux-gnu for a native
>>> compiler but this will take days to start i fear.
>>> So.. if somebody has spare cycles.. :)
>> Hi Bernhard,
>> I can not give an OK for the makefile/configure changes, but in general this
>> seems to be the right direction.
> It seems that the in-tree ISL is not configured nor built upon make
> all-gcc, so libbackend linking fails as it stands. Will have a closer
> look..

The "problem" above was that isl/configure was not generated (automatically).
Is the toplevel Makefile supposed to do that or is the user
responsible for running something like autoreconfig -i in the isl/
subdir before a toplevel make in such a combined tree?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]