#3469: i.atcorr: Sentinel-2 support broken on some systems
--------------------------+-------------------------
Reporter: sbl | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.4.0
Component: Packaging | Version: unspecified
Resolution: | Keywords: i.atcorr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by mlennert):
Replying to [comment:6 mmetz]:
> Replying to [comment:5 mlennert]:
> > Using
> >
> >
> > {{{
> > CFLAGS=-g -Wall -Wextra -Wpedantic -Wshadow -Wno-sign-compare -fno-
common -fexceptions -Werror=implicit-function-declaration
-Wp,-D_FORTIFY_SOURCE=2 -O3 -fno-fast-math
> > }}}
>
> Are you still using
>
> {{{
> CXXFLAGS="-g -Ofast"
> }}}
> ?
No. I left all ldflags and cxxflags commented, and I don't think -Ofast is
default.
>
> i.atcorr is a C++ module
Good to know. So do CFLAGS have any impact ?
>
> >
> > I again get
> >
> >
> > {{{
> > r.info -r test_atcorr
> > min=NULL
> > max=NULL
> > }}}
> >
> > So not sure it's the compiler flags...
>
> I can confirm on Debian testing, all NULL...
Good. This means that it is something systematic which we should be able
to find. Stefan, you tried different versions. Are there any older
versions which work for you ?
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3469#comment:7>
GRASS GIS <https://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-dev
