Hi, dev-libs/libffi-3.3_rc0 was just stabilized. Everything updated well except ghc-8.6.5 which still look for libffi-3.2.1 even if there is not an hard dep on this version.
Was ghc rebuilt after libffi upgrade? To check you can run: $ qlop -muv ghc libffi
(In reply to Sergei Trofimovich from comment #1) > Was ghc rebuilt after libffi upgrade? To check you can run: > $ qlop -muv ghc libffi It was the rebuilding after libffi upgrade which failed. For now my bad and quick solution was: `ln -s /usr/lib64/libffi-3.2.1 /usr/lib64/libffi-3.3_rc0`
(In reply to sp.gentoo from comment #2) > (In reply to Sergei Trofimovich from comment #1) > > Was ghc rebuilt after libffi upgrade? To check you can run: > > $ qlop -muv ghc libffi > > It was the rebuilding after libffi upgrade which failed. > For now my bad and quick solution was: > `ln -s /usr/lib64/libffi-3.2.1 /usr/lib64/libffi-3.3_rc0` Sounds like a ghc bug. Do you have a failed build log?
> Sounds like a ghc bug. Do you have a failed build log? Here it is: https://pastebin.com/BidF617L We can see it searches ffi.h in libffi-3.2.1 instead of libffi-3.3_rc0 which causes "ffi.h: No such file or directory"
The problem here is that you use USE=ghcbootstrap. That uses broken installed ghc version to boot ghc instead of working binary version of ghc. USE=ghcmakebinary was supposed to build a binary that does not depends on libffi. But that should be a separate issue.
Created attachment 591208 [details] build.log Attaching your build.log to ensure it is still available longer term.
> The problem here is that you use USE=ghcbootstrap. That uses broken > installed ghc version to boot ghc instead of working binary version of ghc. I did not put enough attention to my USE flags, thanks. I'll try this and will report the results.
Thanks, that was it. It is solved
