public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: soraberri <421246@posta.unizar.es>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: learning the basics
Date: Mon, 20 Dec 2004 13:14:12 +0100	[thread overview]
Message-ID: <cq6fnu$o0n$1@sea.gmane.org> (raw)
In-Reply-To: <1103542976.29892.92.camel@pegasus>

Marcel Holtmann wrote:
> Hi,
> 
> 
>>This morning, in an attempt of auto-encourage myself, I thougth I was 
>>going to be able to compile the l2test application by my own, only from 
>>the l2test.c source and having all the required libraries properly 
>>installed... Of course I couldn't (crying). My fatal sin is that I'm 
>>learning programming, communications, bluetooth and Linux, all the same 
>>time, and all the same way (you can see that way). I hope don't bother 
>>you trying to justify myself of asking the following question:
>>
>>¿Could you give me some ligth in the points to consider while compiling 
>>a user-made source like the l2test application? I want to do this way 
>>only for learning pourposes, in order to glimpse a bit the whole picture.
>>I'm getting errors of type "undefined references" like the following
>>
>>linking l2captest (libtool)
>>linking l2captest (gcc)
>>/home/soraberri/Desarrollo/estudioC/l2captest/src/l2captest.c:222: 
>>undefined reference to `strtoba'
>>l2captest.o(.text+0x680):/home/soraberri/Desarrollo/estudioC/l2captest/src/l2captest.c:222: 
>>undefined reference to `baswap'
>>/home/soraberri/Desarrollo/estudioC/l2captest/src/l2captest.c:328: 
>>undefined reference to `baswap'
>>l2captest.o(.text+0xb54):/home/soraberri/Desarrollo/estudioC/l2captest/src/l2captest.c:329: 
>>undefined reference to `batostr'
>>/home/soraberri/Desarrollo/estudioC/l2captest/src/l2captest.c:643: 
>>undefined reference to `hci_devba'
>>l2captest.o(.text+0x14df):/home/soraberri/Desarrollo/estudioC/l2captest/src/l2captest.c:645: 
>>undefined reference to `str2ba'
>>*** Exited with status: 2 ***
>>
>>Theese functions are defined in bluetooth.h as you know. I thougth I 
>>should link with the -L /lib/modules/2.6.9-1.667/kernel/net/bluetooth/ 
>>flag, but there is the same output.
> 
> 
> don't link anything against any kernel stuff from userspace. This will
> never work. I don't understand why don't you use --enable-test from the
> bluez-utils configure script. However what you are searching for is:
> 
> 	gcc l2captest.c -o l2captest -lbluetooth
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/

Hi Marcel
Yes, I appreciate very much your answer. You've solved the whole of my 
actual doubts. You said you didn't understand why I don't just use 
--enable-test from the bluez-utils configure script. Well that's easy: 
because I didn't know about the possibility. Anyway, it's helpful for me 
  in order to learn.
Thanks Marcel



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2004-12-20 12:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-20 11:24 [Bluez-devel] learning the basics soraberri
2004-12-20 11:42 ` Marcel Holtmann
2004-12-20 12:14   ` soraberri [this message]

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='cq6fnu$o0n$1@sea.gmane.org' \
    --to=421246@posta.unizar.es \
    --cc=bluez-devel@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