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 681244 - Configure errors out from AC_CHECK_ALIGNOF
Configure errors out from AC_CHECK_ALIGNOF
Status: RESOLVED DUPLICATE of bug 674483
Product: glib
Classification: Platform
Component: build
2.32.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2012-08-05 16:19 UTC by Marko Lindqvist
Modified: 2012-08-05 19:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Workaround (303 bytes, patch)
2012-08-05 17:48 UTC, Marko Lindqvist
none Details | Review

Description Marko Lindqvist 2012-08-05 16:19:09 UTC
Configure errors out with "cannot compute alignment of guint32"
From config.log:

conftest.c: In function 'main':
conftest.c:121:12: error: size of array 'test_array' is negative
conftest.c:121:12: error: storage size of 'test_array' isn't constant
conftest.c:121:12: warning: unused variable 'test_array' [-Wunused-variable]
...
configure:28574: error: in `/tmp/crosser-cazfi/build/glib':
configure:28576: error: cannot compute alignment of guint32
See `config.log' for more details


It seems that this alignment check is AC_CHECK_ALIGNOF in configure.ac. Google found mails from autoconf bugs list about this error (I didn't search for glib specific error, but it turned out that one reported to autoconf list was about glib too). There it was declared (glib) configure.ac bug, not autoconf bug.
http://lists.gnu.org/archive/html/bug-autoconf/2012-04/msg00026.html
Comment 1 Marko Lindqvist 2012-08-05 17:48:59 UTC
Created attachment 220394 [details] [review]
Workaround

This is the workaround I used to get past the error.
Comment 2 Allison Karlitskaya (desrt) 2012-08-05 19:41:24 UTC
Reading the discussion on the list it seems that our problem is that invocation of macros inside of open-coded if statements is not permitted in autoconf and that we should be using AS_IF instead.
Comment 3 Allison Karlitskaya (desrt) 2012-08-05 19:43:42 UTC
Ah.  Looks like this was already fixed a few months ago...

*** This bug has been marked as a duplicate of bug 674483 ***