Bug#957665: Fortran issue solved but symbols issues (Was: Bug#957665: Fortran issue in paw (Was: paw: ftbfs with GCC-10))

2020-10-18 Thread Étienne Mollier
Hi Andreas, Andreas Tille, on 2020-10-17 21:52:24 +0200: > /usr/bin/ld: > paw/cdf/shared/mlpdef.o:/build/paw-2.14.04.dfsg.2/build/pawlib/paw/cdf/mlpdef.c:155: > multiple definition of `klnkaddr'; > paw/cdf/shared/pawcdf.o:/build/paw-2.14.04.dfsg.2/build/pawlib/paw/cdf/pawcdf.c:155: > first

Bug#957665: Fortran issue solved but symbols issues (Was: Bug#957665: Fortran issue in paw (Was: paw: ftbfs with GCC-10))

2020-10-17 Thread Andreas Tille
Hi Andrius On Thu, Oct 15, 2020 at 03:34:15PM +0300, Andrius Merkys wrote: > > FFLAGS += -fallow-argument-mismatch Thanks a lot for the helpful hint which enabled me to do one step forward[1]. Unfortunately there are further errors: ... /usr/bin/ld:

Bug#957665: Fortran issue in paw (Was: paw: ftbfs with GCC-10)

2020-10-15 Thread Andrius Merkys
Hi Andreas, On 2020-10-15 15:26, Andreas Tille wrote: > when trying to build paw with gcc / fortran 10 there are some FORTRAN > errors: > > > ... > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (COMPLEX(4)/INTEGER(4)). >

Bug#957665: Fortran issue in paw (Was: paw: ftbfs with GCC-10)

2020-10-15 Thread Andreas Tille
Control: tags -1 help Hi, when trying to build paw with gcc / fortran 10 there are some FORTRAN errors: ... Error: Type mismatch between actual argument at (1) and actual argument at (2) (COMPLEX(4)/INTEGER(4)). /<>/src/pawlib/comis/code/cs1200.F:138:24: 76 | CALL