Skip to content
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

Strip AVR32 libraries to fix Hudson problem #21

Open
kblomqvist opened this issue May 8, 2013 · 2 comments
Open

Strip AVR32 libraries to fix Hudson problem #21

kblomqvist opened this issue May 8, 2013 · 2 comments

Comments

@kblomqvist
Copy link
Contributor

What's this all about?
http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&t=113202

This can be fixed by calling avr32-strip from Makefile. I have also made a python script to fix this:
https://gist.github.com/kblomqvist/4100575#file-fixhudson-py

@jsnyder
Copy link
Owner

jsnyder commented May 9, 2013

It seems like it should be fairly trivial to add the fix to the makefile. The only reason I'd not just pull in the Python script is that it's not currently on the dependency list.

I see the suggestion to use the find command on that forum, although I'd want to check that that works for both gnu and bsd variants of that tool.

Does this just crop up during debugging? I'm busy with quite a bit of other stuff at the moment and I'm more actively developing on ARM platforms at the moment until I finish up a dissertation :-)

@kblomqvist
Copy link
Contributor Author

It seems like it should be fairly trivial to add the fix to the makefile. The only reason I'd not just pull in the Python script is that it's not currently on the dependency list.

Yep, it should be integrated into Makefile. It wasn't even in my intention to use the Python script to fix this (that was only an example).

Does this just crop up during debugging?

Yes.

I'm busy with quite a bit of other stuff at the moment and I'm more actively developing on ARM platforms at the moment until I finish up a dissertation :-)

That's all fine :) I was planning to fix this issue by myself. Opening the issue was more like a note for me.

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

No branches or pull requests

2 participants