Description of problem: Other systems call the cryptopp library crypto++, leading to incompatibilities in Fedora. Steps to Reproduce: 1.sudo yum install cabal-install openssl-devel cryptopp-devel 2.cabal update 3.cabal install happstack-server-6.5.1 Actual results: cabal: Missing dependency on a foreign library: * Missing C library: crypto++ Expected results: Registering happstack-server-6.5.1... Additional info: http://packages.ubuntu.com/oneiric/i386/libcrypto++-dev/filelist
This is bug in cabal. Crypto++ upstream recommends to use cryptopp names i.e /usr/include/cryptopp, libcryptopp.so.
Reassigning to cabal-install.
http://groups.google.com/group/cryptopp-users/browse_thread/thread/3b316bcec601730e/2313449e8be8a932
In that case, it's a bug in upstream happstack-server not cabal-install. The build specification [1] lists a dependency on "crypto++". Now the question is, should Fedora try to be compatible with "debian innovations" when possible? [1] http://hackage.haskell.org/packages/archive/happstack-server/6.5.1/happstack-server.cabal
(In reply to comment #4) > Now the question is, > should Fedora try to be compatible with "debian innovations" when possible? No. Why we should repeat mistakes of other disro? happstack-server should follow naming recommended by Crypto++ upstream.
Fixed in happstack-server-6.5.2. Should I close this now?
(In reply to comment #6) > Fixed in happstack-server-6.5.2. Should I close this now? I guess so, if it actually works.
Ok thanks closing - I was just about to comment that you could patch happstack-server.cabal for this - but good that has already been upstreamed. :)