On Wed, 9 Feb 2000, John Polstra wrote:
> In article <[EMAIL PROTECTED]>,
> Maxim Sobolev <[EMAIL PROTECTED]> wrote:
> > No, because since 20000124 I've recompiled both world (several times
> > actually) and all C++ libs used by the kde. If you will read my
> > previous message thoughtfully, you will notice that after Jan 24 I
> > had successfully compiled kdesupport on system builded/installed on
> > Feb 3.
That's my experience also. I just rebuilt the world on Feb 8, and I
rebuilt Qt, which KDE uses, last night. No dice. I still get errors like
/usr/lib/libstdc++.so.3: undefined reference to `exception type_info node'
/usr/lib/libstdc++.so.3: undefined reference to `exception virtual table'
/usr/lib/libstdc++.so.3: undefined reference to `__builtin_vec_new'
> Sheesh, chill out. I'm just trying to help you. I did read your
> message "thoughtfully." That's why I wrote, "Are you sure ...?"
> rather than, "Hey dumbo, read UPDATING!" I thought (and still think)
> you might possibly have missed rebuilding one of the libraries.
I rebuilt what I thought were the libs I needed, which would be Qt. I
don't know if kdesupport is linking with Qt at all, but just in case, I
rebuilt Qt with the new world. Still, the errors persist. I think the
next step might be to notify the KDE developers via the comp.windows.x.kde
NG. Is this bug specific to FreeBSD, or is it a bug of gcc 2.95.2 in
general?
Anyways, I installed gcc version 2.96 20000131, which is a snapshot. I
was able to compile kdesupport with no such errors. However,
compiling kdelibs is what gives me the libstdc++ errors, because Qt is
linked to gcc 2.95.2. I tried to compile Qt with gcc 2.96
20000131. However, as I soon found out, the development version has a
ghastly memory leak, which soon ate up all my memory and swap
(64M+130M). So, I was unable to recompile Qt with 2.96 to complete the
compilation.
- Donn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
