Looks like the 1.5.3 configure script inadvertently dropped support for alternate cURL library path support via --with-libcurl:
Yes, because it's the crappy way to do it. The right way is to export a variable to specify the PKG_CONFIG_PATH to the correct *.pc file. See my RPMs for reference...
Seems to be a way that works on more systems and with local built binaries is the right way to do it. Dependance on a packaging system is the crappy way to do it.
No offense, but do read up on pkgconfig a little bit before commenting. For how long have you been involved in packaging? I've told what's the correct way of doing it with pkconfig and locally built binaries.
Why? You seem to miss the point completly. I don't have pkgconfig. I don't want pkgconfig, so why should I read up on it? I have been building software from source for a few decades now. Since usenet was the way to distribute the sources for most. The all the worlds linux folks are as annoying today as the all the worlds a vax foks where then.