Bug 14852 - Telepathy-glib fails to build on ppc64
Summary: Telepathy-glib fails to build on ppc64
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-glib (show other bugs)
Version: unspecified
Hardware: PowerPC All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-06 07:56 UTC by Brian Pepple
Modified: 2008-03-07 08:30 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Full build log for tp-glib on ppc64 (75.58 KB, text/plain)
2008-03-06 07:56 UTC, Brian Pepple
Details

Description Brian Pepple 2008-03-06 07:56:54 UTC
Created attachment 14878 [details]
Full build log for tp-glib on ppc64

Summary says it all.  Here's a snippet from the build log, where it fails:
<snip>
ranlib .libs/libtelepathy-glib-internal.a
creating libtelepathy-glib-internal.la
(cd .libs && rm -f libtelepathy-glib-internal.la && ln -s ../libtelepathy-glib-internal.la libtelepathy-glib-internal.la)
/usr/bin/nm -B .libs/libtelepathy-glib-internal.a > _gen/abi.nm
grep " T " < _gen/abi.nm > _gen/abi.funcs
make[3]: *** [_gen/abi.txt] Error 1
make[3]: Leaving directory `/builddir/build/BUILD/telepathy-glib-0.7.4/telepathy-glib'
make[2]: *** [all] Error 2
rm _gen/tp-spec-channel.xml _gen/tp-spec-generic.xml _gen/tp-spec-connection.xml _gen/tp-spec-dbus-daemon.xml _gen/tp-spec-media-session-handler.xml _gen/tp-spec-connection-manager.xml _gen/tp-spec-media-stream-handler.xml
make[2]: Leaving directory `/builddir/build/BUILD/telepathy-glib-0.7.4/telepathy-glib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/builddir/build/BUILD/telepathy-glib-0.7.4'
make: *** [all] Error 2
<snip>

This appears to be due to the fact that some architectures use function descriptors, which will be prefixed by ' D ' not ' T ' in the 'nm' output.
Comment 1 Simon McVittie 2008-03-07 08:30:09 UTC
Fixed in 0.7.5, thanks!


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.