LINUX.ORG.RU

Проблема со сборкой sandbox, gcc и других(configure: error: cannot run C compiled programs.)

 , ,


0

1
hecking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking environment state... ok
checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc -m32
checking whether the C compiler works... checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... 
checking whether we are cross compiling... no
checking for suffix of object files... configure: error: in `/var/tmp/portage/sys-apps/sandbox-2.5/work/build-x86':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details
o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... 
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-apps/sandbox-2.5/work/build-x86/config.log
 * ERROR: sys-apps/sandbox-2.5 failed (compile phase):
 *   econf failed
 * 
 * Call stack:
yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89...  *          ebuild.sh, line   85:  Called src_compile
 *        environment, line 2562:  Called multijob_child_init 'sb_configure'
 *        environment, line 2090:  Called sb_configure
 *        environment, line 2509:  Called econf
 *   phase-helpers.sh, line  467:  Called die
 * The specific snippet of code:
 *                      die "econf failed"
 * 
 * If you need support, post the output of `emerge --info '=sys-apps/sandbox-2.5'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/sandbox-2.5'`.
 * If configure failed with a 'cannot run C compiled programs' error, try this:
none needed
 * FEATURES=-sandbox emerge sandbox
checking for style of include used by make... /usr/lib64/portage/bin/isolated-functions.sh: line 214: wait: `econf failed': не идентификатор  процесса или правильное имя задачи
 * The complete build log is located at '/var/tmp/portage/sys-apps/sandbox-2.5/temp/build.log'.
GNU
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/sandbox-2.5/temp/environment'.
checking dependency style of x86_64-pc-linux-gnu-gcc...  * Working directory: '/var/tmp/portage/sys-apps/sandbox-2.5/work/build-x86'
 * S: '/var/tmp/portage/sys-apps/sandbox-2.5/work/sandbox-2.5'
gcc3
checking whether x86_64-pc-linux-gnu-gcc and cc understand -c and -o together... yes
checking for library containing strerror... none required
checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes

С -sandbox какая же ситуация.
Как это поправить?
cast megabaks

★★★★★

hecking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc -m32
/var/tmp/portage/sys-apps/sandbox-2.5/work/build-x86

Вы случаем не пытаетесь собирать 32битную систему с AMD64 профилем?

anonymous ()
Ответ на: комментарий от deterok

Да, и не забудь собрать портфель — он скоро тебе понадобится.

anonymous ()
Ответ на: комментарий от anonymous

Все ок, еще раз спасибо, настраивал с нуля конфиг для 3.5.1 ...

deterok ★★★★★ ()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.