Re: Information sought from Debian Sid users

[Rob Adams <readams readams net>]

Yes, I had a very similar problem.  I was unable to link ORBit2 because
libtool was trying to link to my /usr/lib libraries rather than the ones
in my jhbuild root.  Removing the -dev gnome-related debian packages
fixed that problem, though I ended up with another problem building gtk
further down the road.  I've been having this problem for a couple of
weeks though, not just since Friday.

This is likely related to a bug in libtool that causes the linking to
not respect the order in which the include directories were specified
and so ends up linking to the wrong library.  I've run into this bug
several times before when trying to build gnome from CVS, causing
problems not just at compile time in ORBit2 but also in gnomemeeting at
run time.  I don't know what the status is for fixing this bug in
upstream libtool, or even if the maintainers consider this behavior to
be a bug.

-Rob

On Sun, 2003-10-26 at 18:20, Malcolm Tredinnick wrote:
> Dear bleeding edge friends,
> 
> I am trying to track down a problem that was reported on
> gnome-accessibility-list recently and I need input from people who are
> using very recent Debian Sid installations.
> 
> The best I have is that somebody who grabbed all the latest Sid upgrades
> last Friday is seeing this problem, so I'm looking for people who
> upgraded either just before or around that time.
> 
> (1) Was libtool upgraded? If so, what version is now being run?
> 
> (2) Are there suddenly compilation problems for any modules that use the
> standard gnome-common autogen.sh script with respect to the ltmain.sh
> script? Try to build something like libgnome from a very clean CVS copy
> (start with no non-CVS files before running autogen.sh). Does it work
> when it comes to linking libraries (if you see the same problem I am
> chasing down, you will know. We are not talking about a subtle breakage
> here)?
> 
> I know that gnopernicus is having problems. What I am trying to work out
> is whether this is a generic problem that affects everybody with some
> upgraded libtool version or if it is something special with gnopernicus
> (which is difficult to see, since it is pretty standard stuff in there).
> I do not use Debian, so I cannot test this myself. But if recent
> upgrades have broken CVS builds, then it's obviously something that we
> need to fix pretty quickly.
> 
> At the moment I don't know if this is a real problem or not. So I am
> gathering bread crumbs. Please supply said crumbs.
> 
> Cheers,
> Malcolm
> _______________________________________________
> desktop-devel-list mailing list
> desktop-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/desktop-devel-list