First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 30160
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Peter Johanson (RETIRED) <latexer@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Alberto Ornaghi <alor@antifork.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 30160 depends on: Show dependency tree
Show dependency graph
Bug 30160 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2003-10-02 07:00 0000 
>>> emerge (1 of 1) net-wireless/kismet-3.0.1 to /
>>> md5 src_uri ;-) kismet-3.0.1.tar.gz
>>> Unpacking source...
>>> Unpacking kismet-3.0.1.tar.gz to /var/tmp/portage/kismet-3.0.1/work
>>> Source unpacked.
 * Running autoconf-2.57 to fix libpcap borkage
/usr/sbin/ebuild.sh: line 39: autoconf-2.57: command not found

!!! ERROR: net-wireless/kismet-3.0.1 failed.
!!! Function src_compile, Line 39, Exitcode 127
!!! Failed to run autoconf-2.57


I have autoconf-2.57a  so it is not found... ;)

bye

Reproducible: Always
Steps to Reproduce:
1.export ACCEPT_KEYWORDS="~x86"
2.emerge autoconf
3.emerge kismet

------- Comment #1 From Robin Johnson 2003-10-12 17:27:59 0000 ------- 
fixed in CVS because I wanted to install kismet myself :-).
First Last Prev Next    No search results available      Search page      Enter new bug