On Mon, Nov 8, 2010 at 12:04 PM, Kfir Lavi <[email protected]> wrote:
> > > On Wed, Nov 3, 2010 at 8:32 PM, Kfir Lavi <[email protected]> wrote: > >> >> >> On Wed, Nov 3, 2010 at 7:50 PM, Kfir Lavi <[email protected]> wrote: >> >>> >>> >>> On Wed, Nov 3, 2010 at 12:33 PM, Kfir Lavi <[email protected]> wrote: >>> >>>> >>>> >>>> On Tue, Nov 2, 2010 at 2:49 PM, Manuel Lauss < >>>> [email protected]> wrote: >>>> >>>>> On Sun, Oct 31, 2010 at 9:08 AM, Kfir Lavi <[email protected]> >>>>> wrote: >>>>> > Hi, >>>>> > I have a cross compilation environment inside a chroot. >>>>> > I run: >>>>> > i686-unknown-linux-gnu-emerge dev-libs/ace >>>>> > ... >>>>> > checking for i686-unknown-linux-gnu-g++... i686-unknown-linux-gnu-g++ >>>>> > checking for C++ compiler default output file name... configure: >>>>> > error: C++ compiler cannot create executables >>>>> >>>>> Have a look at config.log. It tells exactly what went wrong, including >>>>> gcc >>>>> error output. >>>>> >>>>> Manuel >>>>> >>>>> It seems that one of the steps that I do, is deleting the tools. I need >>>> then to install again from package from the mother system (I'm running here >>>> as chroot, and its very good that I did so). >>>> So I install gcc and binutils, then compile them again in the chroot >>>> environment. >>>> Using i686-unknown-linux-gnu-emerge and everything happens again. >>>> I didn't find the culprit yet. >>>> >>>> Kfir >>>> >>> >>> It seems that installing dev-libs/ace is causing the problem. >>> emerge dev-libs/ace [works] >>> i686-gentoo-linux-gnu-g++ [works] >>> i686-gentoo-linux-gnu-gcc [works] >>> gcc [works] >>> g++ [works] >>> i686-gentoo-linux-gnu-emerge dev-libs/ace [DONT WORK] >>> >>> Other packages emerging ok with i686-gentoo-linux-gnu-emerge. >>> Can someone give me a hint? or something to check? >>> >>> Thanks, >>> Kfir >>> >> >> Some diagnostics: >> $ cd /usr/__CHOST__/tmp/portage/dev-libs/ace-5.7.2/work/ACE_wrappers/build >> $ ../configure >> checking build system type... i686-pc-linux-gnu >> checking host system type... i686-pc-linux-gnu >> checking target system type... i686-pc-linux-gnu >> checking for a BSD-compatible install... /usr/bin/install -c >> checking whether build environment is sane... yes >> checking for gawk... gawk >> checking whether make sets $(MAKE)... yes >> checking for egrep... grep -E >> checking whether #! works in shell scripts... yes >> checking for g++... g++ >> checking for C++ compiler default output file name... a.out >> checking whether the C++ compiler works... yes >> checking whether we are cross compiling... no >> checking for suffix of executables... >> checking for suffix of object files... o >> checking whether we are using the GNU C++ compiler... yes >> checking whether g++ accepts -g... yes >> checking for style of include used by make... GNU >> checking dependency style of g++... gcc3 >> checking how to run the C++ preprocessor... g++ -E >> >> Here we see that configure passes the test it failed with emerge. >> One line did grab my attention: checking whether we are cross compiling... >> no >> >> Maybe the environment that i686-gentoo-linux-gnu-emerge creates is not >> working for ACE. >> >> What do you think? >> >> Regards, >> Kfir >> > > I did again a cross compilation, really the same way I did before, but with > a different name. > crossdev -P -vt i686-gentoo1-linux-gnu > But without the -S, so it compiled all the latest and greatest. > > Now the problem is solved, but still ACE will stuck on another line: > checking for epoll_create... configure: error: cannot run test program > while cross compiling > See `config.log' for more details. > > But this is for different thread. > > Regards, > Kfir > I have created an ebuild that deletes the epoll test from configure. I have posted it here: http://bugs.gentoo.org/show_bug.cgi?id=348521 After eliminating the epoll test, the compilation passes. Regards, Kfir
