My windows build fails to run fxc.exe

195 views
Skip to first unread message

oshima

unread,
Apr 26, 2013, 5:45:33 PM4/26/13
to chromium-dev
# from the right account this time..

Hi,

I'm getting "Application Erorr: The application was unable to start correctly (0xc0000022)...."
when windows build try to run fxc.exe.

It's been several months since I did win build last time, and I probably missed an important PSA about windows
build, but I couldn't find how to fix it. Any help would be appreciated.

Thanks,
- oshima

Scott Graham

unread,
Apr 26, 2013, 5:55:35 PM4/26/13
to oshima, chromium-dev
asvitkine@ & wolentz@ tracked down something that sounds like this. I
have no idea what the cause is, but it'd be great to actually debug
it.

wolentz: """
The hlsl target issue is uncorrellated to cygwin/cmd shell choice - it
happens on both.
Work-around is to copy third_party\platformsdk_win8 to another drive,
delete the original, and copy it back (all with Windows Explorer).
asvitkine@ isn't sure why this works, but he's suggested it and
unblocked multiple others in the past.
The issue manifests as a popup (when building from cmd shell) showing
fxc failed to start; no popup in cygwin but the same result of build
failure.
I'm pending a bug # from asvitkine@ ATM.
> --
> --
> Chromium Developers mailing list: chromi...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-dev
>
>
>

Dale Curtis

unread,
Apr 26, 2013, 6:10:04 PM4/26/13
to Scott Graham, ni...@chromium.org, oshima, chromium-dev
+nick who I believe knows more about this.

- dale

oshima

unread,
Apr 26, 2013, 6:37:56 PM4/26/13
to Scott Graham, chromium-dev
Copying did the trick, how funny. Anyway, thank you!


On Fri, Apr 26, 2013 at 2:55 PM, Scott Graham <sco...@chromium.org> wrote:

Nick Carter

unread,
Apr 26, 2013, 7:08:27 PM4/26/13
to osh...@chromium.org, Scott Graham, chromium-dev
It's https://code.google.com/p/chromium/issues/detail?id=181633, and still not well understood. For whatever reason, on many developer's machines that file refuses to execute, with STATUS_ACCESS_DENIED. I wonder if we should touch or rename the problematic binary just in case it helps. Please contact me directly if anyone encounters this problem in the future; I'd like to lick it for good, but without a checkout in the bad state, we're just guessing in the dark.

 - nick

Reply all
Reply to author
Forward
0 new messages