Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Issues going from stage2 to stage3
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64
View previous topic :: View next topic  
Author Message
fbvortex
n00b
n00b


Joined: 01 Jul 2005
Posts: 22

PostPosted: Fri Jul 01, 2005 7:53 pm    Post subject: Issues going from stage2 to stage3 Reply with quote

I started my install as a stage1 on a dual K8/248 Tyan S2882G3NR setup.

The bootstrap script completed OK.

However, when doing
Code:
emerge --emptytree system

I got a failure trying emerge dante. The combined stdout and stderr from that emerge (with the unpacking lines elided due to containing terminal escapes) is as follows:

Code:

>>> Source unpacked.
/usr/portage/net-proxy/dante/dante-1.1.15-r1.ebuild: line 44: libtoolize: command not found
 * econf: updating dante-1.1.15/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating dante-1.1.15/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --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-debug --enable-libwrap --with-pam --with-socks-conf=/etc/socks/socks.conf --with-sockd-conf=/etc/socks/sockd.conf
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
Configuring Dante 1.1.15:
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 x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip
checking for style of include used by make... GNU
checking for x86_64-pc-linux-gnu-gcc... x86_64-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 x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ANSI C... none needed
checking dependency style of x86_64-pc-linux-gnu-gcc... gcc3
checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
checking for egrep... grep -E
checking for AIX... no
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for ld used by x86_64-pc-linux-gnu-gcc... /usr/x86_64-pc-linux-gnu/bin/ld
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/x86_64-pc-linux-gnu-nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
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 dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for x86_64-pc-linux-gnu-g++... x86_64-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether x86_64-pc-linux-gnu-g++ accepts -g... yes
checking dependency style of x86_64-pc-linux-gnu-g++... gcc3
checking how to run the C++ preprocessor... x86_64-pc-linux-gnu-g++ -E
checking for x86_64-pc-linux-gnu-g77... x86_64-pc-linux-gnu-g77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether x86_64-pc-linux-gnu-g77 accepts -g... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/x86_64-pc-linux-gnu-nm -B output from x86_64-pc-linux-gnu-gcc object... ok
checking for objdir... .libs
checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar
checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
checking for x86_64-pc-linux-gnu-strip... (cached) x86_64-pc-linux-gnu-strip
checking if x86_64-pc-linux-gnu-gcc static flag  works... yes
checking if x86_64-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
checking for x86_64-pc-linux-gnu-gcc option to produce PIC... -fPIC
checking if x86_64-pc-linux-gnu-gcc PIC flag -fPIC works... yes
checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... yes
checking whether the x86_64-pc-linux-gnu-gcc linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by x86_64-pc-linux-gnu-g++... /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the x86_64-pc-linux-gnu-g++ linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for x86_64-pc-linux-gnu-g++ option to produce PIC... -fPIC
checking if x86_64-pc-linux-gnu-g++ PIC flag -fPIC works... yes
checking if x86_64-pc-linux-gnu-g++ supports -c -o file.o... yes
checking whether the x86_64-pc-linux-gnu-g++ linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for x86_64-pc-linux-gnu-g77 option to produce PIC... -fPIC
checking if x86_64-pc-linux-gnu-g77 PIC flag -fPIC works... yes
checking if x86_64-pc-linux-gnu-g77 supports -c -o file.o... yes
checking whether the x86_64-pc-linux-gnu-g77 linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
checking for compiler flags... none
checking for support for -pipe compiler flag... yes
checking for support for -Wbounded compiler flag... no
checking for compilation with debugging... yes
checking for warning flags... none
checking for compliation with DIAGNOSTIC... no
checking whether libwrap should be disabled... no
checking for bison... bison -y
checking for gawk... (cached) gawk
checking for flex... flex
checking for yywrap in -lfl... yes
checking lex output file root... lex.yy
checking whether yytext is a pointer... yes
checking for char... yes
checking size of char... 1
checking for short... yes
checking size of short... 2
checking for int... yes
checking size of int... 4
checking for long... yes
checking size of long... 8
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking paths.h usability... yes
checking paths.h presence... yes
checking for paths.h... yes
checking for strings.h... (cached) yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking for unistd.h... (cached) yes
checking crypt.h usability... yes
checking crypt.h presence... yes
checking for crypt.h... yes
checking sys/file.h usability... yes
checking sys/file.h presence... yes
checking for sys/file.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking tcpd.h usability... yes
checking tcpd.h presence... yes
checking for tcpd.h... yes
checking shadow.h usability... yes
checking shadow.h presence... yes
checking for shadow.h... yes
checking ifaddrs.h usability... yes
checking ifaddrs.h presence... yes
checking for ifaddrs.h... yes
checking sys/sem.h usability... yes
checking sys/sem.h presence... yes
checking for sys/sem.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking sys/ipc.h usability... yes
checking sys/ipc.h presence... yes
checking for sys/ipc.h... yes
checking arpa/nameser.h usability... yes
checking arpa/nameser.h presence... yes
checking for arpa/nameser.h... yes
checking for netinet/ip_var.h... no
checking for resolv.h... yes
checking for hardcoded domainname... no
checking for socks config file location... /etc/socks/socks.conf
checking for sockd config file location... /etc/socks/sockd.conf
checking for pid file location... default
checking for dlfcn.h... (cached) yes
checking whether all interposition usage should be disabled... no
checking whether interposition in the client should be disabled... no
checking whether interposition in the server should be disabled... no
checking sys/sockio.h usability... no
checking sys/sockio.h presence... no
checking for sys/sockio.h... no
checking whether <sys/types.h> defines const... no
checking for an ANSI C-conforming const... yes
checking for supported routing socket communication... yes
checking whether <netdb.h> declares h_errno... yes
checking for struct ip_opts in <netinet/in.h>... no
checking whether <sys/types.h> defines inline... no
checking for inline... inline
checking for uid_t in sys/types.h... yes
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking for in6_addr... yes
checking for sockaddr_storage in sys/socket.h... yes
checking to see if openlog accepts LOG_PERROR... yes
checking to see if stdlib.h defines EXIT_FAILURE... yes
checking whether <sys/socket.h> uses AF_UNIX... no
checking for SIGINFO... no
checking to see if MSG_WAITALL exists... yes
checking whether a working SO_SNDLOWAT exists... disabled
configure: WARNING: performance in the server might be degraded without support for the SO_SNDLOWAT socket option
checking whether realloc with a NULL pointer calls malloc... yes
checking whether free can be called with NULL... yes
checking prototypes for accept... ok
checking prototypes for bind... ok
checking prototypes for connect... ok
checking prototypes for gethostbyaddr... ok
checking prototypes for getpeername... ok
checking prototypes for getsockname... ok
checking prototypes for read... ok
checking prototypes for readv... ok
checking prototypes for recv... ok
checking prototypes for recvfrom... ok
checking prototypes for recvmsg... ok
checking prototypes for send... ok
checking prototypes for sendmsg... ok
checking prototypes for sendto... ok
checking prototypes for write... ok
checking prototypes for writev... ok
checking if getsockopt needs cast... no
checking to see if dlopen param has DL_ and not RTLD_ prefix... yes
checking to see if SV_INTERRUPT should be used... no
checking if cmsghdr exists in <sys/socket.h>... yes
checking for CMSG_SPACE in sys/socket.h... yes
checking for CMSG_LEN in sys/socket.h... yes
checking for sa_len in sockaddr... no
checking to see if malloc_options exists... no
checking to see if __progname exists... yes
checking for library containing crypt... -lcrypt
checking for library containing getspnam... none required
checking for library containing setproctitle... no
checking for library containing bindresvport... none required
checking for library containing connect... none required
checking for library containing inet_addr... none required
checking for library containing inet_aton... none required
checking for library containing dlopen... -ldl
checking for libc name... libc.so.6
checking for library containing yp_get_default_domain... -lnsl
checking for libwrap... yes
checking security/pam_appl.h usability... yes
checking security/pam_appl.h presence... yes
checking for security/pam_appl.h... yes
checking for library containing pam_start... -lpam
checking for expected select behaviour... yes
checking for object file type... elf
checking for incorrect inet_ntoa behaviour... no
checking for socklen_t... yes
checking for sig_atomic_t in <signal.h>... yes
checking for int8_t... yes
checking for int16_t... yes
checking for int32_t... yes
checking for uint8_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for in_port_t... yes
checking for in_addr_t... yes
checking for ssize_t... yes
checking whether x86_64-pc-linux-gnu-gcc needs -traditional... no
checking for working memcmp... yes
checking for function prototypes... yes
checking whether setvbuf arguments are reversed... no
checking return type of signal handlers... void
checking for strftime... yes
checking whether utime accepts a null argument... yes
checking for vprintf... yes
checking for _doprnt... no
checking for select... yes
checking for socket... yes
checking for strcspn... yes
checking for strdup... yes
checking for strspn... yes
checking for hstrerror... yes
checking for issetugid... no
checking for strvis... no
checking for vsnprintf... yes
checking for getdtablesize... yes
checking for sysconf... yes
checking for inet_pton... yes
checking for vsyslog... yes
checking for daemon... yes
checking for bzero... yes
checking for sockatmark... yes
checking for difftime... yes
checking for memmove... yes
checking for seteuid... yes
checking for setproctitle... no
checking for inet_aton... yes
checking for gethostbyname2... yes
checking for getaddrinfo... yes
checking for getipnodebyname... no
checking for getprpwnam... no
checking for getspnam... yes
checking for getifaddrs... yes
checking for freeifaddrs... yes
checking for bindresvport... yes
checking for setegid... yes
checking for system V getpwnam... yes
checking for strerror... yes
configure: creating ./config.status
config.status: creating sockd/Makefile
config.status: creating include/Makefile
config.status: creating lib/Makefile
config.status: creating dlib/Makefile
config.status: creating Makefile
config.status: creating example/Makefile
config.status: creating doc/Makefile
config.status: creating bin/Makefile
config.status: creating capi/Makefile
config.status: creating SPECS/Makefile
config.status: creating SPECS/dante.spec
config.status: creating bin/socksify
config.status: creating libscompat/Makefile
config.status: creating contrib/Makefile
config.status: creating unlicensed/Makefile
config.status: creating doc/module/Makefile
config.status: creating VERSION
config.status: creating include/autoconf.h
config.status: linking ./unlicensed/checkmodule.c to sockd/checkmodule.c
config.status: linking ./unlicensed/redirect.c to sockd/redirect.c
config.status: linking ./unlicensed/redirect_key.c to sockd/redirect_key.c
config.status: linking ./unlicensed/bandwidth.c to sockd/bandwidth.c
config.status: linking ./unlicensed/bandwidth_key.c to sockd/bandwidth_key.c
config.status: executing depfiles commands

                     Configure status:

