Re: macOS Sierra Support

2017-01-10 Thread Peter Snyder
There were two things I needed to do to get GDB to work. You need the latest GDB (which it looks like you have) and then codesign the binary. Even though it refers to an older version of MacOS, I found the following instructions under 2.1 in this webpage helpful:

Re: macOS Sierra Support

2017-01-10 Thread Fabio Utzig
If no "brew cleanup" was run, you can always "brew switch" to another version. On Tue, Jan 10, 2017, at 04:00 PM, David G. Simmons wrote: > Oh, yeah, because then it updates your gcc toolchain, and then all hell > breaks loose. There is a way to back one update out. I think I documented > that

Re: macOS Sierra Support

2017-01-10 Thread Sterling Hughes
don’t do brew update/brew upgrade (or maybe use homebrew. :-) On 10 Jan 2017, at 9:53, David G. Simmons wrote: I'm running the latest Sierra without issue ... DSimmons-Pro:myproj dsimmons$ newt -v build air_q Building target targets/air_q Loading compiler

Re: macOS Sierra Support

2017-01-10 Thread David G. Simmons
I'm running the latest Sierra without issue ... DSimmons-Pro:myproj dsimmons$ newt -v build air_q Building target targets/air_q Loading compiler /Users/dsimmons/dev/myproj/repos/apache-mynewt-core/compiler/arm-none-eabi-m4, def debug Compiling src in base directory:

macOS Sierra Support

2017-01-10 Thread Sterling Hughes
Hi, On the latest develop with the latest macOS Sierra and homebrew, If I have a target: targets/slim_slinky app=apps/slinky bsp=hw/bsp/native build_profile=debug (used to be optimized :-) And I try and build: $ newt run slim_slinky Error: In file included from