On vendredi 19 avril 2019 15:36:33 CEST Fengting Chen wrote:
> Removing .libs helped and now pytest is working. Thank you!
>
> Instead of using pytest to run all the tests, how to run individual test?
https://docs.pytest.org/en/latest/ for full reference
And
https://github.com/OSGeo/gdal/blob/ma
Removing .libs helped and now pytest is working. Thank you!
Instead of using pytest to run all the tests, how to run individual test?
On 4/18/2019 3:00 PM, Even Rouault wrote:
Not sure how you find out I used libtool build. In my configure option,
I did specify "--without-libtool".
/scratch/gd
On jeudi 18 avril 2019 19:01:34 CEST John Daniel wrote:
> I had tried 3 different versions of SpatiaLite (4.1.1 - 5.0) since that
> seemed to be where the problem is. My last known good build used
> SpatialLite 4.3.0a.
>
> Is there a list of recommended version of various supporting libraries? I
>
> Not sure how you find out I used libtool build. In my configure option,
> I did specify "--without-libtool".
/scratch/gdal/gdal/gdal/.libs/libgdal.so.20 is a file produced by a libtool
build. You perhaps did initially a libtool build and then a non-libtool one.
Remove /scratch/gdal/gdal/gdal/.l
On 4/18/2019 1:11 PM, Even Rouault wrote:
On jeudi 18 avril 2019 12:38:43 CEST Fengting Chen wrote:
In my case, this didn't work.
1. When I ran the GDAL build, I always use "make clean" to clean the old
build. And I did run scripts/setdevenv.sh before running the test.
/>which gdalinfo//
///
On jeudi 18 avril 2019 16:41:41 CEST John Daniel wrote:
> Even,
> scripts/setdevenv.sh did fix the python problem for me.
>
> However, I get a very similar segfault in the test scripts that I get on the
> Mac. It seems related to SQLite and SpatiaLite. I'm going to try to rebuild
> with an older s
On jeudi 18 avril 2019 12:38:43 CEST Fengting Chen wrote:
> In my case, this didn't work.
>
> 1. When I ran the GDAL build, I always use "make clean" to clean the old
> build. And I did run scripts/setdevenv.sh before running the test.
>
> />which gdalinfo//
> ///scratch/gdal/gdal/gdal/apps/gdal
Even,
scripts/setdevenv.sh did fix the python problem for me.
However, I get a very similar segfault in the test scripts that I get on the
Mac. It seems related to SQLite and SpatiaLite. I'm going to try to rebuild
with an older set of GDAL+libs that has worked in the past.
Here is the backtra
In my case, this didn't work.
1. When I ran the GDAL build, I always use "make clean" to clean the old
build. And I did run scripts/setdevenv.sh before running the test.
/>which gdalinfo//
///scratch/gdal/gdal/gdal/apps/gdalinfo//
/
/>gdalinfo --version//
//GDAL 2.5.0dev-94f370c-dirty, relea
That's it. I didn't expect gdal to already be installed. I should have used a
different distro for this.
John Daniel
Etresoft, Inc.
> On Apr 18, 2019, at 5:17 AM, Even Rouault wrote:
>
>> E ImportError:
>> /home/parallels/OS-GIS/platforms/linux/x86_64/gdal/lib/python2.7/site-packa
>> ges/osg
> E ImportError:
> /home/parallels/OS-GIS/platforms/linux/x86_64/gdal/lib/python2.7/site-packa
> ges/osgeo/_gdal.so: undefined symbol: CPLGetErrorCounter
Try
ldd
/home/parallels/OS-GIS/platforms/linux/x86_64/gdal/lib/python2.7/site-packages/osgeo/_gdal.so
and check which libgdal.so it links t
Sorry for the duplicate message. I'm not sure what e-mail account I had used
for this list.
I am seeing something very similar. Judging from your /scratch/SDK paths, it
looks like you have a similar setup to what I am attempting.
Primarily I am trying to build on the Mac. I can run tests on th
I did run scripts/setdevenv.sh and the path looks correct.
ogrinfo runs ok too:
bash-4.2$ ogrinfo
Usage: ogrinfo [--help-general] [-ro] [-q] [-where
restricted_where|@filename]
[-spat xmin ymin xmax ymax] [-geomfield field] [-fid fid]
[-sql statement|@filename] [-
On Tue, 9 Apr 2019, Fengting Chen wrote:
gdalinfo and gdal_translate are working fine. just pytest failed with the
same error.
Here is my configure:
./configure --prefix=${PREFIX} \
--without-libtool \
--disable-rpath \
--with-libz=internal \
--with-png=internal \
--with-libtiff=int
gdalinfo and gdal_translate are working fine. just pytest failed with
the same error.
Here is my configure:
./configure --prefix=${PREFIX} \
--without-libtool \
--disable-rpath \
--with-libz=internal \
--with-png=internal \
--with-libtiff=internal \
--with-geotiff=internal \
--wit
On lundi 8 avril 2019 17:20:45 CEST Fengting Chen wrote:
> I rebuilt GDAl with python bindings without errors. Now I got a
> different error:
>
> ImportError while loading conftest
> '/scratch/gdal/gdal/autotest/conftest.py'.
> /home/fechen/.local/lib/python2.7/site-packages/six.py:709: in exec_
>
I rebuilt GDAl with python bindings without errors. Now I got a
different error:
ImportError while loading conftest
'/scratch/gdal/gdal/autotest/conftest.py'.
/home/fechen/.local/lib/python2.7/site-packages/six.py:709: in exec_
exec("""exec _code_ in _globs_, _locs_""")
conftest.py:9: in
Fengting,
2 things to check:
- first that the python bindings have been built. Did you ./configure --with-
python ? Or alternatively "cd swig/python && make"
- and that the Python buindings are in the PYTHONPATH. Sourcing scripts/
setdevenv.sh will do it
Even
> Hi,
>
> I followed the descriptio
Hi,
I followed the description in CONTRIUBTING.md on running autotest suite:
/cd ../autotest//
//pip install -r requirements.txt//
//pytest/
At the last step, pytest gave the following error:
/ImportError while loading conftest
'/scratch/gdal/gdal/autotest/conftest.py'.//
///home/fechen/.loc
19 matches
Mail list logo