Acceptlock:        workaround enabled on this platform
Preloading:        OK
SO_SNDLOWAT:       not enabled for this platform
select:            OK
Routeinfo:         OK
PAM support:       OK

This software should perform optimally when all the lines above report 'OK'.
This is not possible on all platforms.

                     Modules:

redirect:          not found
bandwidth:         not found

cd . && /bin/sh /var/tmp/portage/dante-1.1.15-r1/work/dante-1.1.15/missing --run aclocal-1.9
cd . && /bin/sh /var/tmp/portage/dante-1.1.15-r1/work/dante-1.1.15/missing --run autoconf
 cd . && /bin/sh /var/tmp/portage/dante-1.1.15-r1/work/dante-1.1.15/missing --run automake-1.9 --foreign
configure.ac:25: error: possibly undefined macro: AC_PROG_LIBTOOL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
WARNING: `autoconf' is missing on your system.  You should only need it if
         you modified `configure.ac'.  You might want to install the
         `Autoconf' and `GNU m4' packages.  Grab them from any GNU
         archive site.
/bin/sh ./config.status --recheck
running /bin/sh ./configure  --prefix=/usr --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-debug --enable-libwrap --with-pam --with-socks-conf=/etc/socks/socks.conf --with-sockd-conf=/etc/socks/sockd.conf CFLAGS=-pipe -march=k8 -O2 -finline-functions -funroll-loops CXXFLAGS=-pipe -march=k8 -O2 -finline-functions -funroll-loops host_alias=x86_64-pc-linux-gnu  --no-create --no-recursion
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
Configuring Dante 1.1.15:
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 x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip
checking for style of include used by make... GNU
checking for x86_64-pc-linux-gnu-gcc... x86_64-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 x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ANSI C... dlib/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined
dlib/Makefile.am:1:
dlib/Makefile.am:1: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
dlib/Makefile.am:1: to `configure.ac' and run `aclocal' and `autoconf' again.
none needed
checking dependency style of x86_64-pc-linux-gnu-gcc... gcc3
checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
checking for egrep... grep -E
checking for AIX... no
./configure: line 3164: AC_PROG_LIBTOOL: command not found
checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
lib/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined
lib/Makefile.am:1:
lib/Makefile.am:1: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
lib/Makefile.am:1: to `configure.ac' and run `aclocal' and `autoconf' again.
checking for compiler flags... none
checking for support for -pipe compiler flag... libscompat/Makefile.am:2: Libtool library used but `LIBTOOL' is undefined
libscompat/Makefile.am:2:
libscompat/Makefile.am:2: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
libscompat/Makefile.am:2: to `configure.ac' and run `aclocal' and `autoconf' again.
yes
checking for support for -Wbounded compiler flag... no
checking for compilation with debugging... yes
checking for warning flags... none
checking for compliation with DIAGNOSTIC... no
checking whether libwrap should be disabled... no
checking for bison... bison -y
checking for gawk... (cached) gawk
checking for flex... flex
checking for yywrap in -lfl... yes
checking lex output file root... lex.yy
checking whether yytext is a pointer... WARNING: `automake-1.9' is needed, and you do not seem to have it handy on your
         system.  You might have modified some files without having the
         proper tools for further handling them.  Check the `README' file,
         it often tells you about the needed prerequirements for installing
         this package.  You may also peek at any GNU archive site, in case
         some other package would contain this missing `automake-1.9' program.
