On 23 Sep, you wrote: > On Sat, Sep 23, 2006, Stefan Bellon wrote: > > > > Could you try downgrading your pango packages to 1.12.3-2? > > > > (Either from snapshot.debian.net, or 1.12.3-1+b1 from testing.) > > > Could you also try downgrading glib packages to 2.10 from > > > snapshot? > > What's the easiest way of doing this? If I try to downgrade > > pango1.0 and glib2.0 packages, I get a lot of broken packages > > related to gnome and have to remove almost all packages.
> You add a line such as: > deb http://snapshot.debian.net/archive pool pango1.0 > to sources.list, then select the appropriate version with aptitude. That's *exactly* what I was doing. > You should not have to downgrade any package to downgrade to the > versions I mention. I'm sorry, not here. Packages like evolution, gnome-pilot-conduits, multisync0.90, gtk2-engines-pixbuf, mplayer, libgtk2.0-0, wireshark, xcdroast and firefox all depend on libpango1.0-0 (>= 1.12.4), so I cannot downgrade it to 1.12.3-2 without breaking lots of packages. > > Anything else I could supply? > Yes, tell me what command causes the problem and how to run it in the > same conditions. Well, I get it in a quite large project which involves C, Ada, Gtk+ and GtkAda. It's not easy to strip that down. ... some time later ... Ok, I've tracked it down a bit now. When I just touch a file and compile it with gcc into some empty object file foo.o in order to have something to link and then do the following gcc link call, then I get the problem: gcc foo.o -L/usr/local/gtkada/lib -lpangocairo-1.0 -lgobject-2.0 -o foo Inside /usr/local/gtkada/lib there are indeed versions of the libraries that are non-Debian, but vendor supplied. But still I wonder a) why it worked in the past (there must have been a change in the Debian libraries that changed the behaviour) b) gcc reports that there is the undefined reference in /usr/lib/libpango-1.0.so.0 which looks to me as gcc is taking the libraries from /usr/lib and not from /usr/local/gtkada/lib at all I can workaround the problem by specifying -Wl,-R/usr/local/gtkada/lib instead of just -L/usr/local/gtkada/lib, so that the Debian libraries are not taken at all but the ones in /usr/local/gtkada/lib. Then everything works again. But previously it even worked with the Debian libraries. Therefore it's no showstopper for me, but I'm still curious why the behaviour changed. -- Stefan Bellon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]