Where the error occurred: checking for MAXPATHLEN... ./configure: line 61235: syntax error near unexpected token `do' ./configure: line 61235: ` dirs=`for i in $files; do if test -d $i; then echo $i; fi; done`' output of 'emerge --info': Portage 2.1.2_pre2-r9 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.5-r0, 2.6.18-gentoo i686) ================================================================= System uname: 2.6.18-gentoo i686 Intel(R) Celeron(R) CPU 1.70GHz Gentoo Base System version 1.12.5 Last Sync: Fri, 13 Oct 2006 03:20:01 +0000 app-admin/eselect-compiler: [Not Present] dev-java/java-config: 1.3.7, 2.0.30 dev-lang/python: 2.2.3-r6, 2.3.5-r3, 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.60 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.13-r4 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=i686 -O3 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-march=i686 -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distcc distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://www.ibiblio.org/pub/Linux/distributions/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 --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="X X509 aalib acl aim alsa apache2 arts asf audiofile bash-completion berkdb bitmap-fonts bzip2 canvas cddb cdr cli cpudetection crypt cups curl dlloader dpms dri dv eds elibc_glibc emacs emboss encode esd exif expat fam fame fat ffmpeg flac flash foomaticdb fortran gdbm gif gimp gimpprint glut glx gmp gnome gphoto2 gpm gstreamer gtalk gtk gtk2 hfs hpn idl idn imagemagick imlib input_devices_evdev input_devices_keyboard input_devices_mouse ipv6 isdnlog jabber jack java jfs jpeg kde kdeenablefinal kdexdeltas kernel_linux kig-scripting lcms libg++ libwww mad mailbox mikmod mng motif mozdevelop mozilla mozsvg mp3 mp4live mpeg mpeg2 mplayer msn msnextras nas ncurses network nls nptl nptlonly nsplugin offensive ogg on-the-fly-crypt ontlm openal opengl openssl oscar oss pam pcre pearl perl php player png pppd pythin python pyzor qt qt3 qt4 quicktime razor rdesktop readline real recode reflection reiser4 reiserfs rss rtc ruby sametime sdl session slang sockets spell spl sql sqlite srv ssl stream svg svga svgz tcltk tcpd tga theora threads tiff timidity tools truetype truetype-fonts type1-fonts udev usb userland_GNU uudeview v4l v4l2 video_cards_apm video_cards_ark video_cards_ati video_cards_chips video_cards_cirrus video_cards_cyrix video_cards_dummy video_cards_fbdev video_cards_glint video_cards_i128 video_cards_i740 video_cards_i810 video_cards_imstt video_cards_mga video_cards_neomagic video_cards_nsc video_cards_nv video_cards_rendition video_cards_s3 video_cards_s3virge video_cards_savage video_cards_siliconmotion video_cards_sis video_cards_sisusb video_cards_tdfx video_cards_tga video_cards_trident video_cards_tseng video_cards_v4l video_cards_vesa video_cards_vga video_cards_via video_cards_vmware video_cards_voodoo vnc vorbis web win32codecs wma wmf x86 xanim xcomposite xine xml xml2 xmms xorg xv xvid xvmc yahoo zip zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
Did you upgrade to bash-3.2 ?
I also have the same problem with using kdebase-meta. To be more precise kde-base/kdepasswd fails. I'm using ~amd64, and I have upgraded to bash 3.2
*** Bug 151109 has been marked as a duplicate of this bug. ***
*** Bug 151152 has been marked as a duplicate of this bug. ***
*** Bug 151099 has been marked as a duplicate of this bug. ***
I'd masked =app-shells/bash-3.2 localy in /etc/portage/package.mask Now all problematic ebuilds are compiling as they should.
(In reply to comment #1) > Did you upgrade to bash-3.2 ? > In the process of running an 'emerge --sync' then 'emerge -uDv world', bash-3.2 ran first. After reporting the bug, I ran 'etc-update', which updated some kde files and then again ran 'emerge -uDv world'. Kdebase-3.5.5 failed in the same place.
Just FYI, bash-3.2 is now package.masked
Created attachment 99527 [details] kdebase-3.5.5 config.log
Seems like I found the problem, and this is bash-style breakage of rules.. ac_cv_maxpathlen=`sed 's#KDE_HELLO ##' conftest.out` bash handles one of the # as a comment separator (probably the one with a space before it), even if it's in a non-expansion string (''): :3: checking for MAXPATHLEN checking for MAXPATHLEN... test.bash: line 30: unexpected EOF while looking for matching ``' test.bash: line 39: syntax error: unexpected end of file zsh, BSD's ash, bb and bash < 3.2 handle the thing correctly, but bash 3.2 seems not to. I can work it around, but seems like a bug to me. Bad bash!
(In reply to comment #10) > :3: checking for MAXPATHLEN > checking for MAXPATHLEN... > test.bash: line 30: unexpected EOF while looking for matching ``' > test.bash: line 39: syntax error: unexpected end of file > > zsh, BSD's ash, bb and bash < 3.2 handle the thing correctly, but bash 3.2 > seems not to. > > I can work it around, but seems like a bug to me. Bad bash! Doesn't your test say that it's a "`" that it can't find the match for rather than "#"? Looks like I backup to bash-3.1_p17 to get a look at kde-3.5.5.
It can't find ` because the closing ` is considered out of the comment. The error appears about 1000 lines below the point where MAXPATHLEN test is started (which fooled me up for a bit) because it needs to close first a ' and then a `.
(In reply to comment #12) Right. Bad bash. Looks like we'll get a better bash out of it. Good lookin' out.
*** Bug 151178 has been marked as a duplicate of this bug. ***
*** Bug 151195 has been marked as a duplicate of this bug. ***
*** Bug 151193 has been marked as a duplicate of this bug. ***
*** Bug 151204 has been marked as a duplicate of this bug. ***
*** Bug 151258 has been marked as a duplicate of this bug. ***
fixed with bash-3.2_p1
*** Bug 152146 has been marked as a duplicate of this bug. ***