On Monday, 3 February 2020 at 22:08:50 UTC, Vladimir Panteleev
wrote:
On Monday, 3 February 2020 at 22:01:18 UTC, Anonymouse wrote:
No, C:\Temp\work\dl\git does not exist. :o
OK, that makes sense.
Please try the latest Digger version
(24cd4168956dad382d05984b4b8d37d9e8ebe3ae).
Works
On Monday, 3 February 2020 at 22:01:18 UTC, Anonymouse wrote:
No, C:\Temp\work\dl\git does not exist. :o
OK, that makes sense.
Please try the latest Digger version
(24cd4168956dad382d05984b4b8d37d9e8ebe3ae).
On Monday, 3 February 2020 at 21:58:31 UTC, Vladimir Panteleev
wrote:
On Monday, 3 February 2020 at 21:44:20 UTC, Anonymouse wrote:
New log: https://pastebin.com/raw/uUMNQjEN
It looks like it fails to execute git (to get the current
version for the build).
I don't know why that fails, as I
On Monday, 3 February 2020 at 21:44:20 UTC, Anonymouse wrote:
New log: https://pastebin.com/raw/uUMNQjEN
It looks like it fails to execute git (to get the current version
for the build).
I don't know why that fails, as I see C:\Temp\work\dl\git\cmd is
in PATH in the environment that
On Monday, 3 February 2020 at 21:33:09 UTC, Vladimir Panteleev
wrote:
On Monday, 3 February 2020 at 21:30:57 UTC, Anonymouse wrote:
I was on beta 8. I forced dub to download the latest now
(3.0.0-alpha-9), wiped the work directory and retried, but to
similar results.
The latest is
On Monday, 3 February 2020 at 21:30:57 UTC, Anonymouse wrote:
I was on beta 8. I forced dub to download the latest now
(3.0.0-alpha-9), wiped the work directory and retried, but to
similar results.
The latest is v3.0.0-alpha-11.
Oh, I guess that's not how semantic versioning works. Probably
On Monday, 3 February 2020 at 20:54:46 UTC, Vladimir Panteleev
wrote:
On Monday, 3 February 2020 at 20:41:00 UTC, Anonymouse wrote:
It doesn't seem to include debugging symbols.
Is your Digger version up-to-date?
On Monday, 3 February 2020 at 20:41:00 UTC, Anonymouse wrote:
It doesn't seem to include debugging symbols. Does digger not
build its dmds with -g?
The exceptions happens inside of build.d not dmd which wasn't
built with debug informations until recently.
Here's the full log:
On Monday, 3 February 2020 at 20:41:00 UTC, Anonymouse wrote:
It doesn't seem to include debugging symbols.
Is your Digger version up-to-date?
https://github.com/CyberShadow/ae/commit/48ee31a3b0d47e52769ee87b0e673034abe4add5
On Monday, 3 February 2020 at 20:09:43 UTC, MoonlightSentinel
wrote:
On Monday, 3 February 2020 at 16:54:20 UTC, Anonymouse wrote:
It does a `dmd.exe -of..\generated\build.exe`, but then the
immediately following call to `..\generated\build.exe` fails?
What am I doing wrong?
The executable
On Monday, 3 February 2020 at 16:54:20 UTC, Anonymouse wrote:
It does a `dmd.exe -of..\generated\build.exe`, but then the
immediately following call to `..\generated\build.exe` fails?
What am I doing wrong?
The executable was launched because make would yield a different
error message
I'm trying to bisect a dmd compilation error on Windows 10 and I
can't get digger to do more than one initial test. When preparing
to compile the next dmd build (the BAD revision) it errors out.
This is in a normal cmd console.
The bisect ini has nothing weird in it:
```
bad = v2.088.1
good
12 matches
Mail list logo