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

[ldmd2] DUB puts .o in the current directory which breaks the build #634

Closed
p0nce opened this issue Jul 31, 2015 · 5 comments
Closed

[ldmd2] DUB puts .o in the current directory which breaks the build #634

p0nce opened this issue Jul 31, 2015 · 5 comments

Comments

@p0nce
Copy link
Contributor

p0nce commented Jul 31, 2015

DUB file:
https://github.com/p0nce/dplug/blob/master/examples/distort/dub.json

DUB version:
v0.9.23 (didn't test in more recent)

OS:
Mac OS X 10.10

Compiler:
ldc2-0.15.2-beta2-osx-x86_64

Command-line used:
dub build --build=debug --arch=x86 --compiler=ldmd2 --force

Result:
All .o files get created in the current directory. This brings conflicts.

Error: Output file 'package.o' for module 'ae.utils.meta' collides with previous module 'ae.utils.graphics'. See the -oq option
@p0nce
Copy link
Contributor Author

p0nce commented Jul 31, 2015

Still happen in DUB version 0.9.24-rc.2+7-g35a0cca

@p0nce p0nce changed the title DUB puts .o in the current directory DUB puts .o in the current directory which breaks the build Jul 31, 2015
@p0nce
Copy link
Contributor Author

p0nce commented Aug 12, 2015

Work-arounded by using --compiler=ldc2 instead.

@yazd
Copy link

yazd commented Sep 17, 2015

I faced this problem on linux with 0.16.0-alpha3 as well.

@p0nce p0nce changed the title DUB puts .o in the current directory which breaks the build [ldmd2 + Mac] DUB puts .o in the current directory which breaks the build Sep 26, 2015
@p0nce p0nce changed the title [ldmd2 + Mac] DUB puts .o in the current directory which breaks the build [ldmd2] DUB puts .o in the current directory which breaks the build Sep 26, 2015
@WebFreak001
Copy link
Member

reproduction test case doesn't work since a while anymore, didn't see anyone open a similar issue in a while, will just close.

It's recommended to use ldc instead of ldmd anyway, and might just be an ldmd bug if it only happens with it.

@p0nce
Copy link
Contributor Author

p0nce commented Feb 18, 2023

Absolutely agree

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

3 participants