Re: [Evolution-hackers] Failing to build latest GIT code

2009-11-25 Thread Paul Smith
On Wed, 2009-11-25 at 15:05 -0500, Matthew Barnes wrote:
> Do you know of a good way to make that more detectable for developers,
> short of uninstalling Evolution?
> 
> We've had several similar "insufficent LIBADD" bugs lately, all of which
> slipped in under my radar because I keep Evolution installed.

If you've installed the latest evolution into your main system
directories (/lib, /usr/lib, etc.) then there's no good way to do that.
The best you can do is create a virtual machine or fakeroot environment:
I'm not overly familiar with that but Google knows how.

Since I _never_ do that, and only ever install it into /opt/evo or
similar, it's easy enough for me to either (a) delete the previous
installation and start from scratch, or (b) change the directory where
it installs into /opt/evo-test or whatever, that doesn't exist.

___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers


Re: [Evolution-hackers] Failing to build latest GIT code

2009-11-25 Thread Matthew Barnes
On Wed, 2009-11-25 at 08:23 -0500, Paul Smith wrote:
> You will only hit this if you don't already have Evo installed.  If
> you have it installed then the link will use the installed version.
> Most likely that's the problem: the linker found a different libeshell
> somewhere on your system.

Do you know of a good way to make that more detectable for developers,
short of uninstalling Evolution?

We've had several similar "insufficent LIBADD" bugs lately, all of which
slipped in under my radar because I keep Evolution installed.

Matthew Barnes

___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers


Re: [Evolution-hackers] Failing to build latest GIT code

2009-11-25 Thread Paul Smith
On Wed, 2009-11-25 at 11:48 +0100, Milan Crha wrote:
> hrm, I would like to know why I didn't face that when doing the change
> there. Maybe an older gcc or something?

You will only hit this if you don't already have Evo installed.  If you
have it installed then the link will use the installed version.  Most
likely that's the problem: the linker found a different libeshell
somewhere on your system.

___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers


Re: [Evolution-hackers] Failing to build latest GIT code

2009-11-25 Thread Milan Crha
On Tue, 2009-11-24 at 12:25 -0500, Paul Smith wrote:
> On Tue, 2009-11-24 at 12:15 -0500, Paul Smith wrote:
> > What am I missing here?
> 
> found it.  Please apply this patch to fix the build:

Hi,
hrm, I would like to know why I didn't face that when doing the change
there. Maybe an older gcc or something?
Bye,
Milan

___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers