Re: GDC generate wrong .exe ("not a valid win32 application")

2017-06-23 Thread PATRIC DEXHEIMER via Digitalmars-d-learn

On Wednesday, 21 June 2017 at 15:55:27 UTC, David Nadlinger wrote:

On Monday, 19 June 2017 at 14:08:56 UTC, Patric Dexheimer wrote:

Fresh install of GDC. (tried with 32x ad 32_64x)


Where did you get the GDC executable from? The GDC project 
doesn't currently offer any official builds that target 
Windows; the 6.3.0 builds from https://gdcproject.org/downloads 
in fact generate Linux binaries.


 — David


Oh, ops.

I looked at the title "x86_64-w64-mingw32" not at the (target) 
x86_64-linux-gnu.

Thanks :)




Re: GDC generate wrong .exe ("not a valid win32 application")

2017-06-22 Thread Sebastien Alaiwan via Digitalmars-d-learn

On Thursday, 22 June 2017 at 05:57:59 UTC, bauss wrote:
On Wednesday, 21 June 2017 at 15:55:27 UTC, David Nadlinger 
wrote:
On Monday, 19 June 2017 at 14:08:56 UTC, Patric Dexheimer 
wrote:

Fresh install of GDC. (tried with 32x ad 32_64x)


Where did you get the GDC executable from? The GDC project 
doesn't currently offer any official builds that target 
Windows; the 6.3.0 builds from 
https://gdcproject.org/downloads in fact generate Linux 
binaries.


 — David


I see Windows distributions below the Linux ones.


They run on Windows, and produce binaries that run on GNU/Linux.


Re: GDC generate wrong .exe ("not a valid win32 application")

2017-06-22 Thread cym13 via Digitalmars-d-learn

On Thursday, 22 June 2017 at 05:57:59 UTC, bauss wrote:
On Wednesday, 21 June 2017 at 15:55:27 UTC, David Nadlinger 
wrote:
On Monday, 19 June 2017 at 14:08:56 UTC, Patric Dexheimer 
wrote:

Fresh install of GDC. (tried with 32x ad 32_64x)


Where did you get the GDC executable from? The GDC project 
doesn't currently offer any official builds that target 
Windows; the 6.3.0 builds from 
https://gdcproject.org/downloads in fact generate Linux 
binaries.


 — David


I see Windows distributions below the Linux ones.


They're used for cross-compiling.


Re: GDC generate wrong .exe ("not a valid win32 application")

2017-06-22 Thread bauss via Digitalmars-d-learn

On Wednesday, 21 June 2017 at 15:55:27 UTC, David Nadlinger wrote:

On Monday, 19 June 2017 at 14:08:56 UTC, Patric Dexheimer wrote:

Fresh install of GDC. (tried with 32x ad 32_64x)


Where did you get the GDC executable from? The GDC project 
doesn't currently offer any official builds that target 
Windows; the 6.3.0 builds from https://gdcproject.org/downloads 
in fact generate Linux binaries.


 — David


I see Windows distributions below the Linux ones.


Re: GDC generate wrong .exe ("not a valid win32 application")

2017-06-21 Thread David Nadlinger via Digitalmars-d-learn

On Monday, 19 June 2017 at 14:08:56 UTC, Patric Dexheimer wrote:

Fresh install of GDC. (tried with 32x ad 32_64x)


Where did you get the GDC executable from? The GDC project 
doesn't currently offer any official builds that target Windows; 
the 6.3.0 builds from https://gdcproject.org/downloads in fact 
generate Linux binaries.


 — David



Re: GDC generate wrong .exe ("not a valid win32 application")

2017-06-19 Thread Patric Dexheimer via Digitalmars-d-learn

On Monday, 19 June 2017 at 23:55:54 UTC, rjframe wrote:

On Mon, 19 Jun 2017 14:08:56 +, Patric Dexheimer wrote:


Fresh install of GDC. (tried with 32x ad 32_64x)

GDC: 6.3.0 DUB: 1.3.0

dub run --build=release --arch=x86 --compiler=gdc

(...)
Running .\main Failed to spawn new process (%1 is not a valid 
win32

application)


If you try compiling a single file directly (gdc app.d -o app), 
does it work?


If it does, what's the output of `dub run -v ...`?


Same problem compiling directly.

dub verbose output:

C:\Users\User\Desktop\d_test>dub run --build=debug --arch=x86 
--compiler=gdc -v

Using dub registry url 'http://code.dlang.org/'
Refreshing local packages (refresh existing: true)...
Looking for local package map at 
C:\ProgramData\dub\packages\local-packages.json
Looking for local package map at 
C:\Users\User\AppData\Roaming\dub\packages\local-packages.json
Note: Failed to determine version of package d_test at .. 
Assuming ~master.

Refreshing local packages (refresh existing: false)...
Looking for local package map at 
C:\ProgramData\dub\packages\local-packages.json
Looking for local package map at 
C:\Users\User\AppData\Roaming\dub\packages\local-packages.json

Refreshing local packages (refresh existing: false)...
Looking for local package map at 
C:\ProgramData\dub\packages\local-packages.json
Looking for local package map at 
C:\Users\User\AppData\Roaming\dub\packages\local-packages.json

Checking for upgrades.
Using cached upgrade results...
Generating using build
Generate target d_test (executable C:\Users\User\Desktop\d_test 
d_test)

Performing "debug" build using gdc for x86.
d_test ~master: target for configuration "application" is up to 
date.
Using existing build in 
C:\Users\User\Desktop\d_test\.dub\build\application-debug-linux.posix-x86-gdc_2068-413C114DFC17AD06F727410485B0042A\.
Copying target from 
C:\Users\User\Desktop\d_test\.dub\build\application-debug-linux.posix-x86-gdc_2068-413C114DFC17AD06F727410485B0042A\d_test to C:\Users\User\Desktop\d_test

To force a rebuild of up-to-date targets, run again with --force.
Running .\d_test
Failed to spawn new process (%1 n├úo ├® um aplicativo Win32 
válido.)


Re: GDC generate wrong .exe ("not a valid win32 application")

2017-06-19 Thread rjframe via Digitalmars-d-learn
On Mon, 19 Jun 2017 14:08:56 +, Patric Dexheimer wrote:

> Fresh install of GDC. (tried with 32x ad 32_64x)
> 
> GDC: 6.3.0 DUB: 1.3.0
> 
> dub run --build=release --arch=x86 --compiler=gdc
> 
> (...)
> Running .\main Failed to spawn new process (%1 is not a valid win32
> application)

If you try compiling a single file directly (gdc app.d -o app), does it 
work?

If it does, what's the output of `dub run -v ...`?


GDC generate wrong .exe ("not a valid win32 application")

2017-06-19 Thread Patric Dexheimer via Digitalmars-d-learn

Fresh install of GDC. (tried with 32x ad 32_64x)

GDC: 6.3.0
DUB: 1.3.0

dub run --build=release --arch=x86 --compiler=gdc

(...)
Running .\main
Failed to spawn new process (%1 is not a valid win32 application)