[FGS] Success!

Frank Warmerdam warmerdam at pobox.com
Thu Jul 12 12:12:02 EDT 2007

Normand Savard wrote:
> Frank Warmerdam wrote:
>> Folks,
>> OK, I have successfully build updated FGS installers and modules on
>> the download.osgeo.org system.  I have also incorporated the 
>> gdal_ecw-module
>> and gdal_python-module for an ECW plugin, and GDAL python support.
>> The modules directory is:
>>   http://download.osgeo.org/gdal/fgs-modules
>> A GDAL focused installer is available as:
>>  http://download.osgeo.org/gdal/fgs-modules/fgs-gdal-python-1.4.2-linux-i386.bin 
>> A self installer with mapserver, python mapscript and I presume all 
>> the usual
>> php stuff is available as:
>> http://download.osgeo.org/gdal/fgs-modules/fgs-all-0.3a-linux-i386.bin
>> I have the self-installers defaulting to install libstdc++ as I found
>> the FC4'ish dependency was not present on my Ubuntu system I use for
>> testing.
>> Almost all my changes are checked into CVS.  I'd appreciate those who
>> make the "standard distribution FGS" stuff doing a test build to ensure
>> I haven't seriously broken anything.
> Frank,
> I'm trying to build a fgs package that includes gdal_python.  I get the 
> following error:
> python setup.py build
> 'import site' failed; use -v for traceback
> Traceback (most recent call last):
> File "setup.py", line 4, in ?
>   import os
> ImportError: No module named os
> make: *** [build] Error 1
> I know that it is because fgsdev is using the version of Python on the 
> computer I'm building the package on which is 2.3.5, instead of using 
> the version built with fgs.  I check in your makefile that is called by 
> fgs_build and you use "python setup.py build".  I know that for 
> python_mapscript I have to use "$FGS_BUILD_HOME/python/bin/python 
> setup.py build" in order to call the correct python interpreter.  I saw 
> that you set $PYTHONHOME environment variable but it seems to have no 
> effect in selecting the correct python binary.


I have committed a change to the gdal_python fgs_build to add
$FGS_BUILD_HOME/python/bin to the front of the path before doing
the "make build".  Could you "cvs update" and see if that fixes the
issue for you?

Best regards,
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | President OSGeo, http://osgeo.org

More information about the Foss-gis-suite mailing list