make: *** [Makefile.in] Error 1
make: *** Waiting for unfinished jobs....
yes
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 for char... yes
checking size of char... 1
checking for short... yes
checking size of short... 2
checking for int... yes
checking size of int... 4
checking for long... yes
checking size of long... 8
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking paths.h usability... yes
checking paths.h presence... yes
checking for paths.h... yes
checking for strings.h... (cached) yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking for unistd.h... (cached) yes
checking crypt.h usability... yes
checking crypt.h presence... yes
checking for crypt.h... yes
checking sys/file.h usability... yes
checking sys/file.h presence... yes
checking for sys/file.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking tcpd.h usability... yes
checking tcpd.h presence... yes
checking for tcpd.h... yes
checking shadow.h usability... yes
checking shadow.h presence... yes
checking for shadow.h... yes
checking ifaddrs.h usability... yes
checking ifaddrs.h presence... yes
checking for ifaddrs.h... yes
checking sys/sem.h usability... yes
checking sys/sem.h presence... yes
checking for sys/sem.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking sys/ipc.h usability... yes
checking sys/ipc.h presence... yes
checking for sys/ipc.h... yes
checking arpa/nameser.h usability... yes
checking arpa/nameser.h presence... yes
checking for arpa/nameser.h... yes
checking for netinet/ip_var.h... no
checking for resolv.h... yes
checking for hardcoded domainname... no
checking for socks config file location... /etc/socks/socks.conf
checking for sockd config file location... /etc/socks/sockd.conf
checking for pid file location... default
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking whether all interposition usage should be disabled... no
checking whether interposition in the client should be disabled... no
checking whether interposition in the server should be disabled... no
checking sys/sockio.h usability... no
checking sys/sockio.h presence... no
checking for sys/sockio.h... no
checking whether <sys/types.h> defines const... no
checking for an ANSI C-conforming const... yes
checking for supported routing socket communication... yes
checking whether <netdb.h> declares h_errno... yes
checking for struct ip_opts in <netinet/in.h>... no
checking whether <sys/types.h> defines inline... no
checking for inline... inline
checking for uid_t in sys/types.h... yes
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking for in6_addr... yes
checking for sockaddr_storage in sys/socket.h... yes
checking to see if openlog accepts LOG_PERROR... yes
checking to see if stdlib.h defines EXIT_FAILURE... yes
checking whether <sys/socket.h> uses AF_UNIX... no
checking for SIGINFO... no
checking to see if MSG_WAITALL exists... yes
checking whether a working SO_SNDLOWAT exists... disabled
configure: WARNING: performance in the server might be degraded without support for the SO_SNDLOWAT socket option
checking whether realloc with a NULL pointer calls malloc... yes
checking whether free can be called with NULL... yes
checking prototypes for accept... ok
checking prototypes for bind... ok
checking prototypes for connect... ok
checking prototypes for gethostbyaddr... ok
checking prototypes for getpeername... ok
checking prototypes for getsockname... ok
checking prototypes for read... ok
checking prototypes for readv... ok
checking prototypes for recv... ok
checking prototypes for recvfrom... ok
checking prototypes for recvmsg... ok
checking prototypes for send... ok
checking prototypes for sendmsg... ok
checking prototypes for sendto... ok
checking prototypes for write... ok
checking prototypes for writev... ok
checking if getsockopt needs cast... no
checking to see if dlopen param has DL_ and not RTLD_ prefix... yes
checking to see if SV_INTERRUPT should be used... no
checking if cmsghdr exists in <sys/socket.h>... yes
checking for CMSG_SPACE in sys/socket.h... yes
checking for CMSG_LEN in sys/socket.h... yes
checking for sa_len in sockaddr... no
checking to see if malloc_options exists... no
checking to see if __progname exists... yes
checking for library containing crypt... -lcrypt
checking for library containing getspnam... none required
checking for library containing setproctitle... no
checking for library containing bindresvport... none required
checking for library containing connect... none required
checking for library containing inet_addr... none required
checking for library containing inet_aton... none required
checking for library containing dlopen... -ldl
checking for libc name... libc.so.6
checking for library containing yp_get_default_domain... -lnsl
checking for libwrap... yes
checking security/pam_appl.h usability... yes
checking security/pam_appl.h presence... yes
checking for security/pam_appl.h... yes
checking for library containing pam_start... -lpam
checking for expected select behaviour... yes
checking for object file type... elf
checking for incorrect inet_ntoa behaviour... no
checking for socklen_t... yes
checking for sig_atomic_t in <signal.h>... yes
checking for int8_t... yes
checking for int16_t... yes
checking for int32_t... yes
checking for uint8_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for in_port_t... yes
checking for in_addr_t... yes
checking for ssize_t... yes
checking whether x86_64-pc-linux-gnu-gcc needs -traditional... no
checking for working memcmp... yes
checking for function prototypes... yes
checking whether setvbuf arguments are reversed... no
checking return type of signal handlers... void
checking for strftime... yes
checking whether utime accepts a null argument... yes
checking for vprintf... yes
checking for _doprnt... no
checking for select... yes
checking for socket... yes
checking for strcspn... yes
checking for strdup... yes
checking for strspn... yes
checking for hstrerror... yes
checking for issetugid... no
checking for strvis... no
checking for vsnprintf... yes
checking for getdtablesize... yes
checking for sysconf... yes
checking for inet_pton... yes
checking for vsyslog... yes
checking for daemon... yes
checking for bzero... yes
checking for sockatmark... yes
checking for difftime... yes
checking for memmove... yes
checking for seteuid... yes
checking for setproctitle... no
checking for inet_aton... yes
checking for gethostbyname2... yes
checking for getaddrinfo... yes
checking for getipnodebyname... no
checking for getprpwnam... no
checking for getspnam... yes
checking for getifaddrs... yes
checking for freeifaddrs... yes
checking for bindresvport... yes
checking for setegid... yes
checking for system V getpwnam... yes
checking for strerror... yes
configure: creating ./config.status

                     Configure status:

