From: Larry Finger <Larry.Finger@lwfinger.net>
To: Xavier de Almeida <xavierdealmeida@yahoo.fr>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Tr : Tr : Can't make RTL8188CE work with hostapd (rtl8192ce)
Date: Tue, 24 Jul 2012 12:51:02 -0500 [thread overview]
Message-ID: <500EE086.6000304@lwfinger.net> (raw)
In-Reply-To: <1343149616.67668.YahooMailNeo@web28904.mail.ir2.yahoo.com>
On 07/24/2012 12:06 PM, Xavier de Almeida wrote:
> Hi Larry and the team,
>
> couldn't install my compiled (make + checkinstall) package.
>
> sudo dpkg -i compat-wireless-2012-07_03-1_i386.deb
> (Reading database ... 214923 files and directories currently installed.)
> Unpacking compat-wireless-2012-07 (from compat-wireless-2012-07_03-1_i386.deb) ...
> dpkg: error processing compat-wireless-2012-07_03-1_i386.deb (--install):
> trying to overwrite '/bin/ntfs-3g', which is also in package ntfs-3g 1:2012.1.15AR.1-1ubuntu1
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> Errors were encountered while processing:
> compat-wireless-2012-07_03-1_i386.deb
>
> Should I just to a make install instead?
Yes. Using "make" and "sudo make install" is the correct way. Building a .deb.
may be necessary to install a whole kernel (it is not on my distro), but not for
compat-wireless.
Larry
next prev parent reply other threads:[~2012-07-24 17:51 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKjQTCesBzbjbv4T+RPRutrgTyJoXJciwsKqPAxZDDcvot=q5g@mail.gmail.com>
[not found] ` <CAKjQTCex5oXLkPOZeoccT5a0CxMDpdpmSqcJy4SV7h1eaeo=pA@mail.gmail.com>
[not found] ` <1343074978.66314.YahooMailNeo@web28904.mail.ir2.yahoo.com>
2012-07-23 20:31 ` Can't make RTL8188CE work with hostapd (rtl8192ce) Xavier de Almeida
2012-07-23 21:07 ` Larry Finger
[not found] ` <1343138030.94415.YahooMailNeo@web28906.mail.ir2.yahoo.com>
2012-07-24 13:56 ` Tr : " Xavier de Almeida
2012-07-24 15:06 ` Larry Finger
2012-07-24 15:25 ` Xavier de Almeida
2012-07-24 15:46 ` Larry Finger
2012-07-24 17:06 ` Tr : " Xavier de Almeida
2012-07-24 17:51 ` Larry Finger [this message]
2012-07-25 13:54 ` Xavier de Almeida
2012-07-25 17:19 ` Xavier de Almeida
2012-07-25 17:25 ` Xavier de Almeida
2012-07-25 17:43 ` Larry Finger
2012-07-26 9:58 ` Xavier de Almeida
2012-07-26 10:53 ` Larry Finger
2012-07-26 11:01 ` Xavier de Almeida
2012-07-26 11:28 ` Larry Finger
2012-07-26 12:44 ` Xavier de Almeida
2012-07-26 14:49 ` Xavier de Almeida
2012-07-26 21:52 ` Larry Finger
2012-07-27 6:34 ` Xavier de Almeida
2012-07-27 11:51 ` Larry Finger
2012-07-27 13:09 ` Xavier de Almeida
2012-07-27 14:12 ` Xavier de Almeida
2012-07-27 15:38 ` Xavier de Almeida
2012-07-27 15:59 ` Xavier de Almeida
2012-07-27 16:38 ` Xavier de Almeida
2012-07-28 15:25 ` Larry Finger
2012-07-29 19:57 ` Xavier de Almeida
2012-07-29 20:53 ` Larry Finger
2012-07-30 18:06 ` Xavier de Almeida
2012-07-30 19:51 ` Larry Finger
2012-07-30 20:03 ` Xavier de Almeida
2012-07-30 20:17 ` Xavier de Almeida
2012-07-30 21:27 ` Larry Finger
2012-07-30 21:31 ` Larry Finger
2012-07-27 8:14 ` Xavier de Almeida
2012-07-27 10:32 ` Xavier de Almeida
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=500EE086.6000304@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=xavierdealmeida@yahoo.fr \
/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;
as well as URLs for NNTP newsgroup(s).