Kismet Wireless

Kismet Forums


Posted by:dragorn
Subject:Startup segfault on Sabayon 4
Date:14:47:28 14/07/2009

> So, after doing the build and test on SUSE 11.1 AMD-64 KDE (which worked perfectly!), I thought that maybe I could substitute SUSE's libuClibc++ for the one in Sabayon. Big surprise -- SUSE does not include this lib. A check of the kismet config.log confirmed that it looked for the lib and did not find it, so it linked around it and built anyway.

ulibcs is for embedded platforms. Kismet MAY use it, by no means SHOULD or MUST use it.

> The only reason I had had libuClibc++ in my Sabayon system was that emerge picked it up when I installed the Sabayon stock kismet binary, or so it would appear. It does not come in by default. To prove this, I wiped the box (again!) and installed Sab 4.2, and then immediately loaded the kismet source tarball and ran a fresh build. Config had no complaints, and the linker commands showed no mention of libuClibc++; rather they had libstdc++, which is OK.

Looks like they don't understand what uclibc is. No-one should ever be dual-packaging uclibc and libc on a system, there's zero point to having both, and bad stuff will happen. Whoever made the sabayon package has no idea what they're doing.

> And the resulting kismet binary works. :-P
> So I am now going to report this back to Sabayon. I did not see any other apps with a dependence on this library -- only kismet, which apparently links and runs just fine without it.

Definitely - uclibc is an alternate embedded libc implementation and has no business being dual-installed on a full system, and is by no means required by Kismet.


Reply to this message