All,
Beginning a complete rebuild last night was evidently a bad idea. 13 packages
that had previously built without any error now fail to build. The list of
failing packages include:
Beginning build of: libkarma - Apr 4 20:19:06
makepkg --> FAILED
Beginning build of: dependencies/python-tqt - Apr 4 20:12:56
makepkg --> FAILED
Beginning build of: libraries/kipi-plugins - Apr 4 22:43:59
makepkg --> FAILED
Beginning build of: tdegames - Apr 4 23:49:31
makepkg --> FAILED
Beginning build of: tdegraphics - Apr 5 00:21:04
makepkg --> FAILED
Beginning build of: tdepim - Apr 5 00:30:10
makepkg --> FAILED
Beginning build of: applications/rosegarden - Apr 5 00:34:51
makepkg --> FAILED
Beginning build of: applications/basket - Apr 5 00:38:14
makepkg --> FAILED
Beginning build of: applications/k3b - Apr 5 00:39:00
makepkg --> FAILED
Beginning build of: applications/gwenview - Apr 5 00:44:53
makepkg --> FAILED
Beginning build of: applications/kima - Apr 5 00:49:19
makepkg --> FAILED
Beginning build of: applications/krusader - Apr 5 00:54:10
makepkg --> FAILED
Beginning build of: tdesdk - Apr 5 00:57:28
makepkg --> FAILED
The only new packages installed that are related to the failures are:
binutils-2.22-5 boost-1.49.0-1.1 boost-libs-1.49.0-1.1 coreutils-8.16-2
expat-2.1.0-1 fftw-3.3.1-1 freetype2-2.4.9-2 gcc-4.7.0-3 gcc-libs-4.7.0-3
glibc-2.15-10 krb5-1.10.1-2 libarchive-3.0.4-1 libltdl-2.4.2-5
libtool-2.4.2-5 linux-api-headers-3.3-1 p11-kit-0.12-1 tzdata-2012b-3
xfig-3.2.5b-8 xorg-server-1.12.0.901-1 xorg-server-common-1.12.0.901-1
Of those - the obvious winners look like gcc-4.7, glibc-2.15 and xorg.
Frustrating, yes, but understanding the failures will probably disclose
weaknesses in the codebase. I'll put time into trying to narrow down what broke.
You guys that are build wizards, please let me know if you see, or know of, a
common thread that may have been pulled in with gcc 4.7 that may be the base of
the build problem.
--
David C. Rankin, J.D.,P.E.