Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 74234 - Compiling kdebase-3.3.2 fails with parse error - maybe related to autoconf/automake
Summary: Compiling kdebase-3.3.2 fails with parse error - maybe related to autoconf/au...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo KDE team
Depends on:
Reported: 2004-12-12 13:46 UTC by enkil
Modified: 2004-12-13 09:59 UTC (History)
0 users

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


Note You need to log in before you can comment on or make changes to this bug.
Description enkil 2004-12-12 13:46:56 UTC
Compiling kdebase-3.3.2 fails with a parse error when compiling kdm. Here's the first parse error that occurs:

-DQT_NO_TRANSLATION -D_GNU_SOURCE  -c -o kgreet_classic.lo kgreet_classic.cpp
i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../..  -I./../backend -I../../kcontrol/background -I/usr/kde/3.3/include -I/usr/qt/3/include -I.  -DXDMCP -DHAVE_GETUSERSHELL -DUSE_SYSLOG -DUSE_PAM -DQT_THREAD_SUPPORT  -D_REENTRANT -D_FILE_OFFSET_BITS=64  -ansi -W -Wall -Wchar-subscripts -Wshadow -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DNDEBUG -O2  -O2 -march=athlon-xp -pipe  -Wformat-security -Wmissing-format-attribute -D_GNU_SOURCE -c kdm_config.c
kdm_config.c:389: error: parse error before "XBINDIR"
kdm_config.c:389: error: `XBINDIR' undeclared here (not in a function)
kdm_config.c:389: error: initializer element is not constant
kdm_config.c:389: error: (near initialization for `ents_Core[16].def') 

After that, ~100-200 parse errors appear. I think the problem might be related to autoconf/automake. I got errors in my configure-output:

checking whether make sets $(MAKE)... ./configure: line 1927: ac_maketemp=make: command not found

checking for X... ./configure: line 27605: ac_im_incroot=/usr/X11R6/include: No such file or directory
libraries /usr/X11R6/lib, headers .

checking various X settings... done
./configure: line 44683: XDM_CFLAGS=-Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -DUNIXCONN -DTCPCONN : command not found

I did emerge -auDv gcc glibc before compiling kdebase, as I switched to nptl, which installed various versions of autoconf/automake:

     Sat Dec 11 20:18:56 2004 >>> sys-devel/gcc-3.4.3-r1
     Sat Dec 11 20:20:31 2004 >>> sys-devel/autoconf-2.13
     Sat Dec 11 20:20:41 2004 >>> sys-devel/autoconf-wrapper-2
     Sat Dec 11 20:21:21 2004 >>> sys-devel/autoconf-2.59-r6
     Sat Dec 11 20:21:50 2004 >>> sys-devel/automake-1.5
     Sat Dec 11 20:22:15 2004 >>> sys-devel/automake-1.8.5-r2
     Sat Dec 11 20:22:38 2004 >>> sys-devel/automake-1.6.3
     Sat Dec 11 20:23:03 2004 >>> sys-devel/automake-1.7.9
     Sat Dec 11 20:23:22 2004 >>> sys-devel/automake-1.4_p6
     Sat Dec 11 20:23:34 2004 >>> sys-devel/automake-wrapper-1
     Sat Dec 11 20:24:29 2004 >>> sys-devel/automake-1.9.3

I downgraded to automake-2.59-r5, without success. The errors in configure still remain. I haven't tested to compile kdebase since then, as it takes at least an hour until it stops with the parse error. But I can do this if it helps. If I manually ./configure something, everything seems fine:

checking whether make sets $(MAKE)... yes

Reproducible: Always
Steps to Reproduce:
1. update autoconf/automake
2. emerge -auv kdebase

Expected Results:  
no errors in configure, kdebase compiling without errors

[ root@sphere /var/tmp/portage/kdebase-3.3.2/work/kdebase-3.3.2 ] emerge info
Portage 2.0.51-r8 (default-linux/x86/2004.0, gcc-3.4.3, glibc-,
2.6.9-ck3 i686)
System uname: 2.6.9-ck3 i686 AMD Athlon(tm) XP 2000+
Gentoo Base System version 1.6.7
Python:              dev-lang/python-2.3.4 [2.3.4 (#1, Nov 13 2004, 11:05:31)]
dev-lang/python:     2.3.4
sys-devel/autoconf:  2.59-r5, 2.13
sys-devel/automake:  1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.3
sys-devel/libtool:   1.5.2-r7
CFLAGS="-O2 -march=athlon-xp -pipe -fomit-frame-pointer"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/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="-O2 -march=athlon-xp -pipe -fomit-frame-pointer"
FEATURES="autoaddcvs autoconfig ccache distlocks grc sandbox sfperms"
GENTOO_MIRRORS="         "
USE="3dnow X aalib alsa apm arts audiofile avi berkdb bitmap-fonts bzlib cdr cjk
crypt cups dga directfb dvd dvdr encode esd f77 fam flac foomaticdb fortran ftp
gd gdbm gif gpm gtk gtk2 icq imagemagick imlib java jpeg junit kde libg++ libwww
lirc mad mikmod mmx motif mpeg ncurses nls no-old-linux nptl nptlonly oggvorbis
opengl oss pam pdflib perl png postgres ppds python qt quicktime readline sdl
slang spell sse ssl svg svga tcpd tetex tiff truetype unicode usb wmf x86 xml
xml2 xmms xv zlib"
Comment 1 Gregorio Guidi (RETIRED) gentoo-dev 2004-12-12 14:50:47 UTC
It seems that when bash executes the configure script it fails on basic
things like:
 eval `echo variable=value`

and then the compile errors are just a consequence of this.
I can't really imagine the reason for such a strange behaviour.

Please try again emerging kdebase (you just have to look at the configure
output to know if it will fail or not). If it fails, maybe you can try to 
recompile bash?
Comment 2 enkil 2004-12-12 23:53:50 UTC
I recompiled portage, bash, python, baselayout and sed without having effect on portage's configure. I only get configure-errors when using emerge, so I kind of thought portage might somehow cause this.
I'll switch to a system-backup without nptl/ntplonly and report if it works with that.
Comment 3 enkil 2004-12-13 00:22:13 UTC
I've traced the problem.
It was grc. I used grc with portage, that's why a manual ./configure worked. I removed grc-stuff in /etc/portage/bashrc and now configure does work normal. I'm sorry, I should have thought of that one first.
I'm somehow new to bugzilla. Should I change the summary to "grc breaks configure in kdebase" and move it to another section, or close it?
Comment 4 Gregorio Guidi (RETIRED) gentoo-dev 2004-12-13 07:36:26 UTC
I guess it should be closed, as there's nothing that could be done about that.
Maybe grc should be used as a wrapper to emerge instead of putting it in bashrc?
Comment 5 enkil 2004-12-13 09:59:42 UTC
I changed the bug's status to CANTFIX, I hope this is okay.