yep, my bad ...<br>.29 isn't in unstable yet, so I don't know if this was fixed<br>tb <br><br><div><span class="gmail_quote">On 7/12/06, <b class="gmail_sendername">Steve Lime</b> <<a href="mailto:Steve.Lime@dnr.state.mn.us">
Steve.Lime@dnr.state.mn.us</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">There is a 1.3.29 I think.<br><br>Steve<br><br>
>>> thomas bonfort <<a href="mailto:thomas.bonfort@GMAIL.COM">thomas.bonfort@GMAIL.COM</a>> 7/12/2006 10:50:03 AM >>><br>just my 2c<br>latest swig (1.3.28) prevents python mapscript from being properly executed:
<br>ImportError: ../../build/lib.linux-i686-2.3/_mapscript.so: undefined symbol:<br>intarray_setitem<br>see also <a href="http://trac.gispython.org/projects/PCL/ticket/44">http://trac.gispython.org/projects/PCL/ticket/44</a>
<br><br>this is not the case with 1.3.24 (or .27 according to the previous link)<br><br>cheers<br><br><br><br>On 7/12/06, Daniel Morissette <<a href="mailto:dmorissette@mapgears.com">dmorissette@mapgears.com</a>> wrote:
<br>><br>> Steve Lime wrote:<br>> > Hi all: Currently all distributions comming off <a href="http://cvs.gis.umn.edu">cvs.gis.umn.edu</a> are<br>> being build with Swig 1.3.21. I'm just wondering what folks think about
<br>> moving to the latest versions. Has anyone played with MapScript generated by<br>> the new version?<br>> ><br>> > Steve<br>> ><br>><br>> I haven't played with SWIG much lately so I do not have an opinion on
<br>> the upgrade, but I think we should generate the 4.8.4 release before<br>> doing the switch just to be safe.<br>><br>> BTW, I will prepare the 4.8.4 source for the release later today and<br>> will let you know when it's ready to package.
<br>><br>> Daniel<br>> --<br>> Daniel Morissette<br>> <a href="http://www.mapgears.com/">http://www.mapgears.com/</a><br>><br><br></blockquote></div><br>