Moritz Angermann

That is indeed a very curious find and one that should have broken a lot of existing packages already. Can you confirm the does now happen with lowercase names? Could...

@Warbo I think you've found a legitimate bug in the `cabalProject` function. - Do you happen to have a `cabal.project` file in your project? - Is the project folder lowercased?...

could this be an llvm bug in the pipeline? It does not happen with wine3 (wine4 fails for some weird reason, ... maybe I should see if wine4 does not...

> I think that is the correct stopgap. I'll try to cross-validate on a Pi soon. (Sorry to take so long to get back on this. I got pulled away...

@michaelpj I wholeheartedly agree with this in spirit! We *do* need to take care of IFD issues wrt to platform dependencies. The use of IFDs is primarily to bridge the...

@ruhatch are you going to get around to this as well, or should I?

> One thing we could fix is installing benchmarks in $out/bin rather than a path which is different for every component. you mean all benchmarks for a package into the...

@o1lo01ol1o I'm afraid I don't understand the first part of your question: > What's the recommended way to respect the -fllvm flag in a cabal file for > correct version...

I just ran into the same issue. When browsing packages, finding `cryptohash` and `cryptonite`, an no deprecation note (as with some other package), is really confusing.

I've run into minor issues with packages using `cryptohash`, when I was using `cryptonite`, ending up with incompatible, yet identically named, data structures. Package imports solve this to a certain...