"div0" <div0@users.sourceforge.net> wrote in message news:hshfe9$o06$1@digitalmars.com...
>
> Strange what OPTLINK is doing; normally it crashes at the drop of a hat, so it seems unreasonable that it processes the .obj a bit then (un)successfully exits. Maybe the .obj is corrupt in some way that makes it look empty, so it does nothing.
>
> Walter did post about converting it to C, did he finish that in the end?
>

When he talked about it, it sounded to me like a slow long-term project. So I'm sure he's still in the middle of it.

"Daniel Keep" <daniel.keep.lists@gmail.com> wrote in message news:hse30q$1tnt$1@digitalmars.com...
>
> That's right, it's time for everyone's favourite [1] game: guess why OPTLINK's not working! [2]
>
> *sigh*  I'm writing a math eval library.  There are two test applications.  LexerTest only touches part of the code.  AstTest touches everything.
>
> Now, the following works and creates an executable:
>
> dmd -ofLexerTest (appropriate .d files)
>
> So far, so good.  I get LexerTest.map, LexerTest.obj and LexerTest.exe. Let's try the other one...
>
> dmd -ofAstTest (more .d files)
>
> This creates a legitimate-looking AstTest.obj and a completely empty AstTest.map file.
>
> That's it.
>
> No executable, no error message, no register dump, nothing.
>
> Adding or removing -g, -debug, -unittest, -release, -inline, -O does nothing.  Changing the target filename does nothing useful.
>
> There are no spurious link.exe or dmd.exe processes running.  Invoking OPTLINK directly changes nothing.
>
> Does anyone have any idea, any idea at all, on what could be causing this?  I've tried everything myself and several others on #d could think of.
>
> *miserable sob*
>
> After over five years of this sort of shit, I am so, so completely and utterly sick to death of OPTLINK.
>
>
>
> [1] I am, of course, being sarcastic.
>
> [2] It is, of course, entirely possible that it's not OPTLINK's fault. Frankly though, I find that hard to believe.


Disclaimer: There's probably a good chance that I'm completely off-base here....

Did you try deleting all the object files before trying to compile AstTest? I've often had linker problems (although in my case, they were always linker errors, not silence) when compiling two different targets that share code (or two configurations of the same target) without clearing the object files in-between. (Because of that, I've been in the habit of always setting up my builds so that each target/configuration combination has it's own separate directory for object files.)

On 13.05.2010 21:07, torhu wrote:
> On 13.05.2010 10:39, Daniel Keep wrote:
>> Attached both regular and decaffeinated^Hgutted versions.
>
> Most likely DMD turns VisitorCtfe.d into an invalid object file. But
> since you don't need to link with objects that contain only ctfe
> functions...

http://d.puremagic.com/issues/show_bug.cgi?id=4315

On 15.06.2010 01:34, torhu wrote:
> On 13.05.2010 21:07, torhu wrote:
>> On 13.05.2010 10:39, Daniel Keep wrote:
>>> Attached both regular and decaffeinated^Hgutted versions.
>>
>> Most likely DMD turns VisitorCtfe.d into an invalid object file.
>> But since you don't need to link with objects that contain only
>> ctfe functions...
>
> http://d.puremagic.com/issues/show_bug.cgi?id=4315

Linker bug is http://d.puremagic.com/issues/show_bug.cgi?id=4324