-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It would be nice to be able to build with clang rather than gcc #126
Comments
What version/branch did you build? Is this CFE 6.7 (official) or CFE 6.8 (main)? There were a number of alignment fixes that went into the last release cycle. I would expect this error on CFE 6.7, but not in CFE 6.8. |
I just did
So I guess I am on master? |
Also note - if your target architecture does not have strict alignment requirements (e.g. x86) you can also remove |
Perfect, I will try that. Thanks. |
I took a closer look at this one -- this is actually for the So yes -- this is still an isssue in 6.8, but it will be fixed by nasa/cFE#651 |
Getting close!
I also had to futz with arch_build_custom.cmake and for some strange reason add a newline at the end of |
These functions should be part of Does clang support the |
and
|
Followed by
|
Finally
does not complain. |
Thanks a lot for your help @jphickey |
OK -- this explains it, as the current code only puts in the Looks like you swapped the order - which is fine - but be advised there could be other other symbols which are not referenced at all in either CFE nor PSP - but should still be linked into the final EXE so they'd be available for apps. That was the reason for using There is also an existing issue nasa/cFE#722 to implement this in a better way that doesn't depend on toolchain-specific feature. |
Thanks. Actually I am using using gllvm so I can get all the llvm bitcode associated with the build, so the |
See also nasa/cFE#2204 |
I added a target file called target-llvm.cmake for clang and clang++ (from llvm 10), the relevant lines being:
But alas after
followed by
I get
The text was updated successfully, but these errors were encountered: