Opened at 2010-11-16T02:56:07Z
Last modified at 2011-01-02T18:06:25Z
#63 new defect
For build guess in --disable-embedded-cryptopp use python*-config as a guide
| Reported by: | midnightmagic | Owned by: | midnightmagic |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Version: | 0.5.19 | Keywords: | |
| Cc: | Launchpad Bug: |
Description
NetBSD (and every other system that uses non-/usr/local install paths like /opt) will put their libraries somewhere else. The guess ends up being inconsequential, I think, and it works anyway, but it should correctly be the results of pkg-config variables supplied by the system.
Until we get that config for crypto++ in pkgsrc, it might be okay to let your guess be guided by where Python itself is installed; it returns a usable value from:
python2.6-config --prefix
The -lcryptopp can then find its lib, if it needs it.
(Which it doesn't seem to, so /usr/pkg might be in the search path now. But I'm probably wrong about that guess. And I just failed to resist the temptation to guess. Again.)
I'm ambivalent about this. I'd like to resist the temptation to guess, but on the other hand we already guess /usr/local/{include,lib} and asking python2.6-config might be a more principled way to do it. Actually, perhaps it isn't really more principled -- python2.6-config wouldn't tell us where to find libcrypto++, it would just tell us where to find Python headers.
midnightmagic: shall we close this ticket as wontfix?