-
Notifications
You must be signed in to change notification settings - Fork 28
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
libgcc-s-dev should include crtbegin/crtend/libgcc binaries #62
Comments
Nicely spotted, thanks for the report. I'll take a look. I tried to make use of existing .inc's in the core where possible, but the external toolchain sysroot extraction requires more explicit specification than the core recipes do. I'm assuming this is against current master? |
It's against release/2014.12. Using that branch for now. I'll recheck with the master branch tomorrow. |
Created SB-4841, if that matters |
Okay, that's good to know. The recipes were completely reworked in master to use separate recipes for each upstream recipe (e.g. libgcc-external is its own recipe) with an entirely different mechanism for the file extraction from the external toolchain sysroot. Regardless, fixing this should just be a matter of adding a few entries to the FILES variable in question in the external-sourcery-toolchain recipe. |
Good to know. This should give us more flexibility. Unfortuntately ATM I'm stuck with release 2014.12. Regarding FILES_* variables. Not quite. To be as compatible as possible I'm also installing files to a gcc-specific folders, not to /usr/lib. On the other hand just putting everything to /usr/lib should also work. I'll give it a try. |
@kergoth Installing these files to /usr/lib has serious drawback --- they will go now to libc6-dev package instead of libgcc-dev. I'll do few more tests. |
@kergoth just FYI. I ended up with the following snippet:
|
libgcc-s-dev generated by external-sourcery-toolchain should include more binaries. Compare:
Original libgcc-s-dev from OE:
libgcc-s-dev from meta-sourcery:
Noticed by @vsitdikov .
The text was updated successfully, but these errors were encountered: