Tobias Burnus wrote:
Now that CLooG is no longer used by GCC, it makes sense to also remove it from
the main configure file. Especially as the in-tree build currently only works
if also CLooG is available.
Turned out that I missed a dependency. One previously had all-gcc ->
depends on all-cloo
On Wed, Nov 12, 2014 at 11:27 AM, Tobias Burnus
wrote:
> On Tue, Nov 11, 2014 at 02:01:47PM +0100, Tobias Burnus wrote:
>> Now that CLooG is no longer used by GCC, it makes sense to also remove it
>> from
>> the main configure file. Especially as the in-tree build currently only works
>> if also
On Tue, Nov 11, 2014 at 02:01:47PM +0100, Tobias Burnus wrote:
> Now that CLooG is no longer used by GCC, it makes sense to also remove it from
> the main configure file. Especially as the in-tree build currently only works
> if also CLooG is available.
I saw that there were still some traces of C
On Tue, Nov 11, 2014 at 2:01 PM, Tobias Burnus
wrote:
> Now that CLooG is no longer used by GCC, it makes sense to also remove it from
> the main configure file. Especially as the in-tree build currently only works
> if also CLooG is available.
>
> Build on x86-64-gnu-linux - and tested that Graph
On 11.11.2014 14:01, Tobias Burnus wrote:
Now that CLooG is no longer used by GCC, it makes sense to also remove it from
the main configure file. Especially as the in-tree build currently only works
if also CLooG is available.
Build on x86-64-gnu-linux - and tested that Graphite still works.*
OK
Now that CLooG is no longer used by GCC, it makes sense to also remove it from
the main configure file. Especially as the in-tree build currently only works
if also CLooG is available.
Build on x86-64-gnu-linux - and tested that Graphite still works.*
OK for the trunk?
[* I did see a failure for
