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.

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

build the tests failed #10

Open
chaov opened this issue Feb 1, 2023 · 6 comments
Open

build the tests failed #10

chaov opened this issue Feb 1, 2023 · 6 comments

Comments

@chaov
Copy link

chaov commented Feb 1, 2023

image
When I try to build the tests, it prompt that "Incompatible with the version of Windows you are running. Please review your computer's system information and contact the software publisher"
Could you opensource the rps_hlslc?
Thank you.

@RaccoonOnRails
Copy link

Hi, could you please share the OS version info?

@FlorianHerickAMD
Copy link
Collaborator

If you provide us more information about your system like e.g. your OS we can try helping you. Otherwise we would close this issue soon.

@skyt301
Copy link

skyt301 commented May 5, 2023

I'm not the originator of this topic, but I still get the same error.
According to the event log, there seems to be a problem with the 64-bit emulation layer.

エディション	Windows 11 Pro
バージョン	22H2
インストール日	‎2022/‎09/‎22
OS ビルド	22621.1555
エクスペリエンス	Windows Feature Experience Pack 1000.22640.1000.0

ログの名前:         Application
ソース:           Wow64 Emulation Layer
日付:            2023/05/05 12:42:44
イベント ID:       1109
タスクのカテゴリ:      なし
レベル:           情報
キーワード:         クラシック
ユーザー:          N/A
コンピューター:       DESKTOP-2OKP2S6
説明:
64 ビット バージョンの Windows での非互換性のため、プログラムまたは機能である "\??\D:\Github\GPUOpen-LibrariesAndSDKs\RenderPipelineShaders-open-beta-1.1\tools\rps_hlslc\win-x64\rps-hlslc.exe" を開始または実行できません。ソフトウェア製造元に問い合わせて 64 ビット Windows 互換バージョンが利用可能であるかどうか確認してください。
イベント XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Wow64 Emulation Layer" />
    <EventID Qualifiers="16384">1109</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2023-05-05T03:42:44.6652129Z" />
    <EventRecordID>40168</EventRecordID>
    <Correlation />
    <Execution ProcessID="8916" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-2OKP2S6</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\??\D:\Github\GPUOpen-LibrariesAndSDKs\RenderPipelineShaders-open-beta-1.1\tools\rps_hlslc\win-x64\rps-hlslc.exe</Data>
  </EventData>
</Event>

@FlorianHerickAMD
Copy link
Collaborator

FlorianHerickAMD commented May 9, 2023

Are you trying to build for a 32-bit architecture? If so, can you try a build for a 64-bit one instead and let us know the results? The rps-hlslc.exe executable is a 64-bit binary so the fact that the emulation layer is used seems very likely to be the problem.

@skyt301
Copy link

skyt301 commented May 14, 2023

No, I'm trying to do an x64 build. (I'm using the build.bat batch file according to the README.md.)
Also, it's already "broken" (when you download it from Github Releases) even before you build it.
Please replace the EXE file or include the source code of the tool in your project.
image

@FlorianHerickAMD
Copy link
Collaborator

FlorianHerickAMD commented May 15, 2023

I tried reproducing this issue even on a Japanese Win 11 system as well and everything worked out of the box. This is why I have a hard time believing this is a general issue.

Also, the translated output of the error message in your initial post and the source of the WoW64 emulation layer strongly hint at the compiler binary (which is a 64-bit binary) being executed in a 32-bit environment. Could you try to use the windows process explorer to run the batch file and see if you can find any hints pointing at a reason for the emulation layer being active in the first place? Any 32-bit binaries being created or used, etc., look at the child processes spawned. Usually, the layer should only automatically be used when a 32-bit binary is executed on a 64-bit system. However, that should not be the case here.

We cannot publish the source code of the compiler at this moment but may revisit that decision at a later time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants