When I try to emerge net-p2p/mldonkey-2.5.16-r4, the emerge fails. See attachment for the full build log. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 35106 [details] Build log
Created attachment 35107 [details] Portage info
Created attachment 35108 [details] List of the installed ebuilds
2 things- when you upgraded to ocaml 3.07, did you run the rebuild script included with the update? Could you also please try the latest mldonkey-2.5.16 revision in portage?
1) rebuild script -- yes, I did. It showed that it has nothing to do, which is odd, because I have mldonkey installed. I'll check another revision in an hour or so. However, it's a last ebuild marked stable, so it'll ask me to downgrade afterwards.
The last 2.4.16-r7 fails with exactly the same error. 2.4.21-r2 is fails with another error, which I attach as a new error log.
Created attachment 35172 [details] 2.5.21 build log
I meant 2.5.16 and 2.5.21, of course.
Some kind soul advised me to re-emerge liblgtk and liblgl. liblgtk failed to remerge with exactly the same error as mldonkey. liblgl emerged flawlessly, and then i emerge both liblgtk and mldonkey without any problem. Should I close this bug or you would rather further investigate on this issue?
I'd like to investigate further on why lablgl needed to be remerged. mattam- I seemed to get this bug report after the ocaml upgrade- I wasn't sure if you knew of something that might be causing this?
Lablgl needs to be reemerged (like any other caml library) on compiler updates, because caml is not binary compatible from version to version. The problem here is that the rebuilding script did not catch lablgl, which i find bizarre. The fact that lablgtk failed to rebuild without first upgrading to lablgl is another instance of the binary incompatibility problem. Could you try 'reverting' to the moment when you got the compiler merged and investigate by putting some debug echo's in my rebuild script, or just give us the output of `qpkg -nc -n -q -I dev-lang/ocaml-3.06` in this configuration ? I have really no idea of the source of the problem...
Matthieu, Tell me exactly what to do. You want me to downgrade to the previous version of mldonkey and that's it? Or do I need to downgrade the gcc then downgrade mldonkey?
I meant when you got the ocaml 3.07 compiler merged. Thinking twice, you may not be able to do so (you'll need to rebuild 3.06, lablgl etc... and 3.07 again), but you can attach your emerge.log so that i can try to reproduce your installation myself.
*** Bug 57696 has been marked as a duplicate of this bug. ***
Matthieu, I've attached the emerge.log for mldonkey at the very beginning. Please, let me know what do you want me to provide.
Ok, i've been able to reproduce the problem on another machine and i tracked down the problem. It is my rebuild script that expected a particular output from qpkg which it didn't get (it has changed between versions). Now the script find lablgl and lablgtk as expected (but not mldonkey, i don't know why) and should be more robust regarding qpkg changes.
*** Bug 58309 has been marked as a duplicate of this bug. ***
*** Bug 58938 has been marked as a duplicate of this bug. ***
The fixed described here (re-merge lablgl and lablgtk) works fine, but this wasn't drawn to my attention upon upgrading ocaml. should it have been?
The ocaml upgrade should have informed you about the rebuild script which I fixed one week ago so that it properly reemerges lablgl and lablgtk.
*** Bug 59142 has been marked as a duplicate of this bug. ***
*** Bug 59522 has been marked as a duplicate of this bug. ***
*** Bug 60817 has been marked as a duplicate of this bug. ***
*** Bug 61081 has been marked as a duplicate of this bug. ***
*** Bug 61228 has been marked as a duplicate of this bug. ***
*** Bug 68135 has been marked as a duplicate of this bug. ***
*** Bug 65338 has been marked as a duplicate of this bug. ***
rebulding dev-ml/lablgtk solved the problem for me, but yes... that's ugly, so this bug can't me marked as FIXED since there are still affected users with no clues. Perhaps bump up the dev-ml/lablgtk version number to make it rebuild for all users?
It's resolved. The ocaml bump should have told you to run the ocaml update script: sh /usr/portage/dev-lang/ocaml/files/ocaml-rebuild.sh I wish ocaml could cause a post-compile dependency on the ocaml programs you have installed. Sadly, it does not. Unless you can think of a better solution, the rebuild script is the best we have.
*** Bug 72910 has been marked as a duplicate of this bug. ***
*** Bug 78004 has been marked as a duplicate of this bug. ***
*** Bug 133771 has been marked as a duplicate of this bug. ***
*** Bug 134905 has been marked as a duplicate of this bug. ***
*** Bug 137212 has been marked as a duplicate of this bug. ***
*** Bug 142899 has been marked as a duplicate of this bug. ***
*** Bug 127837 has been marked as a duplicate of this bug. ***