Acceptlock:        workaround enabled on this platform
Preloading:        OK
SO_SNDLOWAT:       not enabled for this platform
select:            OK
Routeinfo:         OK
PAM support:       OK

This software should perform optimally when all the lines above report 'OK'.
This is not possible on all platforms.

                     Modules:

redirect:          not found
bandwidth:         not found


!!! ERROR: net-proxy/dante-1.1.15-r1 failed.
!!! Function src_compile, Line 56, Exitcode 2
!!! compile problem
!!! If you need support, post the topmost build error, NOT this status message.

So it looks like it is failing because automake has not yet been built/installed.

So I now have 2 questions:

1. Is this a bug? Should automake not have been detected as a dependence and installed prior to this? Other than the mirror keywords, all I've changed in my make.conf are the CFLAGS, MAKEOPTS, and USE and I do not have an ACCEPT keyword. I did not change make.conf between bootstrap and the stage2 -> stage3.

2. Can I find out, of the packages that were supposed to be installed via the "emerge --emptytree system", which one(s) depend on this package that failed (dante)?

Thanks.
Back to top
View user's profile Send private message
msalerno
Veteran
Veteran


Joined: 17 Dec 2002
Posts: 1338
Location: Sweating in South Florida

PostPosted: Fri Jul 01, 2005 8:16 pm    Post subject: Reply with quote

