Главная » Форум » Gentoo Linux » Система portage

[РЕШЕНО] Ошибка в компиляции htop, помогите пожалуйста.

undertaket 19 октября, 2012 - 16:07

Устанавливаю htop и выдает такую картину:

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-process/htop-1.0.1/work/htop-1.0.1/config.log
* ERROR: sys-process/htop-1.0.1 failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 85: Called src_configure
* environment, line 1437: Called econf '--disable-openvz' '--enable-cgroup' '--disable-vserver' '--enable-unicode' '--enable-taskstats'
* 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-process/htop-1.0.1'`,
* the complete build log and the output of `emerge -pqv '=sys-process/htop-1.0.1'`.
* The complete build log is located at '/var/tmp/portage/sys-process/htop-1.0.1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-process/htop-1.0.1/temp/environment'.
* Working directory: '/var/tmp/portage/sys-process/htop-1.0.1/work/htop-1.0.1'
* S: '/var/tmp/portage/sys-process/htop-1.0.1/work/htop-1.0.1'

>>> Failed to emerge sys-process/htop-1.0.1, Log file:

>>> '/var/tmp/portage/sys-process/htop-1.0.1/temp/build.log'

* Messages for package sys-process/htop-1.0.1:

* To use lsof features in htop(what processes are accessing
* what files), you must have sys-process/lsof installed.
* ERROR: sys-process/htop-1.0.1 failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 85: Called src_configure
* environment, line 1437: Called econf '--disable-openvz' '--enable-cgroup' '--disable-vserver' '--enable-unicode' '--enable-taskstats'
* 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-process/htop-1.0.1'`,
* the complete build log and the output of `emerge -pqv '=sys-process/htop-1.0.1'`.
* The complete build log is located at '/var/tmp/portage/sys-process/htop-1.0.1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-process/htop-1.0.1/temp/environment'.
* Working directory: '/var/tmp/portage/sys-process/htop-1.0.1/work/htop-1.0.1'
* S: '/var/tmp/portage/sys-process/htop-1.0.1/work/htop-1.0.1'

Впервые такое вижу при установке этого пакета. Подключён удалённо через ssh возможна ли проблема из за этого, устанавливаю от root. Помогите пожалуйста.
...

‹ недоступны все пакеты как исправить? Установка wine ›
»

* If you need support, post

Автор _SerEga_, дата создания 19 октября, 2012 - 16:26.
* If you need support, post the output of `emerge --info '=sys-process/htop-1.0.1'`,
* the complete build log and the output of `emerge -pqv '=sys-process/htop-1.0.1'`.
* The complete build log is located at '/var/tmp/portage/sys-process/htop-1.0.1/temp/build.log'.

или можно попробовать версию 1.0.1-r1, или заглянуть в багзилу

»

Маленькое уточнение, с этой

Автор undertaket, дата создания 19 октября, 2012 - 16:34.

Маленькое уточнение, с этой ошибкой не один пакет не собирается! Скачивается но не собирается!

»

/

Автор Anarchist, дата создания 19 октября, 2012 - 16:43.
undertaket написал(а):
Маленькое уточнение, с этой ошибкой не один пакет не собирается! Скачивается но не собирается!

ИМХО похоже на http://gentoo.ru/content/ya-udalilslomal-sistemnyy-paket-i-teper-gentoo-ne-gruzitsya-neuzheli-pereustanavlivatsya

—

:wq
--
Live free or die

»

Того log'a, что ты приводишь

Автор Zharptah, дата создания 19 октября, 2012 - 17:28.

Того log'a, что ты приводишь, недостаточно. У тебя, похоже, проблема на стадии конфигурирования. Нужно вывод конфигуратора, как раз последние строки консоли перед этим логом. Чего-то не хватает для нормальной компиляции, я думаю.

»

tar:

