Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 39630

Summary: ayttm-0.4.5 - 0.4.6 fails to link
Product: Gentoo Linux Reporter: solar (RETIRED) <solar>
Component: New packagesAssignee: Mamoru KOMACHI (RETIRED) <usata>
Status: RESOLVED INVALID    
Severity: normal CC: mholzer
Priority: High    
Version: 1.4   
Hardware: All   
OS: All   
Whiteboard:
Package list:
Runtime testing required: ---

Description solar (RETIRED) gentoo-dev 2004-01-27 18:35:28 UTC
clude -I../../src -march=i686 -O3 -pipe -mcpu=pentium4 -fforce-addr  -fPIC  -L/usr/X11R6/lib -lXft -L/usr/lib -lfreetype -lfontconfig -L/usr/X11R6/lib -lXrender -o libayttmgtk.la   about_window.lo extgtktext.lo file_selection_dlg.lo gtk_eb_html.lo gtkspell.lo gtkutils.lo log_window.lo message_windows.lo prefs_window.lo  -lpspell -lltdl -laudiofile  -L/usr/local/lib -lpthread
grep: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.1/libstdc++.la: No such file or directory
sed: can't read /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.1/libstdc++.la: No such file or directory
libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.1/libstdc++.la' is not a valid libtool archive
make[4]: *** [libayttmgtk.la] Error 1
make[4]: Leaving directory `/var/tmp/portage/ayttm-0.4.6/work/ayttm-0.4.6/src/gtk'
-------------------------------------------------------

Portage 2.0.50_pre15 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20040117-r1, 2.4.24-grsec-1.9.13)
=================================================================
System uname: 2.4.24-grsec-1.9.13 i686 Intel(R) Pentium(R) 4 CPU 1400MHz
Gentoo Base System version 1.4.3.12
distcc 2.5 i686-pc-linux-gnu (protocol 1) (default port 3632) [disabled]
Autoconf: sys-devel/autoconf-2.59
Automake: sys-devel/automake-1.7.8
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=i686 -O3 -pipe -mcpu=pentium4 -fforce-addr  -fPIC"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=i686 -O3 -pipe -mcpu=pentium4 -fforce-addr  -fPIC"
DISTDIR="/usr/portage/distfiles"
FEATURES="buildpkg ccache cvs flawfinder noauto noautoaddcvs rats sfperms strict strip suidctl usersandbox"
GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j4"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/home/cvsroot/gentoo-x86/"
PORTDIR_OVERLAY=""
SYNC="rsync://192.168.1.1/gentoo-portage"
USE="3dfx X aalib acpi apic apm avi berkdb bonobo cdr clflush cmov crypt cx8 de dts encode esd etdyn evo foomaticdb fpu fxsr gd gdbm gnome gnomedb gpm gtkhtml guile ht imlib jpeg justify ldap libg++ libwww mad mca mce mikmod mmx motif mozilla moznocompose moznoirc moznomail mozxmlterm mpeg msr mtrr mysql ncurses nls oggvorbis opengl oss pae pam pat pdflib perl pge pic pie png prelude pse pse36 python quicktime readline sdl sep slang snmp spell ss sse sse2 ssl svga tcpd tetex tm truetype tsc ungif vme voodoo3 x86 xinerama xml2 xmms xv zlib"

-------------------------------------------------------

Any insights? (perhaps gcc-3.3.x?)

I really don't want to use gaim, however I've not been able to compile this from  about the time when yahoo last changed the backend service.  0.4.4 worked for me before.

Btw if 0.4.5 is stable then I would see no reason to keep 0.4.4 in the tree marked as stable as well.
Comment 1 Mamoru KOMACHI (RETIRED) gentoo-dev 2004-01-27 19:57:49 UTC
Hum, it's gcc problem rather than ayttm (gcc 3.3.2 is installed but
libstdc++.la from 3.3.1 is searched). Running
/usr/portage/sys-devel/gcc/files/fix_libtool_files.sh will solve it.
As for 0.4.4, I usually keep four ebuilds for one package to allow
users refer to older releases. They may be useful for some users,
IMO.
Comment 2 Martin Holzer (RETIRED) gentoo-dev 2004-02-11 00:21:59 UTC
closing as the bugtitle has been fixed