Running duckling binary on ARM based architecture (NVIDIA Xavier, Linux) - unknown RTS option: -N

Dear Facebook Team,

I have the following problem when trying to run the successfully built duckling binary on ARM based architecture on SD Card of NVIDIA Xavier, Ubuntu 18.04, Stack version 1.5.1 aarch64:
```
stack build
stack exec duckling-example-exe
```

I get the following output:

```
duckling-example-exe: unknown RTS option: -N
duckling-example-exe:
duckling-example-exe: Usage: [+RTS | -RTS ] ... --RTS
duckling-example-exe:
duckling-example-exe: +RTS Indicates run time system options follow
duckling-example-exe: -RTS Indicates program arguments follow
duckling-example-exe: --RTS Indicates that ALL subsequent arguments will be given to the
duckling-example-exe: program (including any of these RTS flags)
duckling-example-exe:
duckling-example-exe: The following run time system options are available:
duckling-example-exe:
duckling-example-exe: -? Prints this message and exits; the program is not executed
duckling-example-exe: --info Print information about the RTS used by this program
duckling-example-exe:
duckling-example-exe: -K Sets the maximum stack size (default: 80% of the heap)
duckling-example-exe: Egs: -K32k -K512k -K8M
duckling-example-exe: -ki Sets the initial thread stack size (default 1k) Egs: -ki4k -ki2m
duckling-example-exe: -kc Sets the stack chunk size (default 32k)
duckling-example-exe: -kb Sets the stack chunk buffer size (default 1k)
duckling-example-exe:
duckling-example-exe: -A Sets the minimum allocation area size (default 512k) Egs: -A1m -A10k
duckling-example-exe: -n Allocation area chunk size (0 = disabled, default: 0)
duckling-example-exe: -O Sets the minimum size of the old generation (default 1M)
duckling-example-exe: -M Sets the maximum heap size (default unlimited) Egs: -M256k -M1G
duckling-example-exe: -H Sets the minimum heap size (default 0M) Egs: -H24m -H1G
duckling-example-exe: -xb Sets the address from which a suitable start for the heap memory
duckling-example-exe: will be searched from. This is useful if the default address
duckling-example-exe: clashes with some third-party library.
duckling-example-exe: -m Minimum % of heap which must be available (default 3%)
duckling-example-exe: -G Number of generations (default: 2)
duckling-example-exe: -c Use in-place compaction instead of copying in the oldest generation
duckling-example-exe: when live data is at least % of the maximum heap size set with
duckling-example-exe: -M (default: 30%)
duckling-example-exe: -c Use in-place compaction for all oldest generation collections
duckling-example-exe: (the default is to use copying)
duckling-example-exe: -w Use mark-region for the oldest generation (experimental)
duckling-example-exe: -I Perform full GC after idle time (default: 0.3, 0 == off)
duckling-example-exe:
duckling-example-exe: -T Collect GC statistics (useful for in-program statistics access)
duckling-example-exe: -t[] One-line GC statistics (if omitted, uses stderr)
duckling-example-exe: -s[] Summary GC statistics (if omitted, uses stderr)
duckling-example-exe: -S[] Detailed GC statistics (if omitted, uses stderr)
duckling-example-exe:
duckling-example-exe:
duckling-example-exe: -Z Don't squeeze out update frames on stack overflow
duckling-example-exe: -B Sound the bell at the start of each garbage collection
duckling-example-exe:
duckling-example-exe: -h Heap residency profile (output file .hp)
duckling-example-exe: -i Time between heap profile samples (seconds, default: 0.1)
duckling-example-exe:
duckling-example-exe: -C Context-switch interval in seconds.
duckling-example-exe: 0 or no argument means switch as often as possible.
duckling-example-exe: Default: 0.02 sec.
duckling-example-exe: -V Master tick interval in seconds (0 == disable timer).
duckling-example-exe: This sets the resolution for -C and the heap profile timer -i,
duckling-example-exe: and is the frequence of time profile samples.
duckling-example-exe: Default: 0.01 sec.
duckling-example-exe:
duckling-example-exe: --install-signal-handlers=
duckling-example-exe: Install signal handlers (default: yes)
duckling-example-exe: -e Maximum number of outstanding local sparks (default: 4096)
duckling-example-exe: -xq The allocation limit given to a thread after it receives
duckling-example-exe: an AllocationLimitExceeded exception. (default: 100k)
duckling-example-exe:
duckling-example-exe: RTS options may also be specified using the GHCRTS environment variable.
duckling-example-exe:
duckling-example-exe: Other RTS options may be available for programs compiled a different way.
duckling-example-exe: The GHC User's Guide has full details.
duckling-example-exe:
```
I get the same output, when using newer version of stack (2.1.1), the lines inside duckling folder are:

`./stack-2.1.1-linux-aarch64/stack build ../`

and then:

`./stack-2.1.1-linux-aarch64/stack exec duckling-example-exe`

What am I doing wrong?

Many thanks in advance.

Best regards,
Ilia