Catch-22

15 views
Skip to first unread message

mra...@cfl.rr.com

unread,
Dec 12, 2022, 4:45:18 PM12/12/22
to isl-dev...@googlegroups.com
So part of the problem was on my end, since one of my libraries linked to lib64/libisl-23 (which didn't exist).  Thus I soft linked libisl-22 as libisl-23 to finish ./configure

--Michael Ratti

mra...@cfl.rr.com

unread,
Dec 12, 2022, 4:45:18 PM12/12/22
to isl-dev...@googlegroups.com
./configure for both libisl-22 and libisl-23 tests for the existence of: libisl-23.so
Kindly remove libisl existence tests from your libisl configure scripts.

--Michael Ratti


Sven Verdoolaege

unread,
Dec 12, 2022, 5:17:01 PM12/12/22
to mra...@cfl.rr.com, isl-dev...@googlegroups.com
On Mon, Dec 12, 2022 at 03:13:59PM +0000, mra...@cfl.rr.com wrote:
> ./configure for both libisl-22 and libisl-23 tests for the existence
> of: libisl-23.so
> Kindly remove libisl existence tests from your libisl configure
> scripts.

You'll have to explain in a bit more detail what you did.
Where did you get isl? Did you generate configure yourself?
How did you invoke it?

Posting config.log may help diagnose your problem.

skimo
Reply all
Reply to author
Forward
0 new messages