Paul Smith wrote:
> On Fri, 2008-02-29 at 16:59 -0800, Rick Knight wrote:
>   
>> Paul, Thanks for the reply. I'm using Kubuntu 7.04 Feisty.
>>     
>
> That's probably too old to build easily; you're using a version of Gnome
> libraries that are an extra rev back from the latest stable version
> (that was released with 7.10).
>
> Did you set the DISTRO variable to "feisty"?  You definitely need to do
> that.  I haven't tried that in a long time since I upgraded to Gutsy in
> October, but it was working then (on Ubuntu; I don't use KDE/Kubuntu).
> You might also have to add extra libraries to local_PACKAGES as
> described at the bottom of my description.
>   
OK, I added DISTRO="feisty" and installed package 
libexchange-storage1.2-3-dev. I also added /opt/gnome2/lib and 
/opt/gnome2/lib/evolution/2.12 to LD_LIBRARY_PATH. Everything now 
configures without error and everything except evolution-exchange builds 
and installs without error. When I try to make evolution-exchange I get 
this error...'

../calendar/.libs/libexchangecalendar.a(e-cal-backend-exchange.o): In 
function `open_calendar':
/home/rknight/Share/svn/gnome/evolution-exchange/calendar/e-cal-backend-exchange.c:425:
 
undefined reference to `exchange_account_scan_foreign_hierarchy'
collect2: ld returned 1 exit status
make[2]: *** [evolution-exchange-storage] Error 1
make[2]: Leaving directory 
`/home/share/svn/gnome/evolution-exchange/storage'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/share/svn/gnome/evolution-exchange'
make: *** [all] Error 2

My build commands are...
PKG_CONFIG_PATH=/opt/gnome2/lib/pkgconfig/ ./autogen.sh --prefix=/opt/gnome2
make $CPUS

I have Evolution, Evolution-Data-Server, Evolution-Webcal, libsoup and 
gtkhtml built the same way and installed in /opt/gnome2. What else do I 
need here to get Evolution-Exchange to build and install?

Thanks again,
Rick
_______________________________________________
Evolution-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/evolution-list

Reply via email to