stan/jdk-24
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

8335880: More troubleshooting tips around windows space in path

Browse Source 
Reviewed-by: erikj, ihse
This commit is contained in:
Chen Liang 2024-10-26 14:45:19 +00:00
parent 40e07a7ea3
commit 762a573ef1
2 changed files with 23 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/building.html
View File

@ -2016,10 +2016,18 @@ some directory names have spaces. Usually, it assumes those directories
have <a have <a
href="https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/fsutil-8dot3name">short href="https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/fsutil-8dot3name">short
paths</a>. You can run <code>fsutil file setshortname</code> in paths</a>. You can run <code>fsutil file setshortname</code> in
<code>cmd</code> on certain directories, such as <code>cmd</code> on directories to assign arbitrary short paths so
<code>Microsoft Visual Studio</code> or <code>Windows Kits</code>, to <code>configure</code> can access them. If the result says "Access
assign arbitrary short paths so <code>configure</code> can access denied", it may be that there are processes running in that directory;
them.</p> in this case, you can reboot Windows in safe mode and run the command on
those directories again.</p>
<p>The only directories required to have short paths are
<code>Microsoft Visual Studio</code> and <code>Windows Kits</code>; the
rest of the "contains space" warnings from <code>configure</code>, such
as <code>IntelliJ IDEA</code>, can be ignored. You can choose any short
name; once it is set, <code>configure</code>'s tools like
<code>cygpath</code> can convert the directory with spaces to your
chosen short name and pass it to the build system.</p>
<h3 id="getting-help">Getting Help</h3> <h3 id="getting-help">Getting Help</h3>
<p>If none of the suggestions in this document helps you, or if you find <p>If none of the suggestions in this document helps you, or if you find
what you believe is a bug in the build system, please contact the Build what you believe is a bug in the build system, please contact the Build

14
doc/building.md
View File

@ -1800,9 +1800,17 @@ temporarily.
On Windows, when configuring, `fixpath.sh` may report that some directory names On Windows, when configuring, `fixpath.sh` may report that some directory names
have spaces. Usually, it assumes those directories have [short have spaces. Usually, it assumes those directories have [short
paths](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/fsutil-8dot3name). paths](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/fsutil-8dot3name).
You can run `fsutil file setshortname` in `cmd` on certain directories, such as You can run `fsutil file setshortname` in `cmd` on directories to assign
`Microsoft Visual Studio` or `Windows Kits`, to assign arbitrary short paths so arbitrary short paths so `configure` can access them. If the result says "Access
`configure` can access them. denied", it may be that there are processes running in that directory; in this
case, you can reboot Windows in safe mode and run the command on those directories
again.
The only directories required to have short paths are `Microsoft Visual Studio`
and `Windows Kits`; the rest of the "contains space" warnings from `configure`,
such as `IntelliJ IDEA`, can be ignored. You can choose any short name; once it
is set, `configure`'s tools like `cygpath` can convert the directory with spaces
to your chosen short name and pass it to the build system.
### Getting Help ### Getting Help