[Gambas-user] build 2026 failing
Benoît Minisini
gambas at ...1...
Fri Jun 19 01:48:08 CEST 2009
> gambas3, build 2026, x_64, arch
>
> I'm getting:
>
> make[4]: Entering directory `/home/test/gambas3/src/trunk/main/gbx'
> gcc -DHAVE_CONFIG_H -I. -I.. -I../share -D_REENTRANT -I../libltdl
> -I/usr/lib/libffi-3.0.8/include
> -DGAMBAS_PATH="\"/home/test/gambas3/pkg/usr/bin\"" -pipe -Wall
> -Wno-unused-value -fsigned-char -fvisibility=hidden -g -Os -MT
> gbx3-gbx_debug.o -MD -MP -MF .deps/gbx3-gbx_debug.Tpo -c -o
> gbx3-gbx_debug.o `test -f 'gbx_debug.c' || echo './'`gbx_debug.c
> In file included from gbx_class.h:30,
> from gbx_exec.h:31,
> from gbx_debug.c:35:
> gbx_class_desc.h:105: error: duplicate member ‘_reserved’
> gbx_class_desc.h:123: error: duplicate member ‘_reserved’
> In file included from gbx_exec.h:38,
> from gbx_debug.c:35:
> gbx_variant.h: In function ‘VARIANT_free’:
> gbx_variant.h:55: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> gbx_variant.h:55: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> gbx_variant.h:55: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> gbx_variant.h:55: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> gbx_variant.h: In function ‘VARIANT_keep’:
> gbx_variant.h:63: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> gbx_variant.h:67: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> gbx_variant.h:67: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> gbx_variant.h: In function ‘VARIANT_is_null’:
> gbx_variant.h:76: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> gbx_variant.h:79: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> gbx_variant.h: In function ‘VARIANT_clear’:
> gbx_variant.h:90: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
> make[4]: *** [gbx3-gbx_debug.o] Error 1
>
Fixed in revision #2027 !
--
Benoît
More information about the User
mailing list