Bug#386815: gtk+2.0: FTBFS (ppc64): sibling call optimization to `IA__gdk_display_open' does not allow automatic multiple TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls
Andreas Jochens
aj at andaco.de
Fri Jun 15 07:56:40 UTC 2007
Hello,
On Thu, Jun 14, 2007 at 10:47:32PM +0200, Loïc Minier wrote:
> Thanks for the patch, I've applied it to the experimental tree which
> should soon move to unstable.
Great, thanks!
> Since it's failing during ld, I would have assumed I could use LDFLAGS
> instead of CFLAGS, do you think that would be a problem?
The -mminimal-toc flag has to be in CFLAGS. Otherwise the package does
not build.
> Do you agree it's a bug in binutils? Or do you think gtk upstream
> should make IA__gdk_display_open extern on ppc64?
>
> (I'd like to get this fixed at the proper place to build out of the
> box; either ld should find its way, or gtk's upstream should change the
> code and/or pass a flag for ppc64.)
I am not sure if this will be considered as a bug in binutils by the
relevant toolchain people.
Personally, I think it should be possible to build large pieces of
code on ppc64 without having to explicitly add the extra -mminimal-toc
flag. The ppc64 architecture seems to be the only architecture which
requires such a flag for large object code sizes. There should be a
way to handle this by the toolchain automatically.
However, I do not think that the ppc64 toolchain will be changed to
do this in the near future. At the moment there is no other fix
for this problem besides adding -mminimal-toc flags to CFLAGS.
Regards
Andreas Jochens
More information about the pkg-gnome-maintainers
mailing list