-
Notifications
You must be signed in to change notification settings - Fork 4
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
C++ headers not included #4
Comments
I suggest you contact Eric Smith. He's the one who moved us to GCC5. He may know how to merge in these other libraries. I taked it cstring is not part of the standard C++ library? |
We had explicitly disabled libstdc++ builds for GCC5. I think this was because it was also trying to build libgfortran (and failing). I've modified the Makefile to re-enable them, and to build only C and C++. It looks like libstdc++ is being built now, but it still isn't being installed. I'm not sure why this is -- I don't quite follow the logic of the install process. If one of you could take a look perhaps you'll see what's going on. |
Hi Eric. Thanks for working on the libstdc++ build for GCC5. When you say you don't understand the install logic, are you talking about the propeller-gcc Makefile? I can take a look at that if it's causing trouble. Also, do I need to update the submodules in the propeller-gcc project to pick up your changes to the libstdc++ library build? |
I don't understand both the propeller-gcc Makefile and the gcc libstdc++ Makefile. I'm no longer sure how things get put in /opt/parallax. It looks like they're first placed in a holding area and then copied later; I think this is done by propeller-gcc, but I'm not sure. My changes to enable the libstdc++ build are only in the propeller-gcc Makefile, so no need to update submodules. |
Can you push your changes to the Makefile when you get a chance and I'll look into why the library isn't being copied. Sorry if the propeller-gcc Makefile is hard to understand. I'm open to suggestions as to how to improve it. |
Sorry, I thought I had pushed it but I guess not... it's there now. I don't think the propeller-gcc Makefile is hard to understand, I'm just rusty and things have changed since I last looked at the installation procedure. It's not your fault, it's mine. The issue may be in the gcc Makefile or in the top level Makefile; I'm not sure. |
Thanks for pushing your changes. I'll try to figure out why the libstdc++ library isn't getting copied during "make install". Actually, as you pointed out, it probably isn't getting copied to the staging directory since "make install" doesn't do anything other than copy the staging directory to the target directory. |
I use headers such as
cstring
in PropWare, but these are not included in PropGCC GCCv5 yet.The text was updated successfully, but these errors were encountered: