New issue
Advanced search Search tips

Issue 721569 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jun 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

clang++ is complaining about -Wno-psabi using emerge

Project Member Reported by ahass...@chromium.org, May 11 2017

Issue description

I have some code that runs on server (not client devices) that needs to be compiled with emerge (not emerge-$BOARD). Now it is failing and complaining about flag -Wno-psabi which clang doesn't recognize. My workflow is broken :(

The flag seems to be in platform2/common/
 
Labels: Build-Toolchain

Comment 2 by vapier@chromium.org, May 11 2017

Owner: cmt...@chromium.org

Comment 3 by cmt...@chromium.org, May 12 2017

We recently changed the host compiler in ChromeOS from GCC to LLVM/Clang, and apparently that is the root cause of your issue.  If you could tell me what package you are building, I can set things up for your package to build with GCC at the moment.  I am working on another CL that, when it goes in, should allow your package to build with clang.
My package is not in the repo yet. It is in platform/puffin which is empty now. I can temporary build everything with emerge-$BOARD, but that is not the intended purpose. Is there anyway I can set it up myself? How long does it take for you new CL to go in?

Thanks,

Comment 5 by cmt...@chromium.org, May 12 2017

In /etc/make.conf.host_setup, the very last two lines of the file define CC & CXX to be clang & clang++.  If you comment out those lines and then redo your setup_board, that should revert the default compiler to GCC for you.

Comment 6 by cmt...@chromium.org, May 12 2017

Umm...I just tried what I suggested.  I think you need to edit the file and NOT do the setup_board.  Sorry.
Yes, it works now. Thank you for your help.
Status: Fixed (was: Untriaged)
It took a little longer than I expected but my CLs to 'really' fix this issue have all been committed now, so your workaround should not be needed any more.  I am going to mark this as fixed.

Comment 9 by cmt...@chromium.org, Sep 25 2017

Status: Verified (was: Fixed)

Sign in to add a comment