This repository has been archived by the owner on Sep 20, 2023. It is now read-only.

ghci is broken by `capi` calling convention #442

Open

vincenthz opened this issue Nov 11, 2017 · 0 comments

Labels

B

Member

vincenthz commented Nov 11, 2017

Related to #420

Compiling Foundation.System.Bindings.Posix ( .stack-work/dist/x86_64-linux-tinfo6/Cabal-2.0.0.2/build/Foundation/System/Bindings/Posix.hs, interpreted )
Error: bytecode compiler can't handle some foreign calling conventions
  Workaround: use -fobject-code, or compile this module to .o separately.

Options:

remove capi in favor of ignoring the variadic function (since it's not used this way on most system)
jump through a C binding function
hide capi under an ifdef for system that are not BSD,Linux,OSX (using the real variadic api for system that could be using it, hence maximing portability)

The text was updated successfully, but these errors were encountered:

vincenthz added the B label

vincenthz changed the title ~~stack ghci is broken by capi calling convention~~ ghci is broken by capi calling convention

vincenthz mentioned this issue

Use memset and memcpy from ByteString to avoid issues with llvm-ng backend vincenthz/hs-memory#66

Closed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.