After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 545203 - gfile.c: argument is different type.
gfile.c: argument is different type.
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: gio
2.16.x
Other All
: Normal normal
: ---
Assigned To: Alexander Larsson
gtkdev
: 556458 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-07-28 18:37 UTC by Kazuki Iwamoto
Modified: 2009-04-20 10:09 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch for glib-2.16.5 (362 bytes, patch)
2008-07-28 19:02 UTC, Kazuki Iwamoto 		none Details | Review

Description Kazuki Iwamoto 2008-07-28 18:37:36 UTC 
Please describe the problem:
The first argument of g_set_error_literal is 'GError **'.
But g_set_error_literal is called with 'GError *' in gfile.c.

Steps to reproduce:
1. compile gfile.c

Actual results:
Following message is displayed.(Visual C++)
gfile.c(4204) : error C4047: 'function' : 'GError **' differs in levels of indirection from 'GError *'

Expected results:
g_set_error_literal (&error, G_IO_ERROR,
                     G_IO_ERROR_NOT_SUPPORTED,
                     _("Operation not supported"));

Does this happen every time?
Revision 7200 or later
glib-2.16.5

Other information:
Comment 1 Kazuki Iwamoto 2008-07-28 19:02:47 UTC 
Created attachment 115443 [details] [review]
patch for glib-2.16.5

g_set_error which is used in glib-2.16.5 has same problem.
Comment 2 Matthias Clasen 2008-07-28 19:13:44 UTC 
2008-07-28  Matthias Clasen  <mclasen@redhat.com>

        Bug 545203 – gfile.c: argument is different type.

        * gfile.c (open_read_async_thread): Pass a GError **
        to g_file_set_error_literal.
        Reported by Kazuki Iwamoto
Comment 3 Alexander Larsson 2009-04-20 10:09:35 UTC 
*** Bug 556458 has been marked as a duplicate of this bug. ***