[GRASS-user] grass72 or higher on RHEL6

[Vaclav Petras]

On Thu, Feb 2, 2017 at 4:16 PM, Markus Neteler <neteler at osgeo.org> wrote:
>
> Hi,
>
> in order to compile GRASS 7.2.0 on EPEL6 I have created backport patches
of
>
> https://trac.osgeo.org/grass/changeset/70235 (needed to be able to
> apply the next patch)
>
> https://trac.osgeo.org/grass/changeset/70476
>
> This reduces the errors on EPEL6 to:
>
> Errors in:
> /builddir/build/BUILD/grass-7.2.0/display/d.barscale
> /builddir/build/BUILD/grass-7.2.0/display/d.northarrow
> /builddir/build/BUILD/grass-7.2.0/display/d.vect
> /builddir/build/BUILD/grass-7.2.0/raster/r.colors
> /builddir/build/BUILD/grass-7.2.0/vector/v.colors
> /builddir/build/BUILD/grass-7.2.0/temporal/t.rast.colors
> /builddir/build/BUILD/grass-7.2.0/man
>
> Still the parser... (and one wx missing - perhaps that could be
> changed to lazy import?).
>
> The compile errors can be easily spotted by searching for "Error 1" in
the log:
>
https://copr-be.cloud.fedoraproject.org/results/neteler/grass72_epel6/epel-6-x86_64/00506696-grass/build.log.gz
>
> Markus

This looks like that the 2.6 HTMLParser is more picky about the HTML:

...barscale.html
/builddir/build/BUILD/grass-7.2.0/dist.x86_64-redhat-linux-gnu/docs/man/man1/d.barscale.1
Traceback (most recent call last):
  File
"/builddir/build/BUILD/grass-7.2.0/dist.x86_64-redhat-linux-gnu/tools/
g.html2man.py", line 71, in <module>
    main()
  File
"/builddir/build/BUILD/grass-7.2.0/dist.x86_64-redhat-linux-gnu/tools/
g.html2man.py", line 50, in main
    p.close()
  File "/usr/lib64/python2.6/HTMLParser.py", line 112, in close
    self.goahead(1)
  File "/usr/lib64/python2.6/HTMLParser.py", line 164, in goahead
    self.error("EOF in middle of construct")
  File "/usr/lib64/python2.6/HTMLParser.py", line 115, in error
    raise HTMLParseError(message, self.getpos())
HTMLParser.HTMLParseError: EOF in middle of construct, at line 54, column 8

The following one will be tricky to fix. It is already a workaround because
of some cross dependencies and all GUI depends on wx if not for other
reason it is because all depends on globalvar module which needs wx and
testing wx is its main purpose. It is a reasonable request not to require
wx for build, but if the case is just building in non-GUI requirement there
are two other options: make the process ignore all errors (not ideal) or
have a switch to build without GUI (that would be advantageous also for the
speed).

...python core/menutree.py "manager" >> menustrings.py
Traceback (most recent call last):
  File "core/menutree.py", line 44, in <module>
    import wx
ImportError: No module named wx
make[4]: Leaving directory `/builddir/build/BUILD/grass-7.2.0/gui/wxpython'
make[4]: *** [menustrings.py] Error 1

The last one is documentation related. argparse is available only in >2.7
and >3.2, needs some rewrite:

Traceback (most recent call last):
  File "./parser_standard_options.py", line 8, in <module>
    import argparse
ImportError: No module named argparse
make[3]: ***
[/builddir/build/BUILD/grass-7.2.0/dist.x86_64-redhat-linux-gnu/docs/html/parser_standard_options.html]
Error 1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20170202/5530f5ac/attachment.html>