[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: KDE With Sun Forte C++
From: Adriaan de Groot <adridg () cs ! kun ! nl>
Date: 2004-06-16 10:09:31
Message-ID: 200406161209.32085.adridg () cs ! kun ! nl
[Download RAW message or body]
I'm trying to build KDE with CC: Sun C++ 5.5 Patch 113817-07 2004/03/23 -
vaguely supposing that this is a supported compiler - and it's not going very
quickly. Here and there I've made changes to get stuff to compile, like
class A
{
private:
class B;
typedef QValueList<B> BList;
class B
{
private:
BList *m_list;
}
}
which CC complains about (since BList is private in A) and gcc doesn't.
Library modules typically need -lCstd -lCrun -lc added.
Anyway, questions:
1) Has anyone managed to compile KDE with Sun Forte C++?
2) Which compiler is right wrt. the nesting issue above?
3) I'm now working on kssl, and getting things like this:
"kopenssl.cc", line 450: Error: Cannot assign rsa_st*(*)(int,unsigned
long,void(*)(int,int,void*),void*) to extern "C" rsa_st*(*)(int,unsigned
long,extern "C" void(*)(int,int,void*),void*).
"kopenssl.cc", line 451: Warning (Anachronism): Assigning int(*)
(__FILE*,X509_req_st*) to extern "C" int(*)(__FILE*,X509_req_st*).
"kopenssl.cc", line 452: Warning (Anachronism): Assigning void(*)() to extern
"C" void(*)().
now, this tells me that Forte considers 'extern "C"' an additional type
modifier (instead of just linkage info), and that it's being a pain about
type coercion. For this bit of code, would it make sense to add the 'extern
"C"' s where needed?
--
"On top of that [watching KDE CVS] is interesting in a perverse
way, like watching sausage get made. By very smart people." - dkite
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic