Re: gworldclock FTBFS: libgdk-x11-2.0 has "undefined reference to `XineramaIsActive'"
On Sun, Apr 06, 2003 at 08:35:04AM +1000, Drew Parsons wrote:
> Dear m68k porters,
>
> I've uploaded a new version of gworldclock (v1.1).
>
> It fails to build on m68k, the build log is at
> http://buildd.debian.org/build.php?&pkg=gworldclock&ver=1.1-1&arch=m68k&file=log
>
> The build log says:
>
> gcc -g -O2 -o gworldclock main.o misc.o resize.o sync.o timer.o zones.o
> -Wl,--export-dynamic -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0
> -lm -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl
> -lglib-2.0
> /usr/lib/gcc-lib/m68k-linux/3.2.3/../../../libgdk-x11-2.0.so: undefined
> reference to `XineramaIsActive'
> /usr/lib/gcc-lib/m68k-linux/3.2.3/../../../libgdk-x11-2.0.so: undefined
> reference to `XineramaQueryScreens'
> collect2: ld returned 1 exit status
> make[1]: *** [gworldclock] Error 1
>
>
> The problem with Xinerama did not occur on m68k during the last build last
> October (against libgtk+2 v2.0, currently we have v2.2). It builds fine on
> other architectures (except I'm still waiting for arm).
>
> The reference to libgdk-x11-2.0.so is generated automatically by pkg-config,
> GTK+2's build configuration tool.
>
> What can be done about the problem?
I guess it's not your fault, I was about to retry it on another machine that
has an older gcc and gtk+2.0 installed. Two other packages that failed built
fine on that box...
The immediate problem is, the buildd mail script is too clever for me, I
tried to reply to the other buildd to rebuild it there, but it noted that it
was registered by another buildd, so I guess I have to do that manually,
unless somebody comes up with a clever trick. Maybe I can give it back first
and then retry on the other...
But the more important problem is, how do we fix gcc/gtk+2.0... any ideas
welcome (and the porters live on m68k-build).
Christian
Reply to: