| View previous topic :: View next topic |
| Author |
Message |
Kalmairn
n00b
Joined: 27 Jan 2003
Posts: 61
|
 Posted: Thu Mar 16, 2006 12:38 pm Post subject: KDM 3.5.1 Fails to Compile |
 |
|
I am emerge-ing kde-meta with a full KDE package list in /etc/portage/package.keywords (~x86) and have hit a problem with KDM:
I copied more than required, the error itself seems to indicate a problem with a process in the ebuild. I'm workstationless right now, otherwise I'd try to figure out where the problem might be occuring to greater detail.
| Code: | creating kdm_greet.all_cpp.cpp ...
g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I./../backend -I.. -I../../kcontrol/background -I../../kdmlib -I/usr/kde/3.5/include -I/usr/qt/3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -march=nocona -pipe s -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o krootimage.o `test -f 'krootimage.cpp' || echo './'`krootimage.cpp
g++: s: No such file or directory
./../backend/printf.c: In function `fmtstr':
./../backend/printf.c:210: warning: 'lastcol' might be used uninitialized in this function
./../backend/printf.c: In function `fmtstr':
./../backend/printf.c:210: warning: 'lastcol' might be used uninitialized in this function
./../backend/printf.c: In function `Logger':
./../backend/printf.c:298: warning: 'radix' might be used uninitialized in this function
./../backend/printf.c:300: warning: 'arlen' might be used uninitialized in this function
make[4]: *** [kdmctl.o] Error 1
make[4]: *** Waiting for unfinished jobs....
kdm_config.c: In function `GetValue':
kdm_config.c:632: warning: 'bestsec' might be used uninitialized in this function
make[4]: *** [kdm_greet.o] Error 1
make[4]: *** [kdm_config.o] Error 1
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/kdm-3.5.1/work/kdm-3.5.1/kdm/kfrontend'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/kdm-3.5.1/work/kdm-3.5.1/kdm'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/kdm-3.5.1/work/kdm-3.5.1'
make: *** [all] Error 2
|
I don't use KDM, so I am going to continue the build with --resume --skipfirst, but it would be good to get this sorted in the (unlikely) event some part of KDM is required later down the road.
Thanks,
Kal. |
|
| Back to top |
|
 |
pv
Tux's lil' helper
Joined: 25 Mar 2005
Posts: 103
Location: Russia, Yaroslavl
|
| Posted: Thu Mar 16, 2006 8:13 pm Post subject: |
|
|
The first coming to my head is what are your CFLAGS?
Particularly, I prefer to use '-s' CFLAG among others and if I forget the dash ('-' character) before the 's' letter I would get the same error.
Also, it's recommended that you give the output of 'emerge --info' when requesting for support.
_________________
Nothing but perfection. |
|
| Back to top |
|
|
Kalmairn
n00b
Joined: 27 Jan 2003
Posts: 61
|
| Posted: Fri Mar 17, 2006 12:23 pm Post subject: |
|
|
Sorry, didn't know the "emerge --info" preference, here it is:
| Code: | # emerge --info
Portage 2.0.54 (default-linux/x86/2006.0, gcc-3.4.4, glibc-2.3.5-r2, 2.6.15-ck7
i686)
=================================================================
System uname: 2.6.15-ck7 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz
Gentoo Base System version 1.6.14
dev-lang/python: 2.4.2
sys-apps/sandbox: 1.2.12
sys-devel/autoconf: 2.13, 2.59-r6
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils: 2.16.1
sys-devel/libtool: 1.5.22
virtual/os-headers: 2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=nocona -pipe -fomit-frame-pointers"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share
/config /usr/kde/3.4/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kd
e/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/q
mail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=nocona -pipe -fomit-frame-pointers"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/
distributions/gentoo"
MAKEOPTS="-j5"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X aac aim alsa apache2 apm arts audiofile avi bash-completion berkdb bi
tmap-fonts bzip2 cdparanoia cdr cli crypt ctype cups curl dba dri dvd dvdr dvdre
adeds eds emboss encode esd expat fam fastbuild foomaticdb force-cgi-redirect fo
rtran ftp gd gdbm gif gmp gpm gstreamer idn imlib ipv6 jabber javascript jpeg kd
e kdeenablefinal lcms libg++ libwww lm_sensors mad maildir memlimit mikmod mmx m
ng motif mp3 mpeg msn ncurses nls nptl offensive ogg opengl oss pam pcre pdflib
perl php png posix python qt quicktime readline samba sdl session simplexml snmp
soap sockets spell spl sse sse2 ssl static tcpd tiff tokenizer truetype truetyp
e-fonts type1-fonts udev usb vorbis xine xml2 xmms xsl xv yahoo zlib userland_GN
U kernel_linux elibc_glibc"
Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY |
I'm not sure I follow on the "-s" CFLAG question, shouldn't that error occur on all packages rather than just one?
By the way, I am getting the exact same error in xine-lib.
Thanks,
Kal. |
|
| Back to top |
|
|
Kalmairn
n00b
Joined: 27 Jan 2003
Posts: 61
|
| Posted: Fri Mar 17, 2006 12:36 pm Post subject: |
|
|
Ok, so there it is:
| Code: | | CFLAGS="-O2 -march=nocona -pipe -fomit-frame-pointers" |
Note the "s" at the end of omit-frame-pointers
Oops.  I wonder why nothing else died as a result.
Well, that's that. Thanks to all who read this.
Kal- |
|
| Back to top |
|
|
pv
Tux's lil' helper
Joined: 25 Mar 2005
Posts: 103
Location: Russia, Yaroslavl
|
| Posted: Fri Mar 17, 2006 8:18 pm Post subject: |
|
|
| Kalmairn wrote: | | I wonder why nothing else died as a result. |
Because some packages strip CFLAGS to make sure the package will be compiled successfully and some don't. For example, if you have '-O3' then while compiling GCC the given flag will be stripped (really not, in the case of GCC it will just be replaced with -O2, but many other will, for example -ffast-math, etc...).
So, you had problems only with packages that do strip '-fomit-frame-pointer' CFLAG.
_________________
Nothing but perfection. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
