FWIW, I saw a similar error when building kdevelop a couple of days ago
(March 3rd, or perhaps a day or so earlier).  I had just re-supped, and
had rebuilt kdevelop without problems about a week before that.  After
hitting that problem, I rebuilt lots of stuff (libtool, autoconf/automake,
kdebase, kdelibs, ...), and kdevelop still failed to build.

Unlike Ruibiao Qiu, I am NOT running -current.

The problem in my case was that c_cpp_reference (at the time a kind of
sub-package of kdevelop) was using a .C file to test for KDE support, and
libtool said that it didn't know what to do with .C files.  After reading
libtool's info pages, I hacked an explicit instruction (to
c_cpp_reference's config script, I think) to tell libtool to treat the .C
file as a C++ file, and all was well.  (I exchanged email with Berndt
Josef Wulf who had been fixing kdevelop bugs; he hasn't answered my last
email on the subject, so I don't know if he has any more insight than I.)

I've re-supped again, and now (with c_cpp_reference a seperate package),
it all just works.

Since Ruibiao (on -current), someone else here on current-users, and
myself (running 1.5 (proper)) saw this surface apparently at about the
same time, I suspect that it's a pkgsrc problem.  (Or a problem with some
commonly-used packaged tools, such as libtool.)


(Oh, my compiler is the stock gcc that ships with 1.5.  I do not have any
cross-* packages installed.  The problem did NOT come up when kdevelop,
per se, ran its config script (which ALSO checked for KDE support); only
when the c_cpp_reference sub-package was being built.)


  "I probably don't know what I'm talking about." --rauch@eecs.ukans.edu