On Sat, 14 Sep 2013 08:32:04 +0200 Rainer Schuetze <r.sagita...@gmx.de> wrote:
> > > On 13.09.2013 23:31, Nick Sabalausky wrote: > > On Tue, 3 Sep 2013 20:53:11 -0400 > > Nick Sabalausky <seewebsitetocontac...@semitwist.com> wrote: > >> > >> - Windows 7 (64-bit OS): This is where I'm having the biggest > >> trouble. I can coaxing it to handle v2.063.2 just fine (ie, if I > >> update the "tools" makefiles as described above, and comment out > >> all the "libcurl" and "chm" stuff.) However, on master, after it > >> compiles DMD/druntime/phobos, the resulting DMD/phobos can't > >> compile anything that uses phobos because OPTLINK will spew out a > >> bunch of errors. I am *completely* at a loss on this one. It seems > >> like an sc.ini issue, but I've spent days checking everything and > >> I still can't make heads or tails of it. > >> > > > > That issue is still blocking the release generator (seems to be the > > same issue at least one other person was already having): > > http://d.puremagic.com/issues/show_bug.cgi?id=10729 > > > > Can anyone who is able to build a *working* 32-bit DMD/phobos from > > master on Windows pop into that issue page and see what this does > > for them?: > > > > mkdir junk > > create_dmd_release master --extras=junk --only-32 -v > > > > The generated sc.ini in dmd/src is no good, the LIB environment > variable should be set like this: > > LIB="%@P%\..\..\phobos" > > Even if you do so, it does not work because optlink is also looking > for an sc.ini (contrary or in addition to the documentation that > mentions optlink.cfg) and extracts the LIB environment variable. If > the link.exe in the PATH is from a different version of dmd, the > wrong phobos.lib is taken. > > It is easiest to always put link.exe into the same directory as > dmd.exe. > Ahh, ok I had been wondering about all of that, and even toyed around with those changes, but I still couldn't get it to work. But by then, I had already been reduced to kinda tossing around theories semi-randomly, so maybe I still messed it up. I'll try again - at least this time I know ;) > While you are at it, I'd recommend an sc.ini that looks about like > this in the release: > [...] Thanks, I'll update it. > > 3 more nitpicks: > - the working directory defaultWorkDir is never created Really? Hmm: - Is it possible that might be a permissions issue? Since this isn't really an end-user tool, I didn't feel a need to make sure it worked with a limited user account. What temp directory is reported when you do "create_dmd_release --help"? - Are you using --use-clone=path? If so, then it won't create defaultWorkDir unless it needs to - although I might have missed something there, so I'll check into that. > - I get an error that '.' cannot be removed, but I can continue > answering 'n' to the following question for retry Ok now that seems bizarre. Can you post a log or screenshot of that? I have no idea what part of the process might be doing that - definitely something involving an external tool being invoked, because I didn't add any interactive prompts to it. You're not running it *from* the [your temp dir]/.create_dmd_release directory, are you? > - my copies of the Windows SDKs 6 and 7 don't have folders License, > Redist, Samples and Setup. I would just skip these tests. Ok.