checking for working makeinfo... found checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++ checking for C++ compiler default output... configure: error: C++ compiler cannot create executables See `config.log' for more details. !!! ERROR: media-video/avifile-0.7.32.20030219 failed. !!! Function econf, Line 303, Exitcode 77 !!! econf failed -------------------------------------- rc4 - Stage 3 comes with a i586 GCC Toolchain, yet most people will wind up with a chost set to i686 in their default make.conf. avifile seems to want and expect to see a i686 gcc (rightly so), yet it doesn't exist. I solved my problem by rebuilding GCC for my current arch (i686) and avi file worked fine. I am guessing this bug would not affect someone who had used stage 1 or 2. See this forum topic http://forums.gentoo.org/viewtopic.php?t=57418&highlight=
did you try gcc-config ?
At the time, gcc-config showed the i586 GCC that comes in rc4. The only one on my system. All other programs compiled fine, avifile did not. It looked for i686 and only i686 gcc.
I can confirm the same process. I used the stage 3 1.4rc4 tarballs. After installing X successfully, I did an emerge gnome. It failed when trying to compile avifile with the error about not being able to create C++ executables using my gcc. gcc-config -v showed an i586 gcc. emerge gcc emerge avifile (successful) emerge gnome
Doesn't this depend on which stage3 tarball you extracted? I used a recent (at the time of writing) athlon-xp version and CHOST was set to i686. Of course, if you're using the stage3 x86 generic tarball, then this will be an issue again. Can this problem actually be fixed without dropping the i586 stage3 tarballs?
Not sure what the status is now, as I have not done a stage 3 start since I reported the bug. The stage 3 would have been the x86 generic one. I don't recall if their were specific i686/i586 stage 3's RC4 builds at the time. By following the install guild at the time, most people would have had some other value for their CHOST. Even the default is i686. Since that particular stage 3 came with a i586 toolchain (as it should for an x86 build - even a i386 for that matter), things would fail. Anyway - pretty old bug, and I would guess that it has been resolved just by the availablility of more diverse stage 3 builds now.
should be fixed in latest stage tarballs
