Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build fails on linux debian x86 dmd 2.068 #6

Open
dschoerk opened this issue Aug 26, 2015 · 4 comments
Open

build fails on linux debian x86 dmd 2.068 #6

dschoerk opened this issue Aug 26, 2015 · 4 comments

Comments

@dschoerk
Copy link

Building msgpack-rpc 0.1.1 configuration "default", build type debug.
Running dmd...
../../home/vagrant/.dub/packages/msgpack-rpc-0.1.1/src/msgpackrpc/transport/tcp. d(64): Error: cannot implicitly convert expression (size) of type ulong to uint
../../home/vagrant/.dub/packages/msgpack-rpc-0.1.1/src/msgpackrpc/transport/tcp. d(129): Error: cannot implicitly convert expression (input.leastSize()) of type ulong to uint
../../home/vagrant/.dub/packages/msgpack-rpc-0.1.1/src/msgpackrpc/transport/tcp. d(148): Error: template instance msgpackrpc.transport.tcp.ClientSocket!(Client!( tcp)) error instantiating
../../home/vagrant/.dub/packages/msgpack-rpc-0.1.1/src/msgpackrpc/client.d(24): instantiated from here: ClientTransport!(Client!(tcp))
../../home/vagrant/.dub/packages/msgpack-rpc-0.1.1/src/msgpackrpc/client.d(92): instantiated from here: Client!(tcp)
FAIL ../../home/vagrant/.dub/packages/msgpack-rpc-0.1.1/.dub/build/default-debug -linux.posix-x86-dmd_2068-FDBACD6DA71A93D6D4082B2F537CD7A0/ msgpack-rpc staticLi brary
Error executing command run:
dmd failed with exit code 1.

@repeatedly
Copy link
Contributor

Do you use 32bit OS?

@dschoerk
Copy link
Author

not a 32bit OS, but a 32bit build on a 64bit OS
i'd need it for a plugin for a 32bit application

@repeatedly
Copy link
Contributor

I see. msgpack-rpc-d creates new array with size.
I assumesize_t but vibe.d uses ulong so it causes type mismatch.

repeatedly added a commit that referenced this issue Sep 23, 2015
@repeatedly
Copy link
Contributor

Could you try #7 patch on your environment?

repeatedly added a commit that referenced this issue Oct 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants