Jakub Jelinek wrote:
> What do binutils need cloog/isl for btw?
Hmmm...
/usr/lib64/libisl.so.13.1.0-gdb.py
/usr/lib64/libisl.so.13.1.0-gdb.pyc
/usr/lib64/libisl.so.13.1.0-gdb.pyo
David
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/
On Wed, Dec 10, 2014 at 01:58:19PM +, David Howells wrote:
> Jakub Jelinek wrote:
>
> > The toplevel configure is shared with gcc. That doesn't mean anything
> > built in binutils actually uses it.
>
> Ah, ok.
>
> > BTW, cloog 0.18.3 has been released 2 days ago, perhaps it is usable with
Jakub Jelinek wrote:
> The toplevel configure is shared with gcc. That doesn't mean anything
> built in binutils actually uses it.
Ah, ok.
> BTW, cloog 0.18.3 has been released 2 days ago, perhaps it is usable with
> latest 4.8.x/4.9.x. Note GCC 5.x will only need isl and not cloog.
Sounds l
On Wed, Dec 10, 2014 at 01:31:45PM +, David Howells wrote:
> Jakub Jelinek wrote:
>
> > What do binutils need cloog/isl for btw?
>
> I'm not sure, but in binutils/configure, I see:
>
> with_cloog
> with_isl
> with_isl_include
> with_isl_lib
> enable_isl_version
Jakub Jelinek wrote:
> What do binutils need cloog/isl for btw?
I'm not sure, but in binutils/configure, I see:
with_cloog
with_isl
with_isl_include
with_isl_lib
enable_isl_version_check
with_cloog_include
with_cloog_lib
enable_clo
On Wed, Dec 10, 2014 at 01:13:54PM +, David Howells wrote:
> Would there be any problem with upgrading cloog to 0.18.1 so that binutils,
> gcc, cross-binutils and cross-gcc can use it? Also, should I put isl-0.12.2
> into it's own package or should it be added to cloog?
>
> Or should I make a
