I have GNUStep installed which apparently needs libffi. The ebuild for libffi 3.3.5 specifies GCC 3.3.5 as a dependency but GCC 3.3.6 is now stable. This is causing a upgrade/downgrade loop. Reproducible: Always Steps to Reproduce: 1. emerge -Duav world 2. GCC 3.3.5 upgrades to 3.3.6 3. emerge -Duav world 4. GCC 3.3.6 downgrades to 3.3.5 5. Goto 1 and repeat.
I am having this same issue, emerge -uDp world installs gcc-3.3.5 which then emerges then running emerge -uDp world installs gcc-3.3.5 this is a constant loop additionally nothing else seems to register as needing upgrading, which I find unlikely.
A possible workaround is to: echo "=dev-libs/libffi-3.4.1 -*" >> /etc/portage/package.keywords
Created attachment 70368 [details] This ebuild has cured my Problem with the rebuild of gcc-3.3.5 I simply copied the ebuild and changed one line from =sys-devel/gcc-3.3.5* to =sys-devel/gcc-3.3.6* into my local portage Tree. OOLITE which uses gnustep and libffi works for me.
It's also good to mention that: 0) if you build libffi with gcc (which in gcc-3.3.X series means you built gcj) you can use "gcc-libffi" USE flag for gnustep-base, which will use that libffi 1) for >=gnustep-base-1.10.3-r1 you can use the 'ffcall' USE flag which utilizes ffcall, not libffi for foreign function stuff. Honestly, I suggest ffcall -- for x86 systems, in my experience, it is much more stable with respect to GNUstep. I'm still going to fix this bug soon ... just wanted to mention all that.
Out of curiosity, did you build gcc-3.3.6 with gcj and objc? If so, please give the "gcc-libffi" flag a test, and let me know. Soon, dev-libs/libffi will be deprecated, 'cause the source *is in* gcc.
*** This bug has been marked as a duplicate of 105020 ***
