Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Cross Compiling openobex
Date: Tue, 27 Jun 2006 14:18:15 +0200	[thread overview]
Message-ID: <1151410695.25011.25.camel@localhost> (raw)
In-Reply-To: <6297d67c0606270505v511be476t247bcfc16d451833@mail.gmail.com>

Hi Mayank,

> I am able to cross compile openobex-1.0.1 and openobex-apps-1.0.0 for
> ARM.
> But when I try to compile the application ussp-push, I get the
> following errors:
>  
> arm-linux-gcc -I/usr/local/include -I/usr/include/glib-1.2
> -I/usr/lib/glib/include -c obex_main.c -o obex_main.o
> arm-linux-gcc -I/usr/local/include -I/usr/include/glib-1.2
> -I/usr/lib/glib/include -c obex_socket.c -o obex_socket.o 
> arm-linux-gcc obex_main.o obex_socket.o -L/usr/lib -lglib
> -L/usr/local/lib /usr/local/arm/2.95.3/arm-linux/lib/libopenobex.a -o
> ussp-push
> /usr/lib/libglib.so: could not read symbols: Invalid operation
> collect2: ld returned 1 exit status 
>  
>  
> Does this mean that I have to compile glib also for ARM?

use openobex-1.3 all other versions are outdated. And you might need to
change ussp-push to not compile with GLib.

Regards

Marcel



Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-06-27 12:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27 12:05 [Bluez-devel] Cross Compiling openobex Mayank Batra
2006-06-27 12:18 ` Marcel Holtmann [this message]
2006-06-27 13:17   ` Mayank Batra

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=1151410695.25011.25.camel@localhost \
    --to=marcel@holtmann.org \
    --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