Автор undertaket, дата создания 19 октября, 2012 - 19:14.
tar: htop-1.0.1/BatteryMeter.c: time stamp 2012-02-03 04:49:13 is 269690999.350282098 s in the future
tar: htop-1.0.1/config.h: time stamp 2011-12-27 04:47:30 is 266407696.348307757 s in the future
tar: htop-1.0.1/Meter.c: time stamp 2012-02-03 06:06:38 is 269695644.345619873 s in the future
tar: htop-1.0.1/htop.desktop: time stamp 2011-08-27 02:57:35 is 255860301.34404516 s in the future
tar: htop-1.0.1/config.h.in: time stamp 2011-12-27 04:47:31 is 266407697.342176527 s in the future
tar: htop-1.0.1/RichString.c: time stamp 2011-12-27 04:53:45 is 266408071.341179942 s in the future
tar: htop-1.0.1/OpenFilesScreen.h: time stamp 2011-12-27 04:55:08 is 266408154.340229208 s in the future
tar: htop-1.0.1/String.h: time stamp 2011-12-27 04:55:08 is 266408154.339147077 s in the future
tar: htop-1.0.1/ClockMeter.c: time stamp 2011-12-27 04:52:21 is 266407987.337592808 s in the future
tar: htop-1.0.1/Process.h: time stamp 2011-12-27 04:55:08 is 266408154.336490495 s in the future
tar: htop-1.0.1/RichString.h: time stamp 2011-12-27 04:55:08 is 266408154.334414135 s in the future
tar: htop-1.0.1/ClockMeter.h: time stamp 2011-12-27 04:55:08 is 266408154.333843283 s in the future
tar: htop-1.0.1/AffinityPanel.h: time stamp 2011-12-27 04:55:08 is 266408154.332593147 s in the future
tar: htop-1.0.1/CRT.h: time stamp 2011-12-27 04:55:08 is 266408154.330907698 s in the future
tar: htop-1.0.1/ListItem.c: time stamp 2011-12-27 04:52:34 is 266408000.329781522 s in the future
tar: htop-1.0.1/SwapMeter.c: time stamp 2011-12-27 04:51:32 is 266407938.326897791 s in the future
tar: htop-1.0.1/CPUMeter.h: time stamp 2011-12-27 04:55:08 is 266408154.326230278 s in the future
tar: htop-1.0.1/Panel.c: time stamp 2012-02-03 06:45:01 is 269697947.323982842 s in the future
tar: htop-1.0.1/Panel.h: time stamp 2012-02-03 06:49:19 is 269698205.322986358 s in the future
tar: htop-1.0.1/ProcessList.h: time stamp 2012-02-03 06:49:19 is 269698205.321219912 s in the future
tar: htop-1.0.1/Object.h: time stamp 2011-12-27 04:55:08 is 266408154.319992093 s in the future
tar: htop-1.0.1/LoadAverageMeter.c: time stamp 2011-12-27 04:54:39 is 266408125.318456748 s in the future
tar: htop-1.0.1/AffinityPanel.c: time stamp 2011-12-27 04:50:51 is 266407897.31714466 s in the future
tar: htop-1.0.1/Process.c: time stamp 2011-12-27 04:54:07 is 266408093.314083104 s in the future
tar: htop-1.0.1/ScreenManager.h: time stamp 2011-12-27 04:55:08 is 266408154.31249759 s in the future
tar: htop-1.0.1/MetersPanel.h: time stamp 2011-12-27 04:55:08 is 266408154.31112356 s in the future
tar: htop-1.0.1/String.c: time stamp 2011-12-27 04:53:20 is 266408046.308161476 s in the future
tar: htop-1.0.1/INSTALL: time stamp 2011-08-27 02:57:35 is 255860301.306322405 s in the future
tar: htop-1.0.1/UsersTable.h: time stamp 2011-12-27 04:55:08 is 266408154.305271319 s in the future
tar: htop-1.0.1/TasksMeter.h: time stamp 2011-12-27 04:55:08 is 266408154.303961788 s in the future
tar: htop-1.0.1/NEWS: time stamp 2011-11-21 09:55:49 is 263315795.302449637 s in the future
tar: htop-1.0.1/CRT.c: time stamp 2011-12-27 04:52:55 is 266408021.299535614 s in the future
tar: htop-1.0.1/htop.h: time stamp 2012-02-03 06:49:19 is 269698205.298410736 s in the future
tar: htop-1.0.1/TraceScreen.h: time stamp 2012-02-03 04:45:14 is 269690760.296493822 s in the future
tar: htop-1.0.1/AUTHORS: time stamp 2011-08-27 02:57:34 is 255860300.295143727 s in the future
tar: htop-1.0.1/ScreenManager.c: time stamp 2011-12-27 04:53:40 is 266408066.293701907 s in the future
tar: htop-1.0.1/ColorsPanel.c: time stamp 2011-12-27 04:53:04 is 266408030.292120195 s in the future
tar: htop-1.0.1/TraceScreen.c: time stamp 2012-01-04 01:19:53 is 267086439.290861941 s in the future
tar: htop-1.0.1/DisplayOptionsPanel.h: time stamp 2011-12-27 04:55:08 is 266408154.28839834 s in the future
tar: htop-1.0.1/ProcessList.c: time stamp 2012-02-03 06:45:11 is 269697957.28631475 s in the future
tar: htop-1.0.1/CheckItem.c: time stamp 2011-12-27 04:52:06 is 266407972.284929778 s in the future
tar: htop-1.0.1/AvailableColumnsPanel.h: time stamp 2011-12-27 04:55:08 is 266408154.283496069 s in the future
tar: htop-1.0.1/compile: time stamp 2011-08-27 03:18:38 is 255861564.28184782 s in the future
tar: htop-1.0.1/HostnameMeter.c: time stamp 2011-12-27 04:54:43 is 266408129.279347946 s in the future
tar: htop-1.0.1/Makefile.in: time stamp 2012-02-03 04:45:14 is 269690760.273906482 s in the future
tar: htop-1.0.1/Object.c: time stamp 2011-12-27 04:52:30 is 266407996.271627898 s in the future
tar: htop-1.0.1/ColorsPanel.h: time stamp 2011-12-27 04:55:08 is 266408154.26958702 s in the future
tar: htop-1.0.1/Vector.c: time stamp 2011-12-27 04:51:16 is 266407922.267236757 s in the future
tar: htop-1.0.1/DisplayOptionsPanel.c: time stamp 2011-12-27 04:53:58 is 266408084.266258389 s in the future
tar: htop-1.0.1/scripts/MakeHeader.py: time stamp 2011-12-27 04:26:17 is 266406423.264792208 s in the future
tar: htop-1.0.1/scripts: time stamp 2012-02-17 01:37:04 is 270889070.263217593 s in the future
tar: htop-1.0.1/missing: time stamp 2011-08-27 03:18:38 is 255861564.26078674 s in the future
tar: htop-1.0.1/COPYING: time stamp 2011-08-27 02:57:34 is 255860300.259331486 s in the future
tar: htop-1.0.1/Hashtable.h: time stamp 2011-12-27 04:55:08 is 266408154.257571817 s in the future
tar: htop-1.0.1/config.guess: time stamp 2011-08-27 03:18:38 is 255861564.255647534 s in the future
tar: htop-1.0.1: time stamp 2012-02-17 01:37:04 is 270889070.253796491 s in the future
>>> Source unpacked in /var/tmp/portage/sys-process/htop-1.0.1/work
>>> Preparing source in /var/tmp/portage/sys-process/htop-1.0.1/work/htop-1.0.1 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-process/htop-1.0.1/work/htop-1.0.1 ...
 * econf: updating htop-1.0.1/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating htop-1.0.1/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-openvz --enable-cgroup --disable-vserver --enable-unicode --enable-taskstats
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... i686-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
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... configure: error: newly created file is older than distributed files!
Check your system clock

До ошибки это выглядит так...

»

Поменяй батарейку на мамке,

Автор eegorov, дата создания 19 октября, 2012 - 19:40.

Поменяй батарейку на мамке, выстави время...

»

Большое спасибо помогло... А

Автор undertaket, дата создания 19 октября, 2012 - 19:54.

Большое спасибо помогло... А можешь указать конкретную строчку где посмотрел...

»

Ты не поверишь

Автор eegorov, дата создания 19 октября, 2012 - 20:31.
undertaket написал(а):
checking whether build environment is sane... configure: error: newly created file is older than distributed files!
Check your system clock
»

Спасибо!

Автор undertaket, дата создания 20 октября, 2012 - 14:26.

Спасибо!

»

Настройки просмотра комментариев

Выберите нужный метод показа комментариев и нажмите "Сохранить установки".