public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gustavo F. Padovan" <gustavo@las.ic.unicamp.br>
To: Yao Ye <yeyao@utstar.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: OBEX profile support
Date: Mon, 16 Feb 2009 23:20:03 -0300	[thread overview]
Message-ID: <6b53b1990902161820g596a4fc1wfa3c053b81bb315b@mail.gmail.com> (raw)
In-Reply-To: <9F2B2656C8747B498D56A7B30FF5EB9FF291E9@CNMAIL13.cn.utstarcom.com>

On Mon, Feb 16, 2009 at 10:05 PM, Yao Ye <yeyao@utstar.com> wrote:
>
>> I have openobex compiled, but obexftp fail to compile due to its
> bluetooth code.
>
>> if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../includes    -g -O2 -W
>> -Wundef -Wmissing-declarations -Wmissing-prototypes -Wall -MT
> obexftpd.o -MD -MP -MF ".deps/obexftpd.Tpo" -c -o obexftpd.o obexftpd.c;
> \
>>         then mv -f ".deps/obexftpd.Tpo" ".deps/obexftpd.Po"; else rm
> -f ".deps/obexftpd.Tpo"; exit 1; fi
>> obexftpd.c:81: error: expected '=', ',', ';', 'asm' or '__attribute__'
>> before '*' token
>> obexftpd.c: In function 'start_server':
>> obexftpd.c:891: warning: implicit declaration of function
> 'BtOBEX_ServerRegister'
>> obexftpd.c:891: error: 'bt_src' undeclared (first use in this
> function)
>
> in obexftp-0.22-arm\apps\obexftpd.c,
> del static bdaddr_t *bt_src = NULL;
> and add as below,
> then compile again.
>
>
> #ifdef HAVE_BLUETOOTH
>
> //static bdaddr_t *bt_src = NULL; //del by yaoye
>
> //add by yaoye
> struct {
>        uint8_t b[6];
> } __attribute__((packed)) *bt_src = NULL;
>
> #endif


Thank's. It works now. :-)
>



-- 
Gustavo F. Padovan

Computer Engineering Student
Institute of Computing - IC
University of Campinas - UNICAMP

email: gustavo@las.ic.unicamp.br
gtalk: gfpadovan@gmail.com
mobile: +55 19 81030803

      reply	other threads:[~2009-02-17  2:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-14 12:05 OBEX profile support Kartikey Parmar
2009-02-16  4:57 ` shy
2009-02-16  6:03   ` Gustavo F. Padovan
2009-02-16  6:24     ` shy
2009-02-16 12:13       ` Kartikey Parmar
2009-02-16 12:46       ` Gustavo F. Padovan
2009-02-17  1:05         ` Yao Ye
2009-02-17  2:20           ` Gustavo F. Padovan [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=6b53b1990902161820g596a4fc1wfa3c053b81bb315b@mail.gmail.com \
    --to=gustavo@las.ic.unicamp.br \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=yeyao@utstar.com \
    /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