At what point did you install net-proxy/dante?
I would remove it, and add it after the system has been re-emerged.
Normally, until you get the entire install completeled it's best to keep the USE flags and extra apps to a minimum.
Back to top
View user's profile Send private message
fbvortex
n00b
n00b


Joined: 01 Jul 2005
Posts: 22

PostPosted: Fri Jul 01, 2005 10:05 pm    Post subject: Reply with quote

msalerno wrote:
At what point did you install net-proxy/dante?
I would remove it, and add it after the system has been re-emerged.
Normally, until you get the entire install completeled it's best to keep the USE flags and extra apps to a minimum.

Sorry, I was being unclear in my original post. dante was one of the packages portage wanted to install when I did "emerge --emptytree system". I did not manually request dante. In the overview of "these are the packages I will be installing," I don't remember seeing it, but it very well might have been there and I just left it alone. However, that leads to another question I had: why would the --emptytree system invocation even want to pull in dante? This is why I was asking how to find which of these 113 packages depend on dante.
Back to top
View user's profile Send private message
msalerno
Veteran
Veteran


Joined: 17 Dec 2002
Posts: 1338
Location: Sweating in South Florida

PostPosted: Fri Jul 01, 2005 10:43 pm    Post subject: Reply with quote

Have you checked the output of:

