pthをインストールするとeconfが失敗します。

pthをインストールするとeconfが失敗します。

私はGentooを使い始めましたが、Portageのインストーラを使用するのに少し難しいことがあります。そうでない場合を除いて、それは素晴らしいと自動です。

私がインストールしようとしている多くのプログラム(git、gedit、chrome、nautilus)はそれが何であれ、pthに依存します。ただし、econfエラーのため失敗します。

   ERROR: dev-libs/pth-2.0.7-r3::gentoo failed (configure phase):
     econf failed

   Call stack:
            ebuild.sh, line   93:  Called src_configure
          environment, line 2881:  Called econf '--disable-static'
     phase-helpers.sh, line  577:  Called die
   The specific snippet of code:
                die "econf failed"

   If you need support, post the output of `emerge --info '=dev-libs/pth-2.0.7-r3::gentoo'`,
   the complete build log and the output of `emerge -pqv '=dev-libs/pth-2.0.7-r3::gentoo'`.
   The complete build log is located at '/var/tmp/portage/dev-libs/pth-2.0.7-r3/temp/build.log'.
   The ebuild environment file is located at '/var/tmp/portage/dev-libs/pth-2.0.7-r3/temp/environment'.
   Working directory: '/var/tmp/portage/dev-libs/pth-2.0.7-r3/work/pth-2.0.7'

これがイビルドラインです

[ebuild  N    ] dev-libs/pth-2.0.7-r3  USE="-debug -static-libs"

そしてメッセージが表示されます長さが長いのでペーストビンを着ました。

ビルドログ:

 * Package:    dev-libs/pth-2.0.7-r3
 * Repository: gentoo
 * Maintainer: [email protected]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux multilib userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking pth-2.0.7.tar.gz to /var/tmp/portage/dev-libs/pth-2.0.7-r3/work
>>> Source unpacked in /var/tmp/portage/dev-libs/pth-2.0.7-r3/work
>>> Preparing source in /var/tmp/portage/dev-libs/pth-2.0.7-r3/work/pth-2.0.7 ...
 * Applying pth-2.0.5-parallelfix.patch ...                              [ ok ]
 * Applying pth-2.0.6-ldflags.patch ...                                  [ ok ]
 * Applying pth-2.0.6-sigstack.patch ...                                 [ ok ]
 * Applying pth-2.0.7-parallel-install.patch ...                         [ ok ]
 * Applying pth-2.0.7-ia64.patch ...                                     [ ok ]
 * Applying pth-2.0.7-kernel-3.patch ...                                 [ ok ]
 * Replacing obsolete head/tail with POSIX compliant ones
 *  - fixed aclocal.m4
 *  - fixed configure
 * Running elibtoolize in: pth-2.0.7/
 *   Applying portage/1.5.10 patch ...
 *   Applying max_cmd_len/1.5.20 patch ...
 *   Applying sed/1.5.6 patch ...
 *   Applying as-needed/1.5 patch ...
 *   Applying target-nm/2.4.2 patch ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-libs/pth-2.0.7-r3/work/pth-2.0.7 ...
 * econf: updating pth-2.0.7/config.sub with /usr/share/gnuconfig/config.sub
 * econf: updating pth-2.0.7/config.guess with /usr/share/gnuconfig/config.guess
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-static
./configure: line 286: /tmp/autoconf.25970: Permission denied
./configure: line 297: /tmp/autoconf.25970: Permission denied
./configure: line 310: /tmp/autoconf.25970: No such file or directory
 * ERROR: dev-libs/pth-2.0.7-r3::gentoo failed (configure phase):
 *   econf failed
 * 
 * Call stack:
 *          ebuild.sh, line   93:  Called src_configure
 *        environment, line 2887:  Called econf '--disable-static'
 *   phase-helpers.sh, line  577:  Called die
 * The specific snippet of code:
 *              die "econf failed"
 * 
 * If you need support, post the output of `emerge --info '=dev-libs/pth-2.0.7-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/pth-2.0.7-r3::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-libs/pth-2.0.7-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/pth-2.0.7-r3/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-libs/pth-2.0.7-r3/work/pth-2.0.7'
 * S: '/var/tmp/portage/dev-libs/pth-2.0.7-r3/work/pth-2.0.7'

ここで何が間違っているのですか?

ベストアンサー1

/tmp何らかの理由でルートを除いては書き込めませんでした。この問題を解決しました。

chmod a+w /tmp

どうやってこれが起こったのかわかりません。新しくインストールしたものなので、意図的に権限をdrwxr-xr-

おすすめ記事