configure: creating ./config.status wrong input (flag != 4) at admin/conf.change.pl line 117, <> line 1224. config.status: creating Makefile config.status: WARNING: Makefile.in seems to ignore the --datarootdir setting config.status: error: cannot find input file: Makefile.rules.in !!! Please attach the following file when filing a report to bugs.gentoo.org: !!! /var/tmp/portage/ksudoku-0.3/work/ksudoku-0.3/config.log !!! ERROR: games-puzzle/ksudoku-0.3 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile ebuild.sh, line 1255: Called kde_src_compile kde.eclass, line 170: Called kde_src_compile 'all' kde.eclass, line 340: Called kde_src_compile 'myconf' 'configure' 'make' kde.eclass, line 322: Called econf '--with-x' '--enable-mitshm' '--with-xinerama' '--with-qt-dir=/usr/qt/3' '--enable-mt' '--with-qt-libraries=/usr/qt/3/lib64' '--disable-debug' '--without-debug' '--with-arts' '--enable-libsuffix=64' '--with-extra-includes=/usr/kde/3.5/include' '--with-extra-libs=/usr/kde/3.5/lib64' ebuild.sh, line 540: Called die !!! econf failed !!! If you need support, post the topmost build error, and the call stack if relevant.
surprisingly, if I go into work area and untar a fresh copy of ksudoku in it and configure with the same arguments, it works fine.
can you attach the config.log?
Created attachment 104777 [details] Configure log
Looks like some perl lib64 mixup. What do you think?
Why do you say it's perl? configure:11210: checking for shl_load configure:11266: x86_64-pc-linux-gnu-gcc -o conftest -ansi -W -Wall -Wchar-subscripts -Wshadow -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DNDEBUG -O2 -O2 -march=k8 -msse2 -msse3 -fforce-addr -pipe -fomit-frame-pointer -Wformat-security -Wmissing-format-attribute -Wl,-O1 -Wl,--enable-new-dtags conftest.c >&5 /var/tmp/portage/ksudoku-0.3/temp/cctcGcKf.o: In function `main': conftest.c:(.text+0x7): undefined reference to `shl_load' collect2: ld returned 1 exit status
as this version has been dropped in favour of 0.4, this bug doesn't apply any more