On Fri, 5 Apr 2019, Markus Neteler wrote:
On Mon, Apr 1, 2019 at 11:17 PM Andrew C Aitchison
<and...@aitchison.me.uk> wrote:
On Mon, 1 Apr 2019, Markus Neteler wrote:
Now I am stuck at
...
BUILD SUCCESSFUL
Total time: 10 seconds
+ popd
+ %mvn_artifact swig/java/build/maven/gdal-2.3.2.pom
swig/java/build/maven/gdal-2.3.2.jar
~/build/BUILD/gdal-2.3.2-fedora
/var/tmp/rpm-tmp.R4QpDm: line 139: fg: no job control
error: Bad exit status from /var/tmp/rpm-tmp.R4QpDm (%build)
....
That is probably a bug in the rpm .spec file
https://www.redhat.com/archives/rpm-list/2002-October/msg00271.html
suggests that it is a % character being passed to the shell.
Thanks Andrew,
I made further attempts but I am stuck.
Maybe the Python-3 support needs to be kicked out as well?
The current state is here
https://copr.fedorainfracloud.org/coprs/neteler/GDAL/build/876548/
- SPEC file:
https://copr-be.cloud.fedoraproject.org/results/neteler/GDAL/epel-7-x86_64/00876548-gdal/gdal.spec
- Log file:
https://copr-be.cloud.fedoraproject.org/results/neteler/GDAL/epel-7-x86_64/00876548-gdal/builder-live.log
Towards the end your log file has
+ pushd swig/python
~/build/BUILD/gdal-2.3.2-fedora
~/build/BUILD/gdal-2.3.2-fedora/swig/python
~/build/BUILD/gdal-2.3.2-fedora
+ %py3_build
/var/tmp/rpm-tmp.mcNaiW: line 136: fg: no job control
First, it might be useful to have /var/tmp/rpm-tmp.mcNaiW (or whatever
name this gets next time you build) as well as the log file.
Second, this means that your .spec calls
%py3_build
without first defining it:
552-# Make Python modules
553-pushd swig/python
554- %{?with_python2:%py2_build}
555: %{?with_python3:%py3_build}
556-popd
I only have RedHat/CentOS/SL 6, not 7 and
grep -r py3_build /usr/lib/rpm
shows nothing. Does py3_build exist in your rpm tree,
or is it part of COPR ?
--
Andrew C. Aitchison Cambridge, UK
and...@aitchison.me.uk
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
