Created attachment 772037 [details]
while trying to emerge cabal-install, building hackage-security fails due to a linking failure.
build.log and output of emerge --info: see attachment.
output of emerge -pqv:
emerge -pqv hackage-security
[ebuild N ] dev-haskell/hackage-security-0.6.0.1-r1 USE="lukko -doc -hscolour -profile -test"
Created attachment 772040 [details]
output emerge --info
Anyone caring about this issue?
Pretty annoying when you can't run cabal...
I want to use today the csv-conduit package, which is not available in general gentoo repo or haskell-gentoo overlay
when I would have cabal available, I would have simply installed it via cabal and not having being confronted with the intermediary gentoo repos not featuring this package....
I am going to update my system which will take hours or days with probably the same result that this issue prevents me from installing cabal and in the meantime I am blocked in doing my work...
again, a very annoying issue...
(In reply to Didier Colle from comment #2)
> Anyone caring about this issue?
> Pretty annoying when you can't run cabal...
> I want to use today the csv-conduit package, which is not available in
> general gentoo repo or haskell-gentoo overlay
> when I would have cabal available, I would have simply installed it via
> cabal and not having being confronted with the intermediary gentoo repos not
> featuring this package....
> I am going to update my system which will take hours or days with probably
> the same result that this issue prevents me from installing cabal and in the
> meantime I am blocked in doing my work...
> again, a very annoying issue...
The version of hackage-security you had issues with no longer is in the ::gentoo repo. hackage-security-0.6.1.0 should work perfectly with cabal-install-220.127.116.11. If you are having trouble upgrading to ghc-9.0.2, cabal-18.104.22.168, cabal-install-22.214.171.124 etc, let me know.
Also, do let me know if this is no longer an issue for you.
Problem is still there: linking failure during emerge of hackage-security.
The hackage-security version has indeed changed from 0.6.0.1 to 0.6.1.0; the problem nevertheless still exists.
I updated my system with emerge -qauDN --with-bdeps=y @world (against a portage tree of 2 or 3 days old) and emerge -c; as haskell-updater resulting in nothing to rebuild, i did a haskell-updater --all. The problem however unfortunately is still there....
I did not try emerging different versions of cabal-install, as hackage-security is a dependency of cabal-install and the root cause problem is with hackage-security; as such, portage never comes to emerging cabal-install; and as 0.6.1.0 is the only hackage-security available, portage will always try emerging that version.
> dcolle@localhost ~ $ find /usr/portage/dev-haskell/hackage-security/ -name "*.ebuild"
> dcolle@localhost ~ $ find /var/db/repos/haskell/dev-haskell/hackage-security/ -name "*.ebuild"
The first undefined reference in the build.log is:
> /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/../../../../lib64/crt1.o: in function `_start':
> (.text+0x17): undefined reference to `main'
Does that somehow imply an executable was not compiled (Main module of hackage-security), despite the linker is told to put one together?
Please share the new build.log and emerge --info.
(We might also need qlist -ICv dev-haskell)
Created attachment 797095 [details]
new build.log (aug 2nd)
Created attachment 797098 [details]
new output emerge --info (Aug 2nd)
dcolle@localhost ~ $ qlist -ICv dev-haskell