From: "John H." <mistamaila@yahoo.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] error on bluez-utils compile(fc4)
Date: Tue, 21 Jun 2005 01:59:08 -0700 (PDT) [thread overview]
Message-ID: <20050621085908.17812.qmail@web50702.mail.yahoo.com> (raw)
In-Reply-To: <1119217947.8954.8.camel@pegasus>
so libs2 and utils2 is not related to 2.17 of both on
site?
--- Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi John,
>
> > apparently not, or something.
> >
> > I tried utils, and it gave me this error...
> >
> > hciconfig.o(.text+0x1bd4): In function
> `cmd_inq_type':
> > hciconfig.c: undefined reference to
> > `hci_write_inquiry_scan_type'
> > hciconfig.o(.text+0x1bf8):hciconfig.c: undefined
> > reference to `hci_read_inquiry_scan_type'
> > collect2: ld returned 1 exit status
> > make[2]: *** [hciconfig] Error 1
> > make[2]: Leaving directory
> > `/tmp/bluez-utils-cvs/tools'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/tmp/bluez-utils-cvs'
> > make: *** [all] Error 2
>
> you need the libs from CVS, too.
>
> > utils2 gave me this error on configure, although I
> > have luez-libs 2.17 installed ...
> >
> > checking for bt_inquiry in -lbluetooth... no
> > configure: error: Bluetooth library not found
>
> Don't mix libs2 or utils2 with current libs and
> utils.
>
> Regards
>
> Marcel
>
>
>
>
>
-------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux
> Migration Strategies
> from IBM. Find simple to follow Roadmaps,
> straightforward articles,
> informative Webcasts and more! Get everything you
> need to get up to
> speed, fast.
>
http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/bluez-users
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-06-21 8:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-12 8:57 [Bluez-users] can't receive files from phone Graham White
2005-06-12 12:56 ` Fredy P
2005-06-13 2:50 ` [Bluez-users] python error on bluepin John H.
2005-06-13 6:41 ` Fredy P
2005-06-13 19:54 ` John H.
2005-06-13 20:10 ` Marco Trudel
2005-06-13 20:15 ` John H.
2005-06-13 20:26 ` Marco Trudel
2005-06-16 7:50 ` Fredy P
2005-06-17 2:58 ` [Bluez-users] upgrade to fc4 kills bluez-utils John H.
2005-06-19 21:30 ` [Bluez-users] error on bluez-utils compile(fc4) John H.
2005-06-19 21:35 ` Marcel Holtmann
2005-06-19 21:37 ` John H.
2005-06-19 21:48 ` Marcel Holtmann
2005-06-19 21:49 ` John H.
2005-06-19 21:52 ` Marcel Holtmann
2005-06-21 8:59 ` John H. [this message]
2005-06-21 10:58 ` 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=20050621085908.17812.qmail@web50702.mail.yahoo.com \
--to=mistamaila@yahoo.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