From: Steven Susbauer <stupendoussteve@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] BUG? - bridge-utils no binary?
Date: Tue, 09 Aug 2005 07:30:43 -0700 [thread overview]
Message-ID: <42F8BE13.7090301@gmail.com> (raw)
In-Reply-To: <42F8BC51.2030203@mailshack.com>
Check the emerge logs and see what files were copied where (the part
where it's like /usr/bin/brctl - or whatever). It may be that the
command is slightly different with this version. *shrugs*
Ognjen Bezanov wrote:
> Hello
>
> I am building a linux AP using a clean installation of gentoo and this
> howto:
>
> http://gentoo-wiki.com/HOWTO_Building_a_Wireless_Access_Point_With_Gentoo
>
> Everything was going great until I came to emerging bridge-utils.
>
> the actual emerging didnt fail (using "emerge bridge-utils -av") but
> typing the command brctl it tells me '-bash: brctl: command not found'
>
> next I try "whereis brctl", resulting in:
>
> brctl: /usr/man/man8/brctl.8.gz /usr/share/man/man8/brctl.8.gz
>
> ok, so the man files are there, it seems the package was installed. but
> no binary.
>
> Using "find / -name brctl" i also got nothing.
>
> It seems that there is no binary, I have tried emerging again,
> unmerging, updating and the like, still the same problem. The emerge
> itself doesnt fail with the usual "Error..." so I presume thats fine (or
> am i wrong that
> emerge would halt on all errors?)
>
> Any help appreciated as I am somewhat at a loss as to whats going on.
>
> thanks
>
>
--
This site uses frames
And yet your browser does not.
One of these will change.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-09 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 14:23 [gentoo-user] BUG? - bridge-utils no binary? Ognjen Bezanov
2005-08-09 14:30 ` Steven Susbauer [this message]
2005-08-09 20:04 ` Rumen Yotov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42F8BE13.7090301@gmail.com \
--to=stupendoussteve@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox