From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] problem with bluez-utils 3.4 and dbus
Date: Tue, 29 Aug 2006 22:53:48 +0200 [thread overview]
Message-ID: <1156884828.4026.30.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <44F4A0FC.3090809@pracucci.com>
Hi Marco,
> > /usr/local/arm-linux/lib/gcc-lib/arm-linux/3.3.2/../../../../arm-
> > linux/bin/ld:
> > cannot find -ldbus-glib-1
> > collect2: ld returned 1 exit
> > status
>
> Have you cross compiled dbus?
> If you have cross compiled dbus you should add -L<dbus library path> to
> LDFLAG, where <dbus library path> is the path to the cross compiled dbus
> library.
I would prefer if you actually trust pkg-config to configure this
correctly. Messing around with the linker path can have weird side
effects if you don't know exactly what you are doing.
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
next prev parent reply other threads:[~2006-08-29 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 15:38 [Bluez-devel] problem with bluez-utils 3.4 and dbus Alex B
2006-08-29 17:52 ` Marcel Holtmann
2006-08-29 20:18 ` Marco Pracucci
2006-08-29 20:53 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-30 2:03 Li, Lea
2006-08-30 9:40 ` Marcel Holtmann
2006-08-30 17:17 ` Brand, Chris
2006-08-30 2:27 Li, Lea
2006-08-30 9:40 ` Marcel Holtmann
2006-08-30 17:33 ` Brand, Chris
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=1156884828.4026.30.camel@aeonflux.holtmann.net \
--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