emerge --emptytree system -pv
Back to top
View user's profile Send private message
get sirius
Guru
Guru


Joined: 27 Apr 2002
Posts: 316
Location: Madison, WI

PostPosted: Mon Jul 04, 2005 9:38 pm    Post subject: Reply with quote

From man emerge, the "--emptytree" option is of more use to developers than to users. Why not complete the stage 3 install as msalerno suggested, get the new system bootable, and then customize the installation? I gather from the number of your posts that gentoo (although perhaps not GNU/Linux) is relatively new to you. These gentoo forums are fairly renowned for their helpful user base and terrific install docs; with all due respect, you should take advantage of them.:D
Back to top
View user's profile Send private message
fbvortex
n00b
n00b


Joined: 01 Jul 2005
Posts: 22

PostPosted: Tue Jul 05, 2005 8:42 pm    Post subject: Reply with quote

get sirius wrote:
From man emerge, the "--emptytree" option is of more use to developers than to users. Why not complete the stage 3 install as msalerno suggested, get the new system bootable, and then customize the installation?

Actually, that command ("emerge --emptytree system") came directly from the handbook, in the section discussing installation and going from stage2 to stage3. I don't see where msalerno suggested I directly do a stage3 install and go from there.
get sirius wrote:
These gentoo forums are fairly renowned for their helpful user base and terrific install docs; with all due respect, you should take advantage of them.:D

Following the docs is how I got to this point.

msalerno wrote:
Have you checked the output of:

