New failure in cl-libuv I don't understand

[Stelian Ionescu]

Hi Robert,

> This one was my fault.  I did the PR with this patch, because cl-libuv 
> wouldn't build on my Mac.  Since there's no testing, apparently, it 
> slipped through.
>
> I don't know how to fix this, because I have never used CFFI-grovel, so 
> no idea how to put Madhu's advice into practice.
>
> As an aside, doesn't this kind of break Faré's design principle that 
> the person who has the information is the one who should be configuring 
> the software?  It seems like we are expecting the programmer to guess 
> ahead of time what are all of the possible locations for the foreign 
> library and includes. Wouldn't it make more sense for this to be 
> configurable?

Yes, but there's no way to currently configure this except as you point out below.

> Of course, this is partly my fault, since ASDF does not support 
> configuring operations, except with gross dynamic variables.

Adding a configuration stage for a DEFSYSTEM would be my most desired feature at the moment.

-- 
Stelian Ionescu