Mailinglist Archive: opensuse-programming-de (42 mails)

< Previous Next >
Re: [opensuse-programming-de] Fehler bei Seamonkey 2.0 / gcc 3.3.5
  • From: Sebastian Siebert <freespacer@xxxxxx>
  • Date: Sat, 14 Nov 2009 22:28:33 +0100
  • Message-id: <4AFF2101.5000500@xxxxxx>
David Haller schrieb:
In file included from nsDOMFile.cpp:39:
../../../dist/include/content/nsDOMFile.h: At global scope:
../../../dist/include/content/nsDOMFile.h:56: warning: `class nsDOMFile' has
virtual functions but non-virtual destructor
../../../dist/include/xpcom/nsCOMPtr.h: In constructor `
nsCOMPtr<T>::nsCOMPtr(T*) [with T = nsIFile]':
../../../dist/include/content/nsDOMFile.h:63: instantiated from here
../../../dist/include/xpcom/nsCOMPtr.h:552: error: no matching function for
call to `nsCOMPtr_base::nsCOMPtr_base(nsIFile*&)'
../../../dist/include/xpcom/nsCOMPtr.h:416: error: candidates are:
nsCOMPtr_base::nsCOMPtr_base(const nsCOMPtr_base&)
../../../dist/include/xpcom/nsCOMPtr.h:420: error:
nsCOMPtr_base::nsCOMPtr_base(nsISupports*)

==== dist/include/content/nsDOMFile.h ====
class nsDOMFile : public nsIDOMFile,
public nsICharsetDetectionObserver
{
public:
NS_DECL_ISUPPORTS
NS_DECL_NSIDOMFILE

nsDOMFile(nsIFile *aFile)
: mFile(aFile)
{}
virtual ~nsDOMFile() {};
[..]
private:
nsCOMPtr<nsIFile> mFile;
====

==== dist/include/xpcom/nsCOMPtr.h ====
class
nsCOMPtr_base
{
public:

nsCOMPtr_base( nsISupports* rawPtr = 0 )
: mRawPtr(rawPtr) Zeile.
{
// nothing else to do here
====

Liegt's am gcc-3.3.5 oder ...? Ich steh ziemlich auf dem Schlauch.

-dnh


Hallo David,

- Welche Schalter gibst du dem configure-script?
- Welche Schalter werden an c++ übergeben bevor der Fehler auftritt?
(komplette Zeile vom Bau mal einfügen)


--
Gruß Sebastian - openSUSE Member (Freespacer)
<http://de.opensuse.org/Benutzer:Freespacer>
Wichtiger Hinweis zur openSUSE Mailing Liste:
<http://de.opensuse.org/OpenSUSE_mailing_list_netiquette>
--
To unsubscribe, e-mail: opensuse-programming-de+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-programming-de+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups
References