search

kismetwireless / kismet

Github mirror of official Kismet repository
Other
1.58k stars 305 forks source link

Error during make (OS X Mojave) #90

Closed jvdoorn closed 5 years ago

jvdoorn commented 5 years ago

After doing ./configure (no errors as far as I can tell) I ran make which threw the following error:

Undefined symbols for architecture x86_64:
  "void boost_like::hash_combine<unsigned long>(XXHash32&, unsigned long const&)", referenced from:
      Kis_80211_Phy::HandleSSID(std::__1::shared_ptr<kis_tracked_device_base>, std::__1::shared_ptr<dot11_tracked_device>, kis_packet*, dot11_packinfo*, kis_gps_packinfo*) in phy_80211.cc.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [kismet] Error 1

I'm guessing a framework or library is missing, however, I'm unable to tell which one. My version of clang is the following in case it matters:

Apple LLVM version 10.0.0 (clang-1000.11.45.2)
Target: x86_64-apple-darwin18.0.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
kismetwireless commented 5 years ago

Make sure you've got the latest git pull and do a make distclean and reconfigure; I'd guess you've got a stale makefile; that code changed recently and moved to another file, so if you have a stale makefile it won't get linked and you'll get that error.

On Wed, Oct 24, 2018 at 4:36 AM Argetan notifications@github.com wrote:

After doing ./configure (no errors as far as I can tell) I ran make which threw the following error:

Undefined symbols for architecture x86_64: "void boost_like::hash_combine(XXHash32&, unsigned long const&)", referenced from: Kis_80211_Phy::HandleSSID(std::1::shared_ptr, std::1::shared_ptr, kis_packet, dot11_packinfo, kis_gps_packinfo*) in phy_80211.cc.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make: *** [kismet] Error 1

I'm guessing a framework or library is missing, however, I'm unable to tell which one. My version of clang is the following in case it matters:

Apple LLVM version 10.0.0 (clang-1000.11.45.2) Target: x86_64-apple-darwin18.0.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kismetwireless/kismet/issues/90, or mute the thread https://github.com/notifications/unsubscribe-auth/AVScYxaNGzXi48Arp1w-wf5ghTyX9V_tks5uoCaQgaJpZM4X3ZzJ .

jvdoorn commented 5 years ago

Created a fresh directory and cloned the master branch, ran ./configure again but the error remains.

kismetwireless commented 5 years ago

Unfortunately I don't have any other ideas right now, and I don't have access to any mojave systems; I've done a clean checkout on several other systems and that file is linking properly; I'll keep digging at it though.

On Wed, Oct 24, 2018 at 10:45 AM Argetan notifications@github.com wrote:

Created a fresh directory and cloned the master branch, ran ./configure again but the error remains.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kismetwireless/kismet/issues/90#issuecomment-432687437, or mute the thread https://github.com/notifications/unsubscribe-auth/AVScY1TNgW5K40ppowYeokl_2DOGTn7gks5uoH0GgaJpZM4X3ZzJ .

dragorn commented 5 years ago

i've thrown a few more headers into that file to try to make mojave happy, it appears to be a type mismatch with how it defines uint64_t; unfortunately that also causes a problem on other platforms if I change how uit64_t is handled. Digging into it more.

On Wed, Oct 24, 2018 at 11:23 AM Kismet Wireless notifications@github.com wrote:

Unfortunately I don't have any other ideas right now, and I don't have access to any mojave systems; I've done a clean checkout on several other systems and that file is linking properly; I'll keep digging at it though.

On Wed, Oct 24, 2018 at 10:45 AM Argetan notifications@github.com wrote:

Created a fresh directory and cloned the master branch, ran ./configure again but the error remains.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/kismetwireless/kismet/issues/90#issuecomment-432687437 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AVScY1TNgW5K40ppowYeokl_2DOGTn7gks5uoH0GgaJpZM4X3ZzJ

.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kismetwireless/kismet/issues/90#issuecomment-432702901, or mute the thread https://github.com/notifications/unsubscribe-auth/ADIHCFs5lWyWAIYsdFZdw3pEkqF5TaEFks5uoIXYgaJpZM4X3ZzJ .

jvdoorn commented 5 years ago

I just tried compiling on a Mac running Sierra and it threw the same error, could it be that both systems are missing a library/framework somewhere?

kismetwireless commented 5 years ago

Try the latest commit

On Wed, Oct 24, 2018 at 4:27 PM Argetan notifications@github.com wrote:

I just tried compiling on a Mac running Sierra and it threw the same error, could it be that both systems are missing a library/framework somewhere?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kismetwireless/kismet/issues/90#issuecomment-432815668, or mute the thread https://github.com/notifications/unsubscribe-auth/AVScY_SSASZK5n05poNhCrDrqiXh-8O0ks5uoM0jgaJpZM4X3ZzJ .

jvdoorn commented 5 years ago

It compiled successfully on both systems, thank you for the help!

thewifimaster commented 5 years ago

I get an error 'No package 'protobuf‘ found‘.

How did you install https://github.com/protocolbuffers/protobuf/releases to get it to work?

Am 25.10.2018 um 07:16 schrieb Argetan notifications@github.com:

It compiled successfully on both systems, thank you for the help!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

jvdoorn commented 5 years ago

I think I already had it installed but you should be able to install it using HomeBrew: brew install protobuf

thewifimaster commented 5 years ago

That is what I did and I still get the error. Can’t seem to figure it out as it must be in standard paths .. Any thoughts?

Am 25.10.2018 um 12:11 schrieb Argetan notifications@github.com:

I think I already had it installed but you should be able to install it using HomeBrew: brew install protobuf

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

jvdoorn commented 5 years ago

brew link protobuf perhaps? Might have to unlink it first but Brew will tell you in that case.

thewifimaster commented 5 years ago

No success with that. Any other ideas?

Am 25.10.2018 um 20:53 schrieb Argetan notifications@github.com:

brew link protobuf perhaps? Might have to unlink it first but Brew will tell you in that case.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

DaniloNC commented 5 years ago

@thewifimaster Try: brew install protobuf-c