<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [postgis-devel] 1.4 SVN Compile problems</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Paul,<BR>
<BR>
Aren't you getting email notices?<BR>
<BR>
Well I think the build log is on the link that Kevin sent somewhere I think (thought I can't access that link from where I am) - and also when I break a build, I get an email<BR>
with the log of where it broke. Its been pretty useful.<BR>
<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: postgis-devel-bounces@postgis.refractions.net on behalf of Paul Ramsey<BR>
Sent: Fri 10/10/2008 12:33 PM<BR>
To: PostGIS Development Discussion<BR>
Subject: Re: [postgis-devel] 1.4 SVN Compile problems<BR>
<BR>
Does this buildbot have an error log anywhere? It's pretty hopeless to<BR>
debug, it's not like I'm committing things that are broken for *me*,<BR>
so I need to see what's broken for *it*. BTW, it'll need to re-run<BR>
./configure to pick-up the file re-naming.<BR>
<BR>
P.<BR>
<BR>
On Fri, Oct 10, 2008 at 8:16 AM, Kevin Neufeld <kneufeld@refractions.net> wrote:<BR>
> It could simply be that trunk is currently in an unstable build state. (The<BR>
> autobuild is currently in a broken state as of three commits ago - revision<BR>
> 3086). It errors out compiling lwgeom_geos.o<BR>
><BR>
> <A HREF="http://postgis.refractions.net:8082/">http://postgis.refractions.net:8082/</A><BR>
><BR>
> Cheers,<BR>
> Kevin<BR>
><BR>
> Mark Cave-Ayland wrote:<BR>
>><BR>
>> Obe, Regina wrote:<BR>
>>><BR>
>>> This is probably my ineptness at compiling, but I thought I would try to<BR>
>>> experiment with 1.4 and got errors when its trying to compile the<BR>
>>> loader. Errors below. If I go into lwgeom etc. other directories and<BR>
>>> compile those separately, those seem to compile okay so seems to be just<BR>
>>> the loader that is giving me problems. What changed between 1.3.4SVN and<BR>
>>> 1.4SVN for the loader. I didn't have<BR>
>>> problems compiling 1.3.4SVN.<BR>
>>><BR>
>>> The others just seem to be warnings (which I don't remember getting<BR>
>>> before) except for this part<BR>
>>> lkrb5 -lz -lreadline -lcrypt -ldl -lm -o shp2pgsql<BR>
>>> /usr/lib/gcc/i586-suse-linux/4.2.1/../../../../i586-suse-linux/bin/ld:<BR>
>>> cannot find -lkrb5<BR>
>>> collect2: ld returned 1 exit status<BR>
>>><BR>
>>> This is on OpenSUSE 10.3 against a PostgreSQL 8.2.6 install<BR>
>>><BR>
>>> Thanks,<BR>
>>> Regina<BR>
>><BR>
>> Hmmmm looks as if the extra library dependencies are being added by PGXS<BR>
>> for the PROGRAM target - I have no idea why it feels the need to do this<BR>
>> though? The quick fix is to add the krb5 development headers which should be<BR>
>> in a package named something similar to krb5-devel or libkrb5-dev.<BR>
>><BR>
>><BR>
>> ATB,<BR>
>><BR>
>> Mark.<BR>
>><BR>
> _______________________________________________<BR>
> postgis-devel mailing list<BR>
> postgis-devel@postgis.refractions.net<BR>
> <A HREF="http://postgis.refractions.net/mailman/listinfo/postgis-devel">http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR>
><BR>
_______________________________________________<BR>
postgis-devel mailing list<BR>
postgis-devel@postgis.refractions.net<BR>
<A HREF="http://postgis.refractions.net/mailman/listinfo/postgis-devel">http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
The substance of this message, including any attachments, may be confidential, legally privileged and/or exempt from disclosure pursuant to Massachusetts law. It is intended solely for the addressee. If you received this in error, please contact the sender and delete the material from any computer.
</STRONG></P></BODY></HTML>
<P><hr size=1></P>
<P><STRONG><font size="2" color="339900"> Help make the earth a greener place. If at all possible resist printing this email and join us in saving paper. </p> <p> </font></STRONG></P>