Bug 87610 – openssl-0.9.7 fails to emerge on amd64 with USE="perl" during emerge -e system on new install

• Status: RESOLVED DUPLICATE of bug 39318
• Product: Gentoo Linux

[Description Mark R 2005-04-01 16:38:10 UTC]

When I did a emerge -e world on my Athlon64 after successfully bootstrapping the system. The emerge progressed fine until it reached the installing openssl-0.9.7 (version e IIRC). Then it failed with the message of perl not found. If I stepped back, ran emerge perl, then ran emerge -e system - it then completed. I'm guessing this is due to my use flags messing something up.

My make.conf is set as follows:
CFLAGS="-O2 -march=athlon64 -funroll-loops -pipe -fomit-frame-pointer"
CHOST="x86_64-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
USE="X 3dnow aac acl acpi aim alsa avi bash-completion bzlib cdr crypt cscope ctype cups \
     dvx4linux dvd dvdr encode ethereal exif ftp gif gnome icq imap java jpeg \
     kde kerberos ldap memlimit mng mpeg mmx mpeg offensive oggvorbis opengl \
     pdflib perl php png python spell sse ssl szip tiff truetype unicode usb \
     wmf xine xmms zlib"


Reproducible: Didn't try
Steps to Reproduce:
1.bootstrap a amd64 system
2.set the make flags as shown
3.emerge -e system

Actual Results:  
The emerge of openssl failed with a dependancy on perl.

Expected Results:  
The emerge should have worked fine.

emerge info
Portage 2.0.51.19 (default-linux/amd64/2005.0, gcc-3.4.3,
glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r3 x86_64)
=================================================================
System uname: 2.6.11-gentoo-r3 x86_64 AMD Athlon(tm) 64 Processor 3200+
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.4-r1 [2.3.4 (#1, Apr  1 2005, 11:21:33)]
dev-lang/python:     2.3.4-r1
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.6.3, 1.8.5-r3, 1.5, 1.4_p6, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r1
sys-devel/libtool:   1.5.10-r4
virtual/os-headers:  2.6.8.1-r4
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=athlon64 -funroll-loops -pipe -fomit-frame-pointer"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env
/usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=athlon64 -funroll-loops -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox"
GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo/
ftp://gentoo.mirrors.pair.com/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X aac acl acpi aim alsa avi bash-completion berkdb bitmap-fonts bzlib
cdr crypt cscope ctype cups dvd dvdr dvx4linux encode ethereal exif fam
font-server fortran ftp gif gnome gpm icq imap ipv6 java jp2 jpeg kde kerberos
ldap lzw lzw-tiff memlimit mng motif mp3 mpeg ncurses nls offensive oggvorbis
opengl oss pam pdflib perl php png python qt readline spell ssl szip tcpd tiff
truetype truetype-fonts type1-fonts unicode usb userlocales wmf xine xml2 xmms
xpm xrandr xv zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY

[Comment 1 Jonathan Smith (RETIRED) 2005-04-01 17:06:49 UTC]

please provide an exact error message. it is also a good idea to name your bugreports with the package that fails, not "emerge -e world". for instance, instead of calling this "emerge --emptytree world (-e) after bootstrap fails with perl USE flag set", you might consider changing it to "openssl-0.9.7 fails to emerge on amd64 with USE="perl"", enabling people to more readily see what your bug is actually about

"If I stepped back, ran emerge perl, then ran emerge -e system - it then completed." <-- does this mean that your system is running happily now?

[Comment 2 Mark R 2005-04-02 08:54:51 UTC]

I'm sorry that I didn't have the foresight to write down the exact error message (dumb, I know). But what I'm trying to say is that perl needed to be emerged before openssl for my emerge system to complete successfully.

"does this mean that your system is running happily now?" Yes. emerge -e system failed on my new install during the emerge openssl step. I then ran emerge perl to install perl. After perl was installed, emerge -e system completed successfully.

[Comment 3 Diego Elio Pettenò (RETIRED) 2005-04-02 09:44:31 UTC]

That's not amd64 specific.

*** This bug has been marked as a duplicate of 39318 ***