Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
sandbox (cannot run C compiled programs)
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64
View previous topic :: View next topic  
Author Message
DarkDEUS
n00b
n00b


Joined: 14 Nov 2007
Posts: 13

PostPosted: Fri Nov 16, 2007 11:03 pm    Post subject: sandbox (cannot run C compiled programs) Reply with quote

I'm having a dilemma whilst emerging sandbox.
It keeps giving me the error:
Code:
error: cannot run C compiled programs.

I've used FEATURES=-sandbox emerge sandbox, but to no avail. I've read that some issues
might come from i686-* files which might be found in /usr/bin, but none exist. The following
are the two logs for the setup.

sandbox.log
Code:
>>> Unpacking source...
>>> Unpacking sandbox-1.2.18.1.tar.bz2 to /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work
  [32;01m* [0m Applying sandbox-1.2.18.1-open-normal-fail.patch ...
 [A [120C   [34;01m[  [32;01mok [34;01m ] [0m
  [32;01m* [0m Applying sandbox-1.2.18.1-open-cloexec.patch ...
 [A [120C   [34;01m[  [32;01mok [34;01m ] [0m
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1 ...
  [33;01m* [0m If configure fails with a 'cannot run C compiled programs' error, try this:
  [33;01m* [0m FEATURES=-sandbox emerge sandbox
  [32;01m* [0m Configuring sandbox for ABI=x86...
 * econf: updating sandbox-1.2.18.1/config.sub with /usr/share/gnuconfig/config.sub
 * econf: updating sandbox-1.2.18.1/config.guess with /usr/share/gnuconfig/config.guess
../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib --build=i686-pc-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log
  [31;01m* [0m
  [31;01m* [0m ERROR: sys-apps/sandbox-1.2.18.1-r2 failed.
  [31;01m* [0m Call stack:
  [31;01m* [0m                    ebuild.sh, line 1701:  Called dyn_compile
  [31;01m* [0m                    ebuild.sh, line 1039:  Called qa_call 'src_compile'
  [31;01m* [0m                    ebuild.sh, line   44:  Called src_compile
  [31;01m* [0m   sandbox-1.2.18.1-r2.ebuild, line   87:  Called econf '--libdir=/usr/lib32' '--enable-multilib'
  [31;01m* [0m                    ebuild.sh, line  638:  Called die
  [31;01m* [0m The specific snippet of code:
  [31;01m* [0m            die "econf failed"
  [31;01m* [0m  The die message:
  [31;01m* [0m   econf failed
  [31;01m* [0m
  [31;01m* [0m If you need support, post the topmost build error, and the call stack if relevant.
  [31;01m* [0m A complete build log is located at '/var/log/portage/sys-apps:sandbox-1.2.18.1-r2:20071116-175405.log'.
  [31;01m* [0m
config.log
Code:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by sandbox configure 1.2.18.1, which was
generated by GNU Autoconf 2.59.  Invocation command line was

  $ ../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib --build=i686-pc-linux-gnu

## --------- ##
## Platform. ##
## --------- ##

hostname = livecd
uname -m = x86_64
uname -r = 2.6.23-kamikaze5
uname -s = Linux
uname -v = #1 SMP Mon Nov 5 04:15:06 UTC 2007

/usr/bin/uname -p = Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
hostinfo               = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /usr/local/sbin
PATH: /sbin
PATH: /usr/sbin
PATH: /usr/lib64/portage/bin
PATH: /usr/local/bin
PATH: /bin
PATH: /usr/bin
PATH: /opt/bin
PATH: /usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1


## ----------- ##
## Core tests. ##
## ----------- ##

configure:1533: checking for a BSD-compatible install
configure:1588: result: /bin/install -c
configure:1599: checking whether build environment is sane
configure:1642: result: yes
configure:1707: checking for gawk
configure:1723: found /bin/gawk
configure:1733: result: gawk
configure:1743: checking whether make sets $(MAKE)
configure:1763: result: yes
configure:1942: checking for i686-pc-linux-gnu-gcc
configure:1971: result: no
configure:1980: checking for gcc
configure:1996: found /usr/bin/gcc
configure:2006: result: gcc
configure:2250: checking for C compiler version
configure:2253: gcc --version </dev/null >&5
gcc (GCC) 4.1.1 (Gentoo 4.1.1-r3)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:2256: $? = 0
configure:2258: gcc -v </dev/null >&5
Using built-in specs.
Target: x86_64-pc-linux-gnu
Configured with: /var/tmp/portage/sys-devel/gcc-4.1.1-r3/work/gcc-4.1.1/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.1 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.1/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.1/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/include/g++-v4 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec --disable-nls --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-libunwind-exceptions --enable-multilib --disable-libmudflap --disable-libssp --disable-libgcj --enable-languages=c --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix
gcc version 4.1.1 (Gentoo 4.1.1-r3)
configure:2261: $? = 0
configure:2263: gcc -V </dev/null >&5
gcc: '-V' must come at the start of the command line
configure:2266: $? = 1
configure:2289: checking for C compiler default output file name
configure:2292: gcc -O2 -pipe   conftest.c  >&5
configure:2295: $? = 0
configure:2341: result: a.out
configure:2346: checking whether the C compiler works
configure:2352: ./a.out
../sandbox-1.2.18.1//configure: line 2353: ./a.out: cannot execute binary file
configure:2355: $? = 126
configure:2364: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=set
ac_cv_env_CFLAGS_value='-O2 -pipe'
ac_cv_env_CPPFLAGS_set=set
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=set
ac_cv_env_build_alias_value=i686-pc-linux-gnu
ac_cv_env_host_alias_set=set
ac_cv_env_host_alias_value=i686-pc-linux-gnu
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_exeext=
ac_cv_path_install='/bin/install -c'
ac_cv_prog_AWK=gawk
ac_cv_prog_ac_ct_CC=gcc
ac_cv_prog_make_make_set=yes

## ----------------- ##
## Output variables. ##
## ----------------- ##

ACLOCAL='${SHELL} /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1/missing --run aclocal-1.9'
ALLOCA=''
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR='${SHELL} /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1/missing --run tar'
AR=''
AUTOCONF='${SHELL} /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1/missing --run autoconf'
AUTOHEADER='${SHELL} /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1/missing --run autoheader'
AUTOMAKE='${SHELL} /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1/missing --run automake-1.9'
AWK='gawk'
CC='gcc'
CCDEPMODE=''
CFLAGS='-O2 -pipe'
CPP=''
CPPFLAGS=''
CXXCPP=''
CYGPATH_W='echo'
DEFS=''
DEPDIR=''
ECHO='echo'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='${SHELL} $(install_sh) -c -s'
LDFLAGS=''
LIBC_PATH=''
LIBDL=''
LIBOBJS=''
LIBS=''
LIBTOOL=''
LN_S=''
LTLIBOBJS=''
MAKEINFO='${SHELL} /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1/missing --run makeinfo'
OBJEXT=''
PACKAGE='sandbox'
PACKAGE_BUGREPORT='sandbox@gentoo.org'
PACKAGE_NAME='sandbox'
PACKAGE_STRING='sandbox 1.2.18.1'
PACKAGE_TARNAME='sandbox'
PACKAGE_VERSION='1.2.18.1'
PATH_SEPARATOR=':'
RANLIB=''
READELF=''
SET_MAKE=''
SHELL='/bin/sh'
STRIP=''
VERSION='1.2.18.1'
ac_ct_AR=''
ac_ct_CC='gcc'
ac_ct_RANLIB=''
ac_ct_STRIP=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__include=''
am__leading_dot='.'
am__quote=''
am__tar='${AMTAR} chof - "$$tardir"'
am__untar='${AMTAR} xf -'
bindir='${exec_prefix}/bin'
build='i686-pc-linux-gnu'
build_alias='i686-pc-linux-gnu'
build_cpu=''
build_os=''
build_vendor=''
datadir='/usr/share'
exec_prefix='NONE'
host='i686-pc-linux-gnu'
host_alias='i686-pc-linux-gnu'
host_cpu=''
host_os=''
host_vendor=''
includedir='${prefix}/include'
infodir='/usr/share/info'
install_sh='/var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1/install-sh'
libdir='/usr/lib32'
libexecdir='${exec_prefix}/libexec'
localstatedir='/var/lib'
mandir='/usr/share/man'
mkdir_p='mkdir -p --'
oldincludedir='/usr/include'
prefix='/usr'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE "sandbox"
#define PACKAGE_BUGREPORT "sandbox@gentoo.org"
#define PACKAGE_NAME "sandbox"
#define PACKAGE_STRING "sandbox 1.2.18.1"
#define PACKAGE_TARNAME "sandbox"
#define PACKAGE_VERSION "1.2.18.1"
#define VERSION "1.2.18.1"

configure: exit 1

Hopefully someone can help me.
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1408

PostPosted: Fri Nov 16, 2007 11:36 pm    Post subject: Reply with quote

You're going to have more issues in the future than just sandbox. Look:
From Sandbox.log
Code:
[32;01m* [0m Configuring sandbox for ABI=x86


From config.log
Code:
uname -m = x86_64
...
host='i686-pc-linux-gnu'


For everything to work correctly, uname -m must be i686. See my signature for an emerge wrapper and build your toolchain properly, before trying sandbox
_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper
Back to top
View user's profile Send private message
CoolGenie
n00b
n00b


Joined: 16 Nov 2007
Posts: 16

PostPosted: Sat Nov 17, 2007 10:00 am    Post subject: Reply with quote

eyoung100 wrote:
For everything to work correctly, uname -m must be i686. See my signature for an emerge wrapper and build your toolchain properly, before trying sandbox


I'm having the same problem with sandbox. But clicking on 'Emerge Wrapper' in your signature gets me into a topic about changing hostname. Isn't something wrong with this?
Back to top
View user's profile Send private message
Hallas
n00b
n00b


Joined: 17 Nov 2007
Posts: 1
Location: Orange County, USA

PostPosted: Sat Nov 17, 2007 10:36 pm    Post subject: sandbox (cannot run C compiled programs) Reply with quote

the ebuild seams to be passing -m32 to the compiler which means that 32-bit binaries are created,

I fixed it by enabling: "Executable file formats / Emulations" -> "IA32 Emulation" in the kernel config.
Back to top
View user's profile Send private message
donmartio
Apprentice
Apprentice


Joined: 11 Dec 2004
Posts: 179

PostPosted: Sun Nov 18, 2007 3:35 pm    Post subject: Reply with quote

Well my Problem is a little bit different.

I get 'error: C compiler cannot create executable'

Code:

Calculating dependencies... done!
>>> Verifying ebuild Manifests...

>>> Emerging (1 of 1) sys-apps/sandbox-1.2.18.1-r2 to /
 * sandbox-1.2.18.1.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                                         [ ok ]
 * checking ebuild checksums ;-) ...                                                                                                [ ok ]
 * checking auxfile checksums ;-) ...                                                                                               [ ok ]
 * checking miscfile checksums ;-) ...                                                                                              [ ok ]
 * checking sandbox-1.2.18.1.tar.bz2 ;-) ...                                                                                        [ ok ]
>>> Unpacking source...
>>> Unpacking sandbox-1.2.18.1.tar.bz2 to /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work
 * Applying sandbox-1.2.18.1-open-normal-fail.patch ...                                                                             [ ok ]
 * Applying sandbox-1.2.18.1-open-cloexec.patch ...                                                                                 [ ok ]
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1 ...
 * If configure fails with a 'cannot run C compiled programs' error, try this:
 * FEATURES=-sandbox emerge sandbox
 * Configuring sandbox for ABI=x86...
 * econf: updating sandbox-1.2.18.1/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating sandbox-1.2.18.1/config.sub with /usr/share/gnuconfig/config.sub
../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib --build=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 i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log
 *
 * ERROR: sys-apps/sandbox-1.2.18.1-r2 failed.
 * Call stack:
 *                    ebuild.sh, line 1701:  Called dyn_compile
 *                    ebuild.sh, line 1039:  Called qa_call 'src_compile'
 *                    ebuild.sh, line   44:  Called src_compile
 *   sandbox-1.2.18.1-r2.ebuild, line   87:  Called econf '--libdir=/usr/lib32' '--enable-multilib'
 *                    ebuild.sh, line  638:  Called die
 * The specific snippet of code:
 *                      die "econf failed"
 *  The die message:
 *   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'.
 *

 * Messages for package sys-apps/sandbox-1.2.18.1-r2:

 *
 * ERROR: sys-apps/sandbox-1.2.18.1-r2 failed.
 * Call stack:
 *                    ebuild.sh, line 1701:  Called dyn_compile
 *                    ebuild.sh, line 1039:  Called qa_call 'src_compile'
 *                    ebuild.sh, line   44:  Called src_compile
 *   sandbox-1.2.18.1-r2.ebuild, line   87:  Called econf '--libdir=/usr/lib32' '--enable-multilib'
 *                    ebuild.sh, line  638:  Called die
 * The specific snippet of code:
 *                      die "econf failed"
 *  The die message:
 *   econf failed


I first tried
Quote:
I fixed it by enabling: "Executable file formats / Emulations" -> "IA32 Emulation" in the kernel config.


But that doesn't help.

Any hints?
_________________
Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live.
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1408

PostPosted: Mon Nov 19, 2007 3:57 pm    Post subject: Reply with quote

Sorry about the signature problem. (I had left off a 4) It's fixed.

Have you tried what the emerge suggests?
Code:
FEATURES=-sandbox emerge sandbox

_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper
Back to top
View user's profile Send private message
loftwyr
l33t
l33t


Joined: 29 Dec 2004
Posts: 970
Location: 43°38'23.62"N 79°27'8.60"W

PostPosted: Mon Nov 19, 2007 6:28 pm    Post subject: Reply with quote

You may need to go to /usr/bin and delete all the files starting with i686. You shouldn't have them but eselect compiler screwed you over.
_________________
My emerge --info
Have you run revdep-rebuild lately? It's in gentoolkit and it's worth a shot if things don't work well.
Celebrating 5 years of Gentoo-ing.
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1408

PostPosted: Mon Nov 19, 2007 7:09 pm    Post subject: Reply with quote

loftwyr wrote:
You may need to go to /usr/bin and delete all the files starting with i686. You shouldn't have them but eselect compiler screwed you over.


Code:
fix_libtool.sh <proper compiler>
revdep-rebuild


would be more proper
_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper
Back to top
View user's profile Send private message
CoolGenie
n00b
n00b


Joined: 16 Nov 2007
Posts: 16

PostPosted: Mon Nov 19, 2007 9:31 pm    Post subject: Rada: Style moga byc stosowane szybko do zaznaczonego tekstu Reply with quote

Settin 'Executable File Formats / Emulations -> IA32 Emulation' solved all my problems: sandbox, gcc, and others compile without problems!

Thanks!
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1408

PostPosted: Mon Nov 19, 2007 10:03 pm    Post subject: Reply with quote

Please Add [Solved] to your post title.
_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper
Back to top
View user's profile Send private message
DancesWithWords
Apprentice
Apprentice


Joined: 29 Jun 2002
Posts: 253
Location: ottawa, canada

PostPosted: Tue Nov 20, 2007 4:22 pm    Post subject: Re: Rada: Style moga byc stosowane szybko do zaznaczonego te Reply with quote

CoolGenie wrote:
Settin 'Executable File Formats / Emulations -> IA32 Emulation' solved all my problems: sandbox, gcc, and others compile without problems!

Thanks!


I've checked my kernel 2.6.22-8 and there is no IA32 Emulation I can find. so what else do I looks at?

--
Bruce
Back to top
View user's profile Send private message
DancesWithWords
Apprentice
Apprentice


Joined: 29 Jun 2002
Posts: 253
Location: ottawa, canada

PostPosted: Tue Nov 20, 2007 5:59 pm    Post subject: Re: Rada: Style moga byc stosowane szybko do zaznaczonego te Reply with quote

CoolGenie wrote:
Settin 'Executable File Formats / Emulations -> IA32 Emulation' solved all my problems: sandbox, gcc, and others compile without problems!

Thanks!


I've checked my kernel and I've got this enable and I still can not compile sandbox.

--
DWW
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1408

PostPosted: Tue Nov 20, 2007 9:46 pm    Post subject: Re: Rada: Style moga byc stosowane szybko do zaznaczonego te Reply with quote

DancesWithWords wrote:
CoolGenie wrote:
Settin 'Executable File Formats / Emulations -> IA32 Emulation' solved all my problems: sandbox, gcc, and others compile without problems!

Thanks!


I've checked my kernel 2.6.22-8 and there is no IA32 Emulation I can find. so what else do I looks at?

--
Bruce

See the Gentoo Handbook:
Gentoo Linux Documentation --Configuring the Kernel
Code:

Code Listing 6: Selecting processor type and features
 
Processor type and features  --->
   [ ] Intel MCE Features
   [ ] AMD MCE Features
  Processor family (AMD-Opteron/Athlon64)  --->
    ( ) AMD-Opteron/Athlon64
    ( ) Intel EM64T
    ( ) Generic-x86-64
Executable file formats / Emulations  --->
   [*] IA32 Emulation

_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper
Back to top
View user's profile Send private message
DancesWithWords
Apprentice
Apprentice


Joined: 29 Jun 2002
Posts: 253
Location: ottawa, canada

PostPosted: Tue Nov 20, 2007 10:19 pm    Post subject: Re: Rada: Style moga byc stosowane szybko do zaznaczonego te Reply with quote

eyoung100 wrote:
DancesWithWords wrote:
CoolGenie wrote:
Settin 'Executable File Formats / Emulations -> IA32 Emulation' solved all my problems: sandbox, gcc, and others compile without problems!

Thanks!


I've checked my kernel 2.6.22-8 and there is no IA32 Emulation I can find. so what else do I looks at?

--
Bruce

See the Gentoo Handbook:
Gentoo Linux Documentation --Configuring the Kernel
Code:

Code Listing 6: Selecting processor type and features
 
Processor type and features  --->
   [ ] Intel MCE Features
   [ ] AMD MCE Features
  Processor family (AMD-Opteron/Athlon64)  --->
    ( ) AMD-Opteron/Athlon64
    ( ) Intel EM64T
    ( ) Generic-x86-64
Executable file formats / Emulations  --->
   [*] IA32 Emulation


Got this all sorted out. I was quoting my wrong box. The one I'm talking about does in fact have this enabled so my problem has to be something else.

--
DWW
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1408

PostPosted: Tue Nov 20, 2007 10:39 pm    Post subject: Reply with quote

Everyone running 64 bit try:
Code:
fix_libtool.sh x86_64-pc-linux-gnu


Everyone running 32 bit try:
Code:
fix_libtool.sh i686-pc-linux-gnu


then everyone:
Code:
revdep-rebuild


And just for a hunch:
Code:
emerge -pv sandbox

_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper
Back to top
View user's profile Send private message
DancesWithWords
Apprentice
Apprentice


Joined: 29 Jun 2002
Posts: 253
Location: ottawa, canada

PostPosted: Tue Nov 20, 2007 10:45 pm    Post subject: Reply with quote

eyoung100 wrote:
Everyone running 64 bit try:
Code:
fix_libtool.sh x86_64-pc-linux-gnu


Everyone running 32 bit try:
Code:
fix_libtool.sh i686-pc-linux-gnu


then everyone:
Code:
revdep-rebuild


And just for a hunch:
Code:
emerge -pv sandbox


Okay tried that and...
bbox linux # emerge -pv sandbox

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] sys-apps/sandbox-1.2.18.1-r2 0 kB


Then tried to emerge and same failure.
========================================

>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1 ...
* If configure fails with a 'cannot run C compiled programs' error, try this:
* FEATURES=-sandbox emerge sandbox
* Configuring sandbox for ABI=x86...
* econf: updating sandbox-1.2.18.1/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating sandbox-1.2.18.1/config.sub with /usr/share/gnuconfig/config.sub
../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib --build=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 i686-pc-linux-gnu-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log
*
* ERROR: sys-apps/sandbox-1.2.18.1-r2 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* sandbox-1.2.18.1-r2.ebuild, line 87: Called econf '--libdir=/usr/lib32' '--enable-multilib'
* ebuild.sh, line 638: Called die
* The specific snippet of code:
* die "econf failed"
* The die message:
* econf failed



--
DWW
Back to top
View user's profile Send private message
donmartio
Apprentice
Apprentice


Joined: 11 Dec 2004
Posts: 179

PostPosted: Tue Nov 20, 2007 11:54 pm    Post subject: Reply with quote

So the hard method worked for me.
I removed all i686-pc-linux-gnu* Files from /usr/bin and the sandbox compiled.

The main Problem was that i can't find the script fix_libtool.sh

I made a backup of these files because i fear that simple deleting them could break something.
So if anyone tells me which package contains fix_libtool.sh then i'll give it a try.

So far so good
Greetings DonMartio
_________________
Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live.
Back to top
View user's profile Send private message
DancesWithWords
Apprentice
Apprentice


Joined: 29 Jun 2002
Posts: 253
Location: ottawa, canada

PostPosted: Wed Nov 21, 2007 2:02 pm    Post subject: Reply with quote

donmartio wrote:
So the hard method worked for me.
I removed all i686-pc-linux-gnu* Files from /usr/bin and the sandbox compiled.

The main Problem was that i can't find the script fix_libtool.sh

I made a backup of these files because i fear that simple deleting them could break something.
So if anyone tells me which package contains fix_libtool.sh then i'll give it a try.

So far so good
Greetings DonMartio


for me it is here...
/sbin/fix_libtool_files.sh

Personal I didn't want to remove the i686 files just for that reason. Though this issue with sandbox is getting somewhat trying and I'd like to move on to more annoying problems I've got with my box.
--
DWW
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1408

PostPosted: Wed Nov 21, 2007 4:53 pm    Post subject: Reply with quote

Sorry all, normally everything in sbin will run without the path, but I forgot its:
Code:

./fix_libtool_files.sh

_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper
Back to top
View user's profile Send private message
DancesWithWords
Apprentice
Apprentice


Joined: 29 Jun 2002
Posts: 253
Location: ottawa, canada

PostPosted: Wed Nov 21, 2007 5:39 pm    Post subject: Reply with quote

eyoung100 wrote:
Everyone running 64 bit try:
Code:
fix_libtool.sh x86_64-pc-linux-gnu


Everyone running 32 bit try:
Code:
fix_libtool.sh i686-pc-linux-gnu


then everyone:
Code:
revdep-rebuild


And just for a hunch:
Code:
emerge -pv sandbox


Retried this and still no go, still experiencing the same errors.

--
DWW
Back to top
View user's profile Send private message
fiag
n00b
n00b


Joined: 23 Jun 2005
Posts: 12

PostPosted: Thu Nov 29, 2007 10:27 am    Post subject: Reply with quote

DancesWithWords wrote:
eyoung100 wrote:
Everyone running 64 bit try:
Code:
fix_libtool.sh x86_64-pc-linux-gnu


Everyone running 32 bit try:
Code:
fix_libtool.sh i686-pc-linux-gnu


then everyone:
Code:
revdep-rebuild


And just for a hunch:
Code:
emerge -pv sandbox


Okay tried that and...
bbox linux # emerge -pv sandbox

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] sys-apps/sandbox-1.2.18.1-r2 0 kB


Then tried to emerge and same failure.
========================================

>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1 ...
* If configure fails with a 'cannot run C compiled programs' error, try this:
* FEATURES=-sandbox emerge sandbox
* Configuring sandbox for ABI=x86...
* econf: updating sandbox-1.2.18.1/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating sandbox-1.2.18.1/config.sub with /usr/share/gnuconfig/config.sub
../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib --build=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 i686-pc-linux-gnu-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log
*
* ERROR: sys-apps/sandbox-1.2.18.1-r2 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* sandbox-1.2.18.1-r2.ebuild, line 87: Called econf '--libdir=/usr/lib32' '--enable-multilib'
* ebuild.sh, line 638: Called die
* The specific snippet of code:
* die "econf failed"
* The die message:
* econf failed



--
DWW


I had the same problem. It had been fixed in this way.
--host=i686-pc-linux-gnu on AMD64 will cause this problem. i686-pc-linux-gnu couldn't work.
try to move /usr/bin/i686-pc-linux-gnu-* to other path (or delete), so ./configure can not find them, then it use x86_64-pc-linux-gnu .
Back to top
View user's profile Send private message
DancesWithWords
Apprentice
Apprentice


Joined: 29 Jun 2002
Posts: 253
Location: ottawa, canada

PostPosted: Thu Nov 29, 2007 2:42 pm    Post subject: Reply with quote

fiag wrote:
DancesWithWords wrote:
eyoung100 wrote:
Everyone running 64 bit try:
Code:
fix_libtool.sh x86_64-pc-linux-gnu


Everyone running 32 bit try:
Code:
fix_libtool.sh i686-pc-linux-gnu


then everyone:
Code:
revdep-rebuild


And just for a hunch:
Code:
emerge -pv sandbox


Okay tried that and...
bbox linux # emerge -pv sandbox

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] sys-apps/sandbox-1.2.18.1-r2 0 kB


Then tried to emerge and same failure.
========================================

>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1 ...
* If configure fails with a 'cannot run C compiled programs' error, try this:
* FEATURES=-sandbox emerge sandbox
* Configuring sandbox for ABI=x86...
* econf: updating sandbox-1.2.18.1/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating sandbox-1.2.18.1/config.sub with /usr/share/gnuconfig/config.sub
../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib --build=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 i686-pc-linux-gnu-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log
*
* ERROR: sys-apps/sandbox-1.2.18.1-r2 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* sandbox-1.2.18.1-r2.ebuild, line 87: Called econf '--libdir=/usr/lib32' '--enable-multilib'
* ebuild.sh, line 638: Called die
* The specific snippet of code:
* die "econf failed"
* The die message:
* econf failed



--
DWW


I had the same problem. It had been fixed in this way.
--host=i686-pc-linux-gnu on AMD64 will cause this problem. i686-pc-linux-gnu couldn't work.
try to move /usr/bin/i686-pc-linux-gnu-* to other path (or delete), so ./configure can not find them, then it use x86_64-pc-linux-gnu .


I solved the problem by re-installing. Not the best solution, but the only one that seem to address my needs as solutions where not coming fast enough.
I appreciate your suggestion, and help.
--
DWW
Back to top
View user's profile Send private message
cessman4life
Tux's lil' helper
Tux's lil' helper


Joined: 14 Apr 2005
Posts: 141

PostPosted: Sat Dec 01, 2007 7:11 am    Post subject: Reply with quote

I had the same problem after breaking gcc. Simply reinstalled. However, i found this fix on another website. i guess if it's not supposed to be posted here it will be removed:

http://wiki.sabayonlinux.org/index.php?title=HOWTO:_Use_Sabayon_LiveDVD/CD_to_recover_GCC
Back to top
View user's profile Send private message
cyrre
n00b
n00b


Joined: 02 Jul 2007
Posts: 26

PostPosted: Sat Dec 08, 2007 11:26 pm    Post subject: Reply with quote

I had similar problems after updating gcc to 4.1.2 on my newly installed Gentoo (x86_64). NOTHING would compile at all and the errors were different each time..
None of the mentioned solutions worked for me (emerge sandbox, fix_libtool.sh etc).

I was on my way to reinstall but first I tried to boot the 2007.0 minimal CD and chrooted into the installed system.

I re-emerged sandbox and libtool in the chrooted environment and rebooted.. and everything was fine! No more problems at all. 8O :)
Back to top
View user's profile Send private message
muffy
n00b
n00b


Joined: 15 Sep 2003
Posts: 28
Location: :noitacoL

PostPosted: Fri Dec 28, 2007 3:25 pm    Post subject: Reply with quote

loftwyr wrote:
You may need to go to /usr/bin and delete all the files starting with i686. You shouldn't have them but eselect compiler screwed you over.


Thanks, that got it compiled.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64 All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum