Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 890022 - net-wireless/kismet-2022.08.1-r1 calls commands that do not exist: -I
Summary: net-wireless/kismet-2022.08.1-r1 calls commands that do not exist: -I
Status: RESOLVED DUPLICATE of bug 890020
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Rick Farina (Zero_Chaos)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-07 08:14 UTC by Agostino Sarubbo
Modified: 2023-02-22 17:18 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
build.log (build.log,80.18 KB, text/plain)
2023-01-07 08:14 UTC, Agostino Sarubbo 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2023-01-07 08:14:57 UTC 
https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: net-wireless/kismet-2022.08.1-r1 calls commands that do not exist.
Discovered on: amd64 (internal ref: dash_tinderbox)

NOTE:
(DASH-SYSTEM) in the summary means that the bug was found on a machine that runs /bin/sh as dash but this bug MAY or MAY NOT BE related to dash.
Please look for 'command not found' and/or 'no such file or directory'.
Comment 1 Agostino Sarubbo gentoo-dev 2023-01-07 08:14:59 UTC 
Created attachment 847768 [details]
build.log

build log and emerge --info
Comment 2 Agostino Sarubbo gentoo-dev 2023-01-07 08:15:00 UTC 
Error(s) that match a know pattern in addition to what has been reported in the summary:


/bin/sh: 1: -I: not found
-I: not found
kis_external.h:51:10: fatal error: protobuf_cpp/kismet.pb.h: No such file or directory
libnm (the NetworkManager control library) was not found (or it was disabled). 
kis_external.h:51:10: fatal error: protobuf_cpp/kismet.pb.h: No such file or directory
Comment 3 Rick Farina (Zero_Chaos) gentoo-dev 2023-02-22 17:18:23 UTC 

*** This bug has been marked as a duplicate of bug 890020 ***