emerge rxvt-unicode出错！请帮我看看

well

/var/tmp/portage/x11-terms/rxvt-unicode-8.1/temp $ cat build.log
>>> Unpacking source...
>>> Unpacking rxvt-unicode-8.1.tar.bz2 to /var/tmp/portage/x11-terms/rxvt-unicod
e-8.1/work
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/x11-terms/rxvt-unicode-8.1/work/rxvt-un
icode-8.1 ...
* econf: updating rxvt-unicode-8.1/config.guess with /usr/share/gnuconfig/confi
g.guess
* econf: updating rxvt-unicode-8.1/config.sub with /usr/share/gnuconfig/config.
sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --inf
odir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var
/lib --enable-everything --enable-xft --enable-perl --disable-text-blink --disab
le-iso14755 --build=i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu

configuring for rxvt 8.1

checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
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 ANSI C... none needed
checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether i686-pc-linux-gnu-g++ accepts -g... yes
checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E
checking for a BSD-compatible install... /usr/bin/install -c
checking for egrep... grep -E
checking for AIX... no
checking for library containing strerror... none required
checking for working libsupc++... ok
checking for setlocale... no
checking for gethostbyname in -lnsl... no
checking for socket... no
checking for socket in -lsocket... no
checking for mv... /bin/mv
checking for cp... /bin/cp
checking for ln... /bin/ln
checking for sed... /bin/sed
checking for echo... /bin/echo
checking for cmp... /usr/bin/cmp
checking for tic... /usr/bin/tic
checking how to run the C++ preprocessor... i686-pc-linux-gnu-g++ -E
checking for X... libraries /usr/X11R6/lib, headers in standard search path
checking for dnet_ntoa in -ldnet... no
checking for dnet_ntoa in -ldnet_stub... no
checking for gethostbyname... (cached) no
checking for gethostbyname in -lnsl... (cached) no
checking for gethostbyname in -lbsd... no
checking for connect... no
checking for connect in -lsocket... no
checking for remove... no
checking for remove in -lposix... no
checking for shmat... no
checking for shmat in -lipc... no
checking for IceConnectionNumber in -lICE... no
checking for libXpm... -I, -L/usr/X11R6/lib
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for ANSI C header files... no
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 assert.h usability... yes
checking assert.h presence... yes
checking for assert.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking stdarg.h usability... yes
checking stdarg.h presence... yes
checking for stdarg.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking for unistd.h... (cached) yes
checking sys/byteorder.h usability... no
checking sys/byteorder.h presence... no
checking for sys/byteorder.h... no
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/sockio.h usability... no
checking sys/sockio.h presence... no
checking for sys/sockio.h... no
checking sys/strredir.h usability... no
checking sys/strredir.h presence... no
checking for sys/strredir.h... no
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for stdint.h... (cached) yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking cwchar usability... yes
checking cwchar presence... yes
checking for cwchar... yes
checking clocale usability... yes
checking clocale presence... yes
checking for clocale... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether termios.h and sys/ioctl.h may both be included... yes
checking for -rpath dynamic library path recording... no
checking for -R dynamic library path recording... no
checking for XPointer... yes
checking for XLIB_ILLEGAL_ACCESS... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for mode_t... yes
checking for pid_t... yes
checking for uid_t in sys/types.h... yes
checking for short... yes
checking size of short... configure: error: cannot compute sizeof (short), 77
See `config.log' for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/x11-terms/rxvt-unicode-8.1/work/rxvt-unicode-8.1/config.log

!!! ERROR: x11-terms/rxvt-unicode-8.1 failed.
Call stack:
  ebuild.sh, line 1615:   Called dyn_compile
  ebuild.sh, line 972:   Called qa_call 'src_compile'
  ebuild.sh, line 44:   Called src_compile
  rxvt-unicode-8.1.ebuild, line 52:   Called econf '--enable-everything' '--enab
le-xft' '--enable-perl' '--disable-text-blink' '--disable-iso14755'
  ebuild.sh, line 578:   Called die

!!! econf failed
!!! If you need support, post the topmost build error, and the call stack if rel
evant.
!!! A complete build log is located at '/var/tmp/portage/x11-terms/rxvt-unicode-
8.1/temp/build.log'.

well

内容太丰富，放在附件里面，谢谢

zhllg

Please be aware that: http://bugs.gentoo.org is the place you should look for solutions first.
Even if you can not find any similar bugs, please post your search result on bugs.gentoo.org in order to testify that you have searched on bugs.gentoo.org

Theoretically speaking, it is the maintainer of the package whom you should ask first whenever you find problems in a package.