stdlib-fpm branch fails to build on Apple M1

[certik]

Description

(gf) fortran-lang/stdlib(stdlib-fpm) $ fpm build
 + mkdir -p build/dependencies
Initialized empty Git repository in /Users/certik/repos/fortran-lang/stdlib/build/dependencies/test-drive/.git/
remote: Enumerating objects: 31, done.
remote: Counting objects: 100% (31/31), done.
remote: Compressing objects: 100% (29/29), done.
remote: Total 31 (delta 5), reused 13 (delta 0), pack-reused 0
Unpacking objects: 100% (31/31), 31.07 KiB | 1.00 MiB/s, done.
From https://github.com/fortran-lang/test-drive
 * branch            HEAD       -> FETCH_HEAD
 + mkdir -p build/gfortran_2A42023B310FA28D
 + mkdir -p build/gfortran_2A42023B310FA28D/stdlib/
 + gfortran -c ././src/stdlib_system.F90  -Wall -Wextra -Wimplicit-interface -fPIC -fmax-errors=1 -g -fcheck=bounds -fcheck=array-temps -fbacktrace -fcoarray=single -J build/gfortran_2A42023B310FA28D -Ibuild/gfortran_2A42023B310FA28D -o build/gfortran_2A42023B310FA28D/stdlib/src_stdlib_system.F90.o
././src/stdlib_system.F90:31:16:

   31 | subroutine sleep(millisec)
      |                1
Warning: ‘sleep’ declared at (1) may shadow the intrinsic of the same name.  In order to call the intrinsic, explicit INTRINSIC declarations may be required. [-Wintrinsic-shadow]
 + gfortran -c ././src/stdlib_kinds.f90  -Wall -Wextra -Wimplicit-interface -fPIC -fmax-errors=1 -g -fcheck=bounds -fcheck=array-temps -fbacktrace -fcoarray=single -J build/gfortran_2A42023B310FA28D -Ibuild/gfortran_2A42023B310FA28D -o build/gfortran_2A42023B310FA28D/stdlib/src_stdlib_kinds.f90.o
 + gfortran -c build/dependencies/test-drive/src/testdrive.F90  -Wall -Wextra -Wimplicit-interface -fPIC -fmax-errors=1 -g -fcheck=bounds -fcheck=array-temps -fbacktrace -fcoarray=single -J build/gfortran_2A42023B310FA28D -Ibuild/gfortran_2A42023B310FA28D -o build/gfortran_2A42023B310FA28D/stdlib/build_dependencies_test-drive_src_testdrive.F90.o
build/dependencies/test-drive/src/testdrive.F90:898:12:

  898 |     real(qp), intent(in) :: actual
      |            1
Error: Kind -1 not supported for type REAL at (1)
compilation terminated due to -fmax-errors=1.
<ERROR> Compilation failed for object " build_dependencies_test-drive_src_testdrive.F90.o "
<ERROR>stopping due to failed compilation
STOP 1

Expected Behaviour

xxxxxxxxxxxxxxxxx

Version of stdlib

cc641dd

Platform and Architecture

MacOS/ARM

Additional Information

This form is so hard to fill out that I almost gave up on reporting this.

I would suggest to either get rid of it, or simplify this.

[zoziha]

May be the same as #527 .

[awvwgk]

Duplicate of #527

[awvwgk]

@certik Good bug reports are important to help maintainers figure out what the actual problem is. The bug report form is meant to guide reporters to provide at least the required information (compiler, platform, architecture, project version, commands used, logs) to not require the maintainers to chase after those bits. Taking the time to provide a detailed bug report is a good way to help a project improve.

If you think the form is not suitable for your report, there is also a free form template which doesn't impose any constraints on the provided input.