Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2176991 | 7 | Erik Trimble | P3 | Closed | Fixed | b17 |
JDK-2172457 | 6u10 | Abhijit Saha | P3 | Closed | Fixed | b09 |
###@###.### wrote:
I bringover'ed the latest Hotspot WS and found one more issue while building it with VS2005:
In the src/os/win32/vm/os_win32.cpp file on line 989 (the os::get_current_directory() function) the getcwd() function is used. However, according to the latest ISO C++ standard (well, as cl.exe says, at least) it is necessary to use _getcwd() instead of the plain getcwd() function. This, of course, generates just a warning, but warnings are considered to be fatal in case of Hotspot building, and therefore it causes the whole build to fail. I would encourage somebody from Hotspot team to fix this problem (though, I guess it's necessary to test such a change using VS2003 of course, I've no idea whether it will work with our current compiler).
I bringover'ed the latest Hotspot WS and found one more issue while building it with VS2005:
In the src/os/win32/vm/os_win32.cpp file on line 989 (the os::get_current_directory() function) the getcwd() function is used. However, according to the latest ISO C++ standard (well, as cl.exe says, at least) it is necessary to use _getcwd() instead of the plain getcwd() function. This, of course, generates just a warning, but warnings are considered to be fatal in case of Hotspot building, and therefore it causes the whole build to fail. I would encourage somebody from Hotspot team to fix this problem (though, I guess it's necessary to test such a change using VS2003 of course, I've no idea whether it will work with our current compiler).
- backported by
-
JDK-2172457 Hotspot Windows build fails in VS2005 due to getcwd/_getcwd POSIX name change
- Closed
-
JDK-2176991 Hotspot Windows build fails in VS2005 due to getcwd/_getcwd POSIX name change
- Closed