public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ricky Soh" <rickysoh@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] bccmd compilation fails (help needed)
Date: Thu, 6 Sep 2007 14:23:08 +0800	[thread overview]
Message-ID: <db972f430709052323m7d7df2dfn78fd802aeb4b780d@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 563 bytes --]

Hi,

I did ./configure, make and make install.

I scanned the Make execution, realise bccmd was not compiled.

Inside the tool folders, only has those executed during the Make command.
There is no executable bccmd.

Please help. Thanks alot.

>Hi,

>> during normal bluez-util-3.18 installation, bccmd in the "tools"
> >folder was not compiled.
>>
>> i tried the following compilation but have the following error.
>>
> >[root@localhost tools]# gcc -lusb -lbluetooth csr.c csr_3wire.c

>have the build system build it for you. That works fine.

>Regards

>Marcel

[-- Attachment #1.2: Type: text/html, Size: 692 bytes --]

[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2007-09-06  6:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06  6:23 Ricky Soh [this message]
2007-09-06  6:56 ` [Bluez-users] bccmd compilation fails (help needed) Brad Midgley
  -- strict thread matches above, loose matches on Subject: below --
2007-09-04 10:51 Ricky Soh
2007-09-04 11:23 ` Marcel Holtmann

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=db972f430709052323m7d7df2dfn78fd802aeb4b780d@mail.gmail.com \
    --to=rickysoh@gmail.com \
    --cc=bluez-users@lists.sourceforge.net \
    /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