Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 74515 - callgrind 0.9.9 fails to compile
Summary: callgrind 0.9.9 fails to compile
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: SpanKY
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-15 09:09 UTC by Alexander Gretencord
Modified: 2004-12-17 17:32 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Gretencord 2004-12-15 09:09:22 UTC
Callgrind is a dep of kdesdk and fails right at the beginning with this error:

gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_
STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"callgrind\" -DVERSION=\"0.9.9\"
  -I. -I. -I../ -I/usr/include/valgrind    -DVG_LIBDIR="\"/usr/lib"\" -Winline -
Wall -Wshadow -O2 -fomit-frame-pointer -mpreferred-stack-boundary=2 -g -mpreferr
ed-stack-boundary=2 -c clo.c
In file included from bb.c:29:
global.h:547: parse error before `__attribute__'
global.h:547: warning: no semicolon at end of struct or union
global.h:551: parse error before `}'
make[2]: *** [bb.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from clo.c:28:
global.h:547: parse error before `__attribute__'
global.h:547: warning: no semicolon at end of struct or union
global.h:551: parse error before `}'
clo.c: In function `vgSkin_process_cmd_line_option':
clo.c:591: invalid use of undefined type `struct cachesim_if'
clo.c: In function `vgSkin_print_usage':
clo.c:649: invalid use of undefined type `struct cachesim_if'

Reproducible: Always
Steps to Reproduce:




Portage 2.0.51-r3 (default-linux/x86/gcc2, gcc-2.95.3, glibc-2.2.5-r9, 2.6.8.1 
i686) 
================================================================= 
System uname: 2.6.8.1 i686 AMD Athlon(tm) XP 1700+ 
Gentoo Base System version 1.4.16 
Autoconf: sys-devel/autoconf-2.59-r5 
Automake: sys-devel/automake-1.8.5-r1 
Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 
Headers:  sys-kernel/linux-headers-2.4.18 
Libtools: sys-devel/libtool-1.5.2-r7 
ACCEPT_KEYWORDS="x86" 
AUTOCLEAN="yes" 
CFLAGS="-march=i686 -O2 -pipe" 
CHOST="i686-pc-linux-gnu" 
COMPILER="" 
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.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/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/terminfo /etc/env.d" 
CXXFLAGS="-march=i686 -O2 -pipe" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" 
GENTOO_MIRRORS="ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo 
ftp://ftp.tu-clausthal.de/pub/linux/gentoo/ http://gentoo.oregonstate.edu 
http://www.ibiblio.org/pub/Linux/distributions/gentoo" 
MAKEOPTS="-j2" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="/usr/local/portage" 
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" 
USE="3dnow X acpi alsa arts berkdb bitmap-fonts cdr crypt cscope cups dvd dvdr 
f77 fam fortran gdbm gif gpm gtk2 imagemagick java jpeg jpeg2k kde ldap 
lesstif libwww mad maildir memlimit mmx motif ncurses nls oggvorbis opengl pam 
pdflib perl png qt readline samba sasl sdl slang smime speex spell sse ssl 
tetex tiff truetype unicode vim-with-x x86 xine xml xml2 xprint xv zlib"
Comment 1 Daniel Black (RETIRED) gentoo-dev 2004-12-16 02:38:46 UTC
please don't use gcc-2.95.3 and expect it to work. Use a gcc 3.3 or 3.4 (if 3.4 causes problems we'll fix it)

Suggest changing your profile (the /etc/make.profile symlink to /usr/portage/profiles/default-linux/x86/2004.3
Comment 2 Alexander Gretencord 2004-12-16 04:18:38 UTC
My profile is the 2.95 one, if you have this profile in portage, then support it! If you don't want to support it, have an upgrade path and _tell_ people to upgrade their systems a long time before declaring this profile inactive. I will try to upgrade the machine in a chroot and switch to that but until then I can only say this: You have the gcc 2.95 glibc 2.2 profile in portage, so fix bugs for it until you can safely phase it out.

I really don't understand this whole issue. The people supporting xorg-x11 did not complain about gcc 2.95 and glibc 2.2 but try to fix the bugs.
Comment 3 SpanKY gentoo-dev 2004-12-17 17:32:56 UTC
no