Error running make
nacnudus opened this issue · 5 comments
nacnudus commented
I'm looking forward to using this, but I get the following error when running the first step from the makefile.
$ mlton -show-def-use support/def-use-util.du -prefer-abs-paths true support/def-use-util.mlb
Warning: /home/nacnudus/.config/nvim/plugged/vim-better-sml/support/unused-defs.sml 19.11.
Declaration is not exhaustive.
missing pattern: (:: (_, (:: (_, (:: (_, nil))))))
| (:: (_, (:: (_, nil)))) | (:: (_, nil)) | nil
in: idType :: id :: filename :: linec ... ens Char.isSpace def
/usr/bin/ld: /usr/lib/mlton/targets/self/libmlton.a(platform.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/mlton/targets/self/libmlton.a(gc.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/mlton/targets/self/libmlton.a(bug.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/mlton/targets/self/libmlton.a(Stat.o): relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/mlton/targets/self/libmlton.a(util.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/mlton/targets/self/libmlton.a(linux.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/mlton/targets/self/libgdtoa.a(strtof.o): relocation R_X86_64_32 against `.data' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/mlton/targets/self/libgdtoa.a(strtodg.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/mlton/targets/self/libgdtoa.a(hexnan.o): relocation R_X86_64_32S against hidden symbol `hexdig_D2A' can not be used when making a shared object
/usr/bin/ld: /usr/lib/mlton/targets/self/libgdtoa.a(misc.o): relocation R_X86_64_32S against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: /usr/lib/mlton/targets/self/libgdtoa.a(gethex.o): relocation R_X86_64_32S against hidden symbol `hexdig_D2A' can not be used when making a shared object
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
call to system failed with exit status 1:
gcc -o support/def-use-util /tmp/file2d9bX5.o /tmp/fileYGneUE.o /tmp/fileR5nUKO.o -L/usr/lib/mlton/targets/self -lmlton -lgdtoa -lm -lgmp -m64 -Wl,-znoexecstack
make: *** [Makefile:6: support/def-use-util] Error 1
jez commented
Looks like that's just a warning. Does it also not work?
…On Fri, Aug 4, 2017 at 4:01 PM Duncan Garmonsway ***@***.***> wrote:
I'm looking forward to using this, but I get the following error when
running the first step from the makefile.
$ mlton -show-def-use support/def-use-util.du -prefer-abs-paths true support/def-use-util.mlb
Warning: /home/nacnudus/.config/nvim/plugged/vim-better-sml/support/unused-defs.sml 19.11.
Declaration is not exhaustive.
missing pattern: (:: (_, (:: (_, (:: (_, nil))))))
| (:: (_, (:: (_, nil)))) | (:: (_, nil)) | nil
in: idType :: id :: filename :: linec ... ens Char.isSpace def
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#8>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFSaVMACDj-CRi0GV8KaotMSBpYYsxQyks5sU6K0gaJpZM4OuRTV>
.
nacnudus commented
Yes, it also doesn't work. Sorry, I missed the rest of the output but have now pasted it in above.
jez commented
Does MLton normally work on your laptop? You could test this like so. Add to a file called "hello.sml":
print "hello\n"
Then run
mlton hello.sml
nacnudus commented
Ah. No, it doesn't. Sorry to have spammed you, I'll go and sort that out!
jez commented
No worries! Hope everything works out and you're able to play around with the plugin itself.
Good luck!