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.

Sign up for GitHub

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

Jump to bottom

_D2ae5utils4sini link error #37

Open
MartinNowak opened this issue May 30, 2016 · 5 comments
Open

_D2ae5utils4sini link error #37

MartinNowak opened this issue May 30, 2016 · 5 comments

Comments

@MartinNowak
Copy link
Contributor

MartinNowak commented May 30, 2016 •
edited
Loading

Just build the latest version (ff1be21) and got the following linker error with dmd 2.070.2 and 2.071.0.

OPTLINK (R) for Win32  Release 8.00.17

Undefined _D2ae5utils4sini63__T14makeIniHandlerTAyaTS▒▒▒3sys1d7manager8DM▒▒▒3DMD6ConfigZ▒▒▒FNaNbNfK▒▒▒▒▒▒▒▒▒30▒▒▒20▒▒▒Traver▒▒▒g▒▒▒Z▒▒▒
@CyberShadow
Copy link
Owner

It's this bug: https://issues.dlang.org/show_bug.cgi?id=15985

Workaround: build with -debug

@CyberShadow CyberShadow mentioned this issue May 30, 2016
Closed
@Cauterite Cauterite mentioned this issue Aug 26, 2016
Closed
@CyberShadow CyberShadow mentioned this issue Sep 9, 2016
Closed
@CyberShadow CyberShadow mentioned this issue Sep 29, 2016
Closed
@timotheecour
Copy link

timotheecour commented Sep 29, 2016 •
edited
Loading

not just windows: OSX also
please update docs until this is fixed?
(ie, link to this bug below rdmd --build-only digger)

@CyberShadow CyberShadow changed the title Build error on Windows Link error on Windows and OSX Sep 29, 2016
@CyberShadow CyberShadow changed the title Link error on Windows and OSX _D2ae5utils4sini link error Sep 30, 2016
@wilzbach
Copy link

wilzbach commented Oct 7, 2016

not just windows: OSX also

I can reproduce it on Linux x86_64 with 2.071.2 & 2.072.0 too.

@wilzbach wilzbach mentioned this issue Oct 7, 2016
Merged
@CyberShadow CyberShadow mentioned this issue Jun 7, 2017
Closed
@CyberShadow CyberShadow mentioned this issue Jul 12, 2017
Closed
@CyberShadow CyberShadow mentioned this issue Feb 24, 2018
Closed
@CyberShadow CyberShadow mentioned this issue Mar 4, 2018
Closed
@Bolpat Bolpat mentioned this issue May 17, 2018
Closed
@wilzbach
Copy link

FYI @CyberShadow I see that you updated the install instructions to -allinst.
At least on my machine this results in a linker error too and only -debug works.

CyberShadow added a commit that referenced this issue Jun 19, 2018
@CyberShadow
README: Add -debug back...
536bd32 
#37 (comment)
@CyberShadow
Copy link
Owner

Thanks, added -debug back. Sigh...

CyberShadow added a commit to CyberShadow/ae that referenced this issue Dec 15, 2019
@CyberShadow
ae.utils.main: Catch GetOptException even in debug builds
179adca 
Don't show stack traces for usage errors in debug builds,
as non-technical users find them unsightly.

Debug builds are produced by default by Dub and
sometimes are needed to work around compiler bugs
(e.g. CyberShadow/Digger#37).

Hopefully the try/catch clause does not affect debugability of
applications; otherwise, this change will be reverted.

Partially fixes CyberShadow/Digger#81.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@CyberShadow @MartinNowak @timotheecour @wilzbach