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

i686 build failure #19

Closed
antonio-rojas opened this issue Sep 1, 2016 · 3 comments
Closed

i686 build failure #19

antonio-rojas opened this issue Sep 1, 2016 · 3 comments

Comments

@antonio-rojas
Copy link
Contributor

antonio-rojas commented Sep 1, 2016

0.5.0 doesn't build on 32 bits with gdc:

appstream-generator ~master: building configuration "application"...

source/utils.d:373:13: error: function std.net.curl.HTTP.Protocol!().onReceive (uint delegate(ubyte[]) callback) is not callable using argument types (void)
             downloader.onReceive = (data) => onReceiveCb (dest, data);
             ^
source/utils.d:379:13: error: function std.net.curl.FTP.Protocol!().onReceive (uint delegate(ubyte[]) callback) is not callable using argument types (void)
             downloader.onReceive = (data) => onReceiveCb (dest, data);
             ^
gdc failed with exit code 1.
make: *** [Makefile:3: all] Error 2
@ximion
Copy link
Owner

ximion commented Sep 1, 2016

Yes, I see this on Debian too and even with 3c0bdb9 applied the last few issues don't get fixed.

They are also complete nonsense in my opinion, and I wonder whether this is actually a compiler bug.
Can you try building with LDC and see if that exhibits the same behavior?

@antonio-rojas
Copy link
Contributor Author

Same error with gdc, dmd and ldc.

@ximion
Copy link
Owner

ximion commented Sep 1, 2016

Okay, then it's likely real - question is why does it works on amd64, and what does this error message want to tell us?
onReceive is called using a delegate, not void, so this should be fine. I'll check this out when I arrived in Berlin, probably need to ping the D community about this, because I am rather clueless here (or simply not seeing the obvious bug).

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