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 688083 - some multilib distrib may result in wrong alignment (exposed by unit-test)
some multilib distrib may result in wrong alignment (exposed by unit-test)
Status: RESOLVED FIXED
Product: at-spi
Classification: Platform
Component: at-spi2-core
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Li Yuan
At-spi maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-11-11 09:16 UTC by Nikolay Orlyuk
Modified: 2012-11-12 17:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Nikolay Orlyuk 2012-11-11 09:16:32 UTC 
dbind/dbtest exposes an issue related with left dbind/dbind-config.h in releases of 2.6.1 and 2.7.1 which contains values for some platform that looks to be one with 64bit word size.
Some distributives (at least Exherbo) which uses technique where 32bit and 64bit versions of library are built without touching original sources (and thus without overwriting dbind-config.h by configure) results bad libdbind.la build under 32bit version. That caused by picking up dbind-config.h include from source folder during preprocessing/compilation.

I think all files (with .in pairs) that is generated by configure shouldn't be present in final release archive.
Comment 1 Nikolay Orlyuk 2012-11-11 10:06:19 UTC 
Same for at-spi2-atk
Comment 2 Mike Gorse 2012-11-12 17:53:33 UTC 
I've removed dbind-config from the distribution:
at-spi2-core master: a44a807
at-spi2-core gnome-3-6 branch: 6891174
at-spi2-atk gnome-3-6 branch: a24c0d

Dbind wasn't actually used by at-spi2-atk except in droute-test.c, so I've adapted the test to stop using it and removed it from the distribution altogether for at-spi2-atk 3.7 (it now lives only in at-spi2-core).