Your message dated Mon, 5 Sep 2005 23:10:19 +0200
with message-id <[EMAIL PROTECTED]>
and subject line gnet: Can't declare a GUnixSocket* element in a struct
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 28 Aug 2005 11:50:50 +0000
>From [EMAIL PROTECTED] Sun Aug 28 04:50:50 2005
Return-path: <[EMAIL PROTECTED]>
Received: from fry.debianforum.de (mail.debianforum.de) [213.239.213.245] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1E9LgX-0001Lv-00; Sun, 28 Aug 2005 04:50:50 -0700
Received: from localhost (localhost [127.0.0.1])
        by mail.debianforum.de (Postfix) with ESMTP id 0DA07B1C0B6
        for <[EMAIL PROTECTED]>; Sun, 28 Aug 2005 13:50:46 +0200 (CEST)
Received: from mail.debianforum.de ([127.0.0.1])
        by localhost (mail.debianforum.de [127.0.0.1]) (amavisd-new, port 10024)
        with ESMTP id 30838-03 for <[EMAIL PROTECTED]>;
        Sun, 28 Aug 2005 13:50:42 +0200 (CEST)
Received: from wall.foobar.lan (p54B4B442.dip0.t-ipconnect.de [84.180.180.66])
        (using TLSv1 with cipher AES256-SHA (256/256 bits))
        (No client certificate requested)
        by mail.debianforum.de (Postfix) with ESMTP id BD5A5B1C0AD
        for <[EMAIL PROTECTED]>; Sun, 28 Aug 2005 13:50:41 +0200 (CEST)
Received: from florian by wall.foobar.lan with local (Exim 4.50)
        id 1E9LPu-0000lc-Iq
        for [EMAIL PROTECTED]; Sun, 28 Aug 2005 13:33:39 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Florian Ragwitz <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: gnet: Can't declare a GUnixSocket* element in a struct
X-Mailer: reportbug 3.8
Date: Sun, 28 Aug 2005 13:33:37 +0200
Message-Id: <[EMAIL PROTECTED]>
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at debianforum.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: gnet
Severity: normal

Hello,

compiling the following program doesn't work:

#include <gnet.h>

typedef struct {
        GTcpSocket* tcp;
        GUnixSocket* unix;
} socket;

int main (int argc, char** argv) {
        return 0;
}

It gives me an error about a syntax error after a numeric constant in
the GUnixSocket line.

If I omit this line it works.


Regards,
Flo

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-686
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)

---------------------------------------
Received: (at 325403-done) by bugs.debian.org; 5 Sep 2005 21:10:30 +0000
>From [EMAIL PROTECTED] Mon Sep 05 14:10:30 2005
Return-path: <[EMAIL PROTECTED]>
Received: from fry.debianforum.de (mail.debianforum.de) [213.239.213.245] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1ECOEY-0002e0-00; Mon, 05 Sep 2005 14:10:30 -0700
Received: from localhost (localhost [127.0.0.1])
        by mail.debianforum.de (Postfix) with ESMTP id 4E62DB1C0BD
        for <[EMAIL PROTECTED]>; Mon,  5 Sep 2005 23:10:29 +0200 (CEST)
Received: from mail.debianforum.de ([127.0.0.1])
        by localhost (mail.debianforum.de [127.0.0.1]) (amavisd-new, port 10024)
        with ESMTP id 03979-06 for <[EMAIL PROTECTED]>;
        Mon, 5 Sep 2005 23:10:21 +0200 (CEST)
Received: from wall.foobar.lan (p54B49D83.dip0.t-ipconnect.de [84.180.157.131])
        (using TLSv1 with cipher AES256-SHA (256/256 bits))
        (No client certificate requested)
        by mail.debianforum.de (Postfix) with ESMTP id BB144B1C0AD
        for <[EMAIL PROTECTED]>; Mon,  5 Sep 2005 23:10:20 +0200 (CEST)
Received: from florian by wall.foobar.lan with local (Exim 4.50)
        id 1ECOEN-0001Dc-4m
        for [EMAIL PROTECTED]; Mon, 05 Sep 2005 23:10:19 +0200
Date: Mon, 5 Sep 2005 23:10:19 +0200
From: Florian Ragwitz <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: gnet: Can't declare a GUnixSocket* element in a struct
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8"
Content-Disposition: inline
Priority: normal
X-Operating-System: Debian GNU/Linux 2.6.7-1-686
X-Binford: 5100 (more power)
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at debianforum.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02


--ibTvN161/egqYuK8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello,

this bug occured because "unix" is defined to "1" (cpp showed this to
me) because we're on a unix system. This is totally OK and not a bug.

-Flo

--=20
BOFH excuse #215:
High nuclear activity in your area.

--ibTvN161/egqYuK8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFDHLQ6dC8qQo5jWl4RAvJCAKCEbCbku5ha8QcK9qIoTAgU08eV8QCffifT
84LGAK4jYLjJeGtXNztMOEM=
=ZZl7
-----END PGP SIGNATURE-----

--ibTvN161/egqYuK8--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to