You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Moving to a newer gcc has identified an existing bug. We saw the same thing over in phosphor-user-manager in openbmc/phosphor-user-manager#10.
This code as-is is not doing any locking so to make forward progress I'm going to put up a commit to just comment it out (so we can get upstream yocto in) and then someone can use this issue to renable it using {} and verify any needed test cases.
| ../../git/user_channel/passwd_mgr.cpp: In member function 'void ipmi::PasswdMgr::initPasswordMap()':
| ../../git/user_channel/passwd_mgr.cpp:230:38: error: empty parentheses were disambiguated as a function declaration [-Werror=vexing-parse]
| 230 | phosphor::user::shadow::Lock lock();
| | ^~
| ../../git/user_channel/passwd_mgr.cpp:230:38: note: remove parentheses to default-initialize a variable
| 230 | phosphor::user::shadow::Lock lock();
| | ^~
| | --
| ../../git/user_channel/passwd_mgr.cpp:230:38: note: or replace parentheses with braces to value-initialize a variable
| ../../git/user_channel/passwd_mgr.cpp: In member function 'int ipmi::PasswdMgr::updatePasswdSpecialFile(const string&, const string&)':
| ../../git/user_channel/passwd_mgr.cpp:360:38: error: empty parentheses were disambiguated as a function declaration [-Werror=vexing-parse]
| 360 | phosphor::user::shadow::Lock lock();
| | ^~
| ../../git/user_channel/passwd_mgr.cpp:360:38: note: remove parentheses to default-initialize a variable
| 360 | phosphor::user::shadow::Lock lock();
| | ^~
| | --
The text was updated successfully, but these errors were encountered:
This code as-is is not doing anything other then declaring a function.
The solution is to utilize {} to tell the compiler it's an object
instantiation. Given that this code has been a noop up until this point,
it's best to just comment it out until someone can come in enable and
test it properly.
The latest yocto update which brings in a newer compiler is erroring out
on this so we need something quick to be able to make progress there.
#170 is tracking this issue.
Signed-off-by: Andrew Geissler <[email protected]>
Change-Id: Idd4acd8e8541195f1b6e73c854866281832f1878
Moving to a newer gcc has identified an existing bug. We saw the same thing over in phosphor-user-manager in openbmc/phosphor-user-manager#10.
This code as-is is not doing any locking so to make forward progress I'm going to put up a commit to just comment it out (so we can get upstream yocto in) and then someone can use this issue to renable it using {} and verify any needed test cases.
The text was updated successfully, but these errors were encountered: