Skip to content

GCC Windows export does not build as of #6577 #7112

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

Closed
cmonr opened this issue Jun 5, 2018 · 3 comments
Closed

GCC Windows export does not build as of #6577 #7112

cmonr opened this issue Jun 5, 2018 · 3 comments

Comments

@cmonr
Copy link
Contributor

cmonr commented Jun 5, 2018

Description

When attempting to build an exported GCC project, the Makefile generated is now so large that the link step fails to link all files because the command is too long to be run successfully (all files are linked in one command).

Mbed CLI and Pip are at their latest versions. Issue is independent of Python versions and the target specified.

Steps to reproduce

git clone https://github.com/ARMmbed/mbed-os-example-blinky blinky
cd blinky
git clone https://github.com/ARMmbed/mbed-os

# Will pass
cd mbed-os
git checkout 53aa1b0
cd ..

mbed export --ide GCC_ARM --m K22F --clean -vv
make

# Will fail
cd mbed-os
git checkout 5038135
cd ..

mbed export --ide GCC_ARM --m K22F --clean -vv
make

Files

Attached are the generated makefiles for mbed-os-5.8.0, and the two Mbed OS SHAs in question.
Makefile-5.8.5.txt
Makefile-53aa1b0.txt
Makefile-5038135.txt

Issue request type

[ ] Question
[ ] Enhancement
[x] Bug

@ciarmcom
Copy link
Member

ciarmcom commented Jun 5, 2018

ARM Internal Ref: MBOTRIAGE-415

@SeppoTakalo
Copy link
Contributor

Duplicate of:

@cmonr
Copy link
Contributor Author

cmonr commented Jun 5, 2018

Closing due to duplicate issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants