Mehdi Asgari

@BatchDrake Well I've pulled everything today, so I am using the latest. So I fixed that error as well with some dirty hacks. So here are the changes I've made...

@smdjeff I will submit a PR, but it needs some pre-requisites: 1- I should test the software to make sure none of my changes actually affect runtime and are OK...

@smdjeff Sure. I cloned fresh repos on another MacBook and observed some differences when compiling; I should investigate those. For example in the first MacBook I didn't change any INCLUDE...

@BatchDrake Please ignore my comment on pan-adapter. Enabling Hardware AGC fixed it

@BatchDrake Ok so the first error showed itself and it's related to pthread. The only thing I know that I have changed in this laptop since 2 days ago is...

@BatchDrake I rebuilt everything with those flags. I've pasted the output of debugger at the end of this comment (it's the output of `bt all` from `lldb`) I found out...

@BatchDrake I renamed the folder and it worked again!! Please find attached my ~./suscan. By the way I found a weird issue you may find interesting: I tried to rebuild...

I tried anything that I could think of, but I can't figure out why the same exact linker command results in different behaviours on these 2 systems.

You're right. There's a difference between `libtestutil.a` in 2 systems. Here's the output of `otool -L` on them: First system (working): `Archive : testutil/.libs/libtestutil.a` **`testutil/.libs/libtestutil.a(libtestutil_la-common.o):`** `testutil/.libs/libtestutil.a(libtestutil_la-poolhelper.o):` `testutil/.libs/libtestutil.a(libtestutil_la-sigbufpool.o):` Second system (linker...

Thanks. Much better now (IMHO)