Re: [PATCH] Support official CLooG.org versions.

[Andreas Simbuerger <simbuerg at googlemail dot com>]

On 09/12/2010 02:36 PM, Konrad Trifunovic wrote:
> Hi again,
> 
> it seems that I have a problem with the following scenario:
> 
> I have a cloog-ppl installed in /usr/local/lib (a legacy one).
> Now, I have also a new cloog-isl installed in one of my home
> directories (/home/konrad/cloog-isl).
> 
> I configure it with: ./configure --with-cloog=/home/konrad/cloog-isl/lib
> 
> Now, it seems I'm not able to override the order in which
> a configuration script is looking for cloog libraries.
> 
> It first tries a legacy one (linking with -lcloog).
> It finds that there is indeed a legacy cloog in /usr/local/lib
> and it is not even trying "-lcloog-isl" with the value
> --with-cloog=/home/konrad/cloog-isl/lib.
> 
> I think we need some prioritizing mechanism. Let's say, that if you could find
> both legacy and isl-cloog then the priority should be given to the isl-cloog.
> But, this is not a good solution either. It seems that if we can find multiple
> valid cloog installations, an user should be able to manually override the
> desired cloog version.
> 

I could add such an option if you need it, but this patch is just
intended for Graphite testing. After successfully testing CLooG-ISL
the CLooG-PPL (legacy) support and CLooG-PPL support will be removed.

With the recent include path changes you proposed it should be possible
to control the used backend with the --with-cloog* options.

> I'm not a configuration scripts expert.
> I'm not sure whether this solution would be accepted by GCC community,
> but I propose the following:
> 
> have a flag called "--with-cloog" that can take several values, for
> example "auto", "isl", "ppl", "no" etc.
> 
> Then, have other flag called "--with-cloog-prefix" that gives a path
> to the place where we should be looking for a cloog.
> 
> Konrad
> 
> 

Thanks for pointing this out :-)

Cheers,
Andreas