[gdal-dev] building gdal with python and libtool

[Andrew C Aitchison]

On Mon, 27 Jun 2016, Kai Mühlbauer wrote:

> Hi all,
>
> while trying to build gdal on linux (on CircleCi in a CentOS based docker 
> image using conda/conda-forge) like this:

> /bin/bash -pthread -shared -L/home/sam/miniconda3/envs/_build/lib 
> -Wl,-rpath=/home/sam/miniconda3/envs/_build/lib,--no-as-needed 
> -L/home/sam/miniconda3/envs/_build/lib -L/home/sam/miniconda3/envs/_build/lib 
> -m64 -Wall -Wdeclaration-after-statement -Wextra -Winit-self 
> -Wunused-parameter -Wmissing-prototypes -Wmissing-declarations -Wformat 
> -Werror=format-security -Wno-format-nonliteral -Wlogical-op -Wshadow 
> -Werror=vla -Wdeclaration-after-statement -DOGR_ENABLED 
> -I/home/sam/miniconda3/envs/_build/include 
> -I/home/sam/miniconda3/conda-bld/work/gdal-2.1.0/port 
> -I/home/sam/miniconda3/envs/_build/include 
> -I/home/sam/miniconda3/envs/_build/include -I/home/sam/miniconda3/envs/_build 
> -I/home/sam/miniconda3/envs/_build/include 
> -I/home/sam/miniconda3/envs/_build/include -I/home/sam/miniconda3/envs/_build 
> -I/home/sam/miniconda3/envs/_build/include -I/home/sam/miniconda3/envs/_build 
> -I/home/sam/miniconda3/envs/_build/include -DGDAL_COMPILATION 
> build/temp.linux-x86_64-3.4/extensions/gdal_wrap.o -L../../.libs -L../../ 
> -L/home/sam/miniconda3/envs/_build/lib 
> -L/home/sam/miniconda3/conda-bld/work/gdal-2.1.0/lib -lpython3.4m -lgdal -o 
> build/lib.linux-x86_64-3.4/osgeo/_gdal.cpython-34m.so
> /bin/bash: -d: invalid option
> error: command '/bin/bash' failed with exit status 1
> make[2]: *** [build] Error 1
> make[2]: Leaving directory 
> `/home/sam/miniconda3/conda-bld/work/gdal-2.1.0/swig/python'
> make[1]: *** [build] Error 2
> make[1]: Leaving directory 
> `/home/sam/miniconda3/conda-bld/work/gdal-2.1.0/swig'

I'm surprised to see python3.4 on a CentOS system;
I'd be very suprised if it is the default python (as
opposed to an additional python from SCL).
If I'm right, I'd guess python34 needs extra environment variables,
perhaps set with something like "scl python34 ..."

But, I'm not sure how that would make bash fail like that.