Bugzilla Bug 41908

When emerging the latest release of lame, lame-3.95.1, on Alpha I get the
following error:

make[1]: Entering directory `/var/tmp/portage/lame-3.95.1/work/lame-3.95.1'
Making all in mpglib
make[2]: Entering directory
`/var/tmp/portage/lame-3.95.1/work/lame-3.95.1/mpglib'
if /bin/sh ../libtool --mode=compile ccc -DHAVE_CONFIG_H  -I. -I. -I..
-I../include -I. -I../libmp3lame -I..    -w0 -migrate -fast -inline speed
-unroll 0 -arch host -tune host -Wall -pipe -mcpu=ev67 -O3 -pipe  -MT common.lo
-MD -MP -MF ".deps/common.Tpo" \
  -c -o common.lo `test -f 'common.c' || echo './'`common.c; \
then mv -f ".deps/common.Tpo" ".deps/common.Plo"; \
else rm -f ".deps/common.Tpo"; exit 1; \
fi
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
make[2]: *** [common.lo] Error 1
make[2]: Leaving directory
`/var/tmp/portage/lame-3.95.1/work/lame-3.95.1/mpglib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/lame-3.95.1/work/lame-3.95.1'
make: *** [all] Error 2

!!! ERROR: media-sound/lame-3.95.1 failed.
!!! Function src_compile, Line 57, Exitcode 2
!!! (no error message)


Reproducible: Always
Steps to Reproduce:
1. emerge -u lame
2.
3.

Actual Results:  
See comments above.

Expected Results:  
Worked.

Portage 2.0.50-r1 (default-alpha-1.4, gcc-3.3.2,
glibc-2.3.2-r1,2.3.3_pre20040207-r0, 2.4.21-alpha-r2)
=================================================================
System uname: 2.4.21-alpha-r2 alpha EV67
Gentoo Base System version 1.4.3.13
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.59
Automake: sys-devel/automake-1.8.2
ACCEPT_KEYWORDS="alpha ~alpha"
AUTOCLEAN="yes"
CFLAGS="-mcpu=ev67 -O3 -pipe "
CHOST="alphaev67-unknown-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc
/usr/X11R6/lib/X11/xkb:/usr/kde/3.2/share/config:/usr/share/config
/usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-mcpu=ev67 -O3 -pipe "
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache"
GENTOO_MIRRORS="http://gentoo.oregonstate.edu
http://www.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j1"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/my_gentoo"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X alpha arts artswrappersuid avi berkdb crypt cups encode esd ev6
foomaticdb gdbm gif gnome gpm gtk gtk2 imlib ipv6 jpeg kde ldap libg++ libwww
mikmod motif mozilla moznocompose moznoirc ncurses oggvorbis opengl oss pam
pdflib perl png python qt quicktime readline ruby sdl slang spell ssl tcltk
tcpd
tiff truetype xinerama xml2 xmms xv zlib"

Looks like some weird Makefile logic to search for ccc, overriding configure.

I'm fairly sure there some 64bit issues with lame as well.

assigning to self.

For what it is worth I compiled it just fine the other day using ccc.

I have the same problem, using gcc.

libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'

Ok, I fixed lame's crippled configure with a patch to respect CC.  Seems to
work for both CC=gcc (with ccc installed on the system) and for CC=ccc.  I
tested building 3.96 and 3.96.1