emerge --emptytree system -pv

Thanks for that tip; even though I did so prior to invoking emerge "for real," I don't know why I didn't think to do it at this point. The output shows that dante uses the tcpd and pam USE flags, which I had set. The handboook discusses the USE flags within the installation section, so I figured I should set the flags I'm interested in prior to the "emerge --emptytree system." That's different from your advice, so I'll mind what you said for future installations.

I'd still like to know if it's a bug or expected behavior that emerge should try to install the dante package, which requires automake, without having automake installed (dependence not satisfied).
Back to top
View user's profile Send private message
get sirius
Guru
Guru


Joined: 27 Apr 2002
Posts: 316
Location: Madison, WI

PostPosted: Tue Jul 05, 2005 11:51 pm    Post subject: Reply with quote

I was referring to msalerno's first post here, not his second. Although he did not say it directly, I inferred that he was saying that. And it has evidently been a while since I've gone over the install notes, because the "emerge --emptytree system" is new to me (and I won't use it anyway because it works totally fine without it), so I apologize for advising you wrongly!:D
Back to top
View user's profile Send private message
bl00mie
Tux's lil' helper
Tux's lil' helper


Joined: 05 Apr 2003
Posts: 82
Location: washington, dc

PostPosted: Wed Jul 06, 2005 10:39 am    Post subject: Reply with quote

It sounds to me like you went a little over-board on setting USE flags. I did the same thing the first time I installed gentoo a couple years ago. In my experience, most utilities than need things like pam will auto-set USE to include them.

Is anything important other than dante using pam? If not, remove pam until after building the system. In my experience, all of the system utilities that require pam (util-linux, openssh... shadow maybe?) automatically add pam to USE.

As an exercise, I just added pam and tcpd to my USE flags and tried a emerge -pve system and dante was not in the list. My recomendation would be to trim down your USE flags a lot. For my main machine "USE=-kde -gnome -qt gtk gtk2 alsa". That just tells emerge to add a gtk or gtk2 gui if it's optional, include alsa-sound options, and never ever emerge gnome or kde (because I hate them =).

It is certainly good practice to include all appropriate use flags... like apache2 to indicate that emerge should always use apache2 instead of 1.3... or including mysql and/or lirc when building a mythtv server.... but including more than you really need can cause all kinds of problems, and doesn't tend to help you out all that much...

just my $0.02

--chad
Back to top
View user's profile Send private message
Goatking
n00b
n00b


Joined: 11 Feb 2004
Posts: 20
Location: Rochester, NY (USA)

PostPosted: Wed Jul 06, 2005 1:43 pm    Post subject: Reply with quote

Today I ran into the exact same problem the original poster had. What fixed it for me was to emerge libtool then continue with emerge system. Hope this helps.
Back to top
View user's profile Send private message
fbvortex
n00b
n00b


Joined: 01 Jul 2005
Posts: 22

PostPosted: Wed Jul 06, 2005 6:31 pm    Post subject: Reply with quote

bl00mie wrote:
It sounds to me like you went a little over-board on setting USE flags. I did the same thing the first time I installed gentoo a couple years ago. In my experience, most utilities than need things like pam will auto-set USE to include them.

Is anything important other than dante using pam? If not, remove pam until after building the system. In my experience, all of the system utilities that require pam (util-linux, openssh... shadow maybe?) automatically add pam to USE.

The documentation could really benefit from a discussion like this. Everybody's advice seems to be to avoid changing USE flags during the installation phase, but the documentation mentions it prior to the stage2 -> stage3 step, so I thought I should do my USE configuration at that point.

What you are mentioning with respect to pam USE flags and so on, is also not really discussed in depth within the documentation. What I did, since I found no good discussion on how USE should properly be managed, was to look at the Gentoo-Portage site, investigate which packages care about which USE flags, and set them accordingly prior to running "emerge --emptytree system".

It seems like the better thing to do would have been to see which USE flags were set by default in the standard 2005.0 AMD64 profile, and then unset the ones that I didn't want by default, like -alsa since this machine has no sound.
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
Page 1 of 1

 
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