pinentry - unproper use of glib allocation
Maciej Piechotka
uzytkownik2 at gmail.com
Sun Feb 17 14:14:20 CET 2008
On Feb 17, 2008 1:47 PM, Maciej Piechotka <uzytkownik2 at gmail.com> wrote:
>
> On Feb 17, 2008 11:50 AM, Maciej Piechotka <uzytkownik2 at gmail.com> wrote:
> > With the newest glib it is impossible to compile pinentry:
> > i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/gtk-2.0
> > -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo
> > -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
> > -I/usr/lib/glib-2.0/include -I/usr/include/freetype2
> > -I/usr/include/libpng12 -I../secmem -I../pinentry -Wall -O2
> > -march=pentium-m -mfpmath=sse -pipe -momit-leaf-frame-pointer -ggdb -w
> > -ftree-vectorize -ftree-loop-optimize -Wall -Wcast-align -Wshadow
> > -Wstrict-prototypes -c gtksecentry.c
> > gtksecentry.c:274: error: conflicting types for 'g_malloc'
> > /usr/include/glib-2.0/glib/gmem.h:47: error: previous declaration of
> > 'g_malloc' was here
> > gtksecentry.c:292: error: conflicting types for 'g_malloc0'
> > /usr/include/glib-2.0/glib/gmem.h:48: error: previous declaration of
> > 'g_malloc0' was here
> > gtksecentry.c:312: error: conflicting types for 'g_realloc'
> > /usr/include/glib-2.0/glib/gmem.h:50: error: previous declaration of
> > 'g_realloc' was here
> >
> > Since the gmem api was misused. It should be done by setting
> > GMemVTable instead of definition of g_*alloc* in file.
> >
> > Best regards
> >
>
> Quick'n'dirty patch - all gobjects in secure memory.
>
I think this emulates the orginal behaviour using GMemVTable.
Best regards
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gmem.patch
Type: application/octet-stream
Size: 2850 bytes
Desc: not available
URL: </pipermail/attachments/20080217/40e5a2f3/attachment.obj>
More information about the Gnupg-devel
mailing list