Subject: x11/tk8.4.15 problems building with pkgsrc-current out of the box
To: None <pkgsrc-users@netbsd.org>
From: Bernd Limbach <bernd@belimbach.de>
List: pkgsrc-users
Date: 10/12/2007 15:51:11
Hi all,
I have a question, which I do not understand...
Situation:
When compiling tk8.4.15 with pkgsrc-current from 20071011 approx. 16:00h
GMT (and earlier) the build stopped with
--------8<--------
[..]
.libs/tk3d.o
In file included from
/usr/pkgsrc/x11/tk/work/tk8.4.15/unix/../generic/tkPort.h:34,
from
/usr/pkgsrc/x11/tk/work/tk8.4.15/unix/../generic/tkInt.h:27,
from
/usr/pkgsrc/x11/tk/work/tk8.4.15/unix/../generic/tk3d.h:18,
from
/usr/pkgsrc/x11/tk/work/tk8.4.15/unix/../generic/tk3d.c:16:
/usr/pkgsrc/x11/tk/work/tk8.4.15/unix/../generic/../unix/tkUnixPort.h:210:20:
error: tclInt.h: No such file or directory
*** Error code 1
Stop.
make: stopped in /usr/pkgsrc/x11/tk/work/tk8.4.15/unix
*** Error code 1
Stop.
make: stopped in /usr/pkgsrc/x11/tk
/bin/rm -f /usr/pkgsrc/x11/tk/work/.warning/*.tmp;
test -d /usr/pkgsrc/x11/tk/work/.warning || exit 0;
cd /usr/pkgsrc/x11/tk/work/.warning;
for file in ./*; do
test "$file" != "./*" || exit 0;
break; done;
/bin/cat ./* | /usr/bin/sed -e
"s|^|WARNING: |" 1>&2; /bin/mv -f ./*
/usr/pkgsrc/x11/tk/work/.warning-done
/bin/rm -f /usr/pkgsrc/x11/tk/work/.error/*.tmp;
test -d /usr/pkgsrc/x11/tk/work/.error || exit 0;
cd /usr/pkgsrc/x11/tk/work/.error;
for file in ./*; do
test "$file" != "./*" || exit 0;
break; done;
/bin/cat * | /usr/bin/sed -e
"s|^|ERROR: |" 1>&2; if
/usr/bin/awk 'END { exit (NR > 0) ? 0 : 1; }' ./*; then
/bin/mv -f ./* /usr/pkgsrc/x11/tk/work/.error-done;
exit 1; fi
*** Error code 1
Stop.
make: stopped in /usr/pkgsrc/x11/tk
loewenburg: {106}
--------8<--------
That told me that the include file "tclInt.h" was not found. This file
is included in "lang/tcl/work/tcl8.4.15/generic/". Copying this file
into "x11/tk/work/tk8.4.15/generic/" brought me one step further.
To make it compile completely I also had to copy "tclIntDecls.h" and
"tclMath.h" into "x11/tk/work/tk8.4.15/generic/".
I am pretty sure, that this is not the intended way to do and I am
wondering where the root cause of this behavior can be found.
Does anybody has a clue what can cause that?
Any additional information needed to trace this down?
Thanks, Bernd