!!! econf failed
!!! 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/sys-apps/sandbox-1.2.18.1-r2/temp/build.log'.

Last edited by cornish on Mon May 12, 2008 1:38 pm; edited 1 time in total

!!! econf failed
!!! 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/sys-apps/sandbox-1.2.18.1-r2/temp/build.log'.

# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /etc/make.conf.example for a more detailed example.
CFLAGS="-O2 -pipe"
CXXFLAGS="${CFLAGS}"
# This should not be changed unless you know exactly what you are doing. You
# should probably be using a different stage, instead.

Do you have any "experimental" CFLAGS or LDFLAGS in your /etc/make.conf?
Sometimes that will break some ebuilds.

informations from emerge info will show it all

cornish: try commenting out MAKE_OPTS and ACCEPT_KEYWORDS (second one is the one which enables you ALL not-tested AND not-working packages on amd64, you shouldn't use it in make.conf). This sandbox ebuild should work on amd64 though.

If it won't work, please attach this file: /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log

this looks odd to my, why is that? mine has only amd64 in it.
moreover, you cflags is missing the -march option_________________Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball

still there is something that I dont understand, his make.conf is missing the -march tag, from what I understand, omitting this tag causes alot of problems....._________________Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball