When I try to compile the new twolame-0.3.9 package, I get a compile error. See attached build.log file. Reproducible: Always Steps to Reproduce: 1. emerge twolame Actual Results: I receive a build error Expected Results: package is supposed to compile properly emerge --info: Portage 2.1.2.12 (default-linux/x86/2007.0, gcc-4.1.2, glibc-2.5-r4, 2.6.23-rc3 i686) ================================================================= System uname: 2.6.23-rc3 i686 Intel(R) Pentium(R) M processor 2.00GHz Gentoo Base System release 1.12.9 Timestamp of tree: Mon, 10 Sep 2007 19:50:01 +0000 app-shells/bash: 3.2_p17 dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.9-r2 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium-m -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /u sr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/revdep-rebuild /etc/ter minfo" CXXFLAGS="-march=pentium-m -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distribu tions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclud e=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="X a52 aac aalib acl alsa amrnb amrnd berkdb bitmap-fonts bzip2 cddb cli cpudetectio n cracklib crypt cups divx doc dri dts dvd dvdnav dvdr dvdread encode ffmpeg firefox fla c fortran gdbm gpm iconv isdnlog java jpeg kde libcaca mad midi mmx mmxext mp2 mp3 mplay er mudflap ncurses nls nptl nptlonly nsplugin offensive ogg openal opengl openmp pam pcr e perl png pppd python quicktime rar readline real realmedia reflection samba sdl sessio n sid spell spl sse sse2 ssl svg tcpd tiff timidity truetype truetype-fonts tta type1 ty pe1-fonts unicode vcd vorbis wifi win32codecs wma wmf wmp x264 x86 xcomposite xorg xscre ensaver xv xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipc i emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maes tro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym c opy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboa rd mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lc dm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="apm ark chips cirrus cyrix dummy fbdev glint i128 i740 i810 imstt mach64 mga neomagic nsc nv r128 radeon rendition s3 s3v irge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware vood oo" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORT AGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
You have just upgraded media-libs/flac and now you need to rebuild packages that depend on flac, like media-libs/libsndfile. Please run revdep-rebuild.
Created attachment 130626 [details] build.log Attached build.log file
(In reply to comment #1) > You have just upgraded media-libs/flac and now you need to rebuild packages > that depend on flac, like media-libs/libsndfile. > > Please run revdep-rebuild. > I actually received this error doing a emerge --update --deep world. Shouldn't it have done that automatically?
(In reply to comment #3) > I actually received this error doing a emerge --update --deep world. Shouldn't > it have done that automatically? Nope.