when i tried to emerge gnome-base/orbit-2.14.7 i got the following error: "Making all in orb-core make[8]: Entering directory `/var/tmp/portage/gnome-base/orbit-2.14.7/work/ORBit2-2.14.7/include/orbit/orb-core' (rm -f corba-defs.h corba-defs-stubs.c corba-defs-skels.c corba-defs-common.c corba-defs-imodule.c corba-defs-skelimpl.c || true) > /dev/null ../../../src/idl-compiler/orbit-idl-2 -I../../../src/idl/CORBA_PIDL -I../../../src/idl/CORBA -I../../../src/idl/interop -I../../../src/orb/orb-core --noskels --nodefskels --nostubs --noidata --nocommon --showcpperrors --define=Object=OObject --define=TypeCode=TTypeCode --deps ./.deps/corba-defs.idl.P ../../../src/orb/orb-core/corba-defs.idl orbit-idl-2 2.14.7 compiling mode, show preprocessor errors, passes: headers Processing file ../../../src/orb/orb-core/corba-defs.idl gcc-config error: Could not run/locate "i386-pc-linux-gnu-gcc" ** (orbit-idl-2:20278): WARNING **: ../../../src/orb/orb-core/corba-defs.idl compilation failed make[8]: *** [corba-defs.h] Error 1 make[8]: Leaving directory `/var/tmp/portage/gnome-base/orbit-2.14.7/work/ORBit2-2.14.7/include/orbit/orb-core' make[7]: *** [all-recursive] Error 1 make[7]: Leaving directory `/var/tmp/portage/gnome-base/orbit-2.14.7/work/ORBit2-2.14.7/include/orbit' make[6]: *** [all] Error 2 make[6]: Leaving directory `/var/tmp/portage/gnome-base/orbit-2.14.7/work/ORBit2-2.14.7/include/orbit' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/var/tmp/portage/gnome-base/orbit-2.14.7/work/ORBit2-2.14.7/include' make[4]: *** [all] Error 2 make[4]: Leaving directory `/var/tmp/portage/gnome-base/orbit-2.14.7/work/ORBit2-2.14.7/src/orb/include' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/var/tmp/portage/gnome-base/orbit-2.14.7/work/ORBit2-2.14.7/src/orb' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/gnome-base/orbit-2.14.7/work/ORBit2-2.14.7/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gnome-base/orbit-2.14.7/work/ORBit2-2.14.7' make: *** [all] Error 2 !!! ERROR: gnome-base/orbit-2.14.7 failed. Call stack: ebuild.sh, line 1615: Called dyn_compile ebuild.sh, line 972: Called qa_call 'src_compile' ebuild.sh, line 44: Called src_compile orbit-2.14.7.ebuild, line 40: Called gnome2_src_compile gnome2.eclass, line 71: Called die !!! compile failure !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/gnome-base/orbit-2.14.7/temp/build.log'." the whole log file is here: http://users.ntua.gr/el05007/log my emerge --info is here: http://users.ntua.gr/el05007/emergeinfo Reproducible: Always Steps to Reproduce: 1. 2. 3.
i just noticed that i get the same error when i tried to reemerge the previous stable version of orbit... :/ i looked at the file that the log mentions,but i couldn't find something useful...
<snip> gcc-config error: Could not run/locate "i386-pc-linux-gnu-gcc" CHOST="i686-pc-linux-gnu" </snip> You can't just switch CHOST on the fly... http://www.gentoo.org/doc/en/change-chost.xml
i did what the guide says,some months ago when i needed to switch to the new chost... and i had no problems with chost... moreover,i can emerge other packages(ie i emerged lftp without any such problems)... i want also to add that orbit was emerged during an update... before orbit,glibc and glib were updated... could it be this that causes the problem?... (In reply to comment #2) > <snip> > gcc-config error: Could not run/locate "i386-pc-linux-gnu-gcc" > CHOST="i686-pc-linux-gnu" > </snip> > > You can't just switch CHOST on the fly... > > http://www.gentoo.org/doc/en/change-chost.xml >
however,even after glibc and glib update i can still emerge other packages... only orbit is the problem...
try reemerging libIDL first. Changing CHOST as you might have seen is a complicated matter. The biggest problem being rebuilding all with the correct order to avoid dependencies X using an old CHOST and for whatever reason perturbing ebuild Y stopping you from compiling it.
thx... :D that solved the problem... (In reply to comment #5) > try reemerging libIDL first. > > Changing CHOST as you might have seen is a complicated matter. The biggest > problem being rebuilding all with the correct order to avoid dependencies X > using an old CHOST and for whatever reason perturbing ebuild Y stopping you > from compiling it. >
In our terms it was resolution INVALID, but I'll just close it instead :) Great you got it fixed! Watch out that many other things don't break similarly due to this delicate matter of order on CHOST change, if you really really had to even change it.. I believe this broke because libIDL stores the CHOST based gcc binary and calls it for apps when they need to process IDL files
