From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] compile on apple
Date: Wed, 11 Jun 2008 15:15:55 +0200 [thread overview]
Message-ID: <1213190155.17870.28.camel@violet.holtmann.net> (raw)
In-Reply-To: <95bb57cb0806110251xe9cc530v80224cfd836aef05@mail.gmail.com>
Hi Nico,
> i've tried to compile Bluez on macbookpro and came across error:
>
> /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I.. -I../include -Wall -O2 -D_FORTIFY_SOURCE=2 -MT bluetooth.lo
> -MD -MP -MF .deps/bluetooth.Tpo -c -o bluetooth.lo bluetooth.c
> mkdir .libs
> gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wall -O2
> -D_FORTIFY_SOURCE=2 -MT bluetooth.lo -MD -MP -MF .deps/bluetooth.Tpo
> -c bluetooth.c -fno-common -DPIC -o .libs/bluetooth.o
> bluetooth.c:35:20: error: malloc.h: No such file or directory
> In file included from bluetooth.c:39:
> ../include/bluetooth/bluetooth.h:36:20: error: endian.h: No such file
> or directory
> ../include/bluetooth/bluetooth.h:37:22: error: byteswap.h: No such
> file or directory
>
> does macros included in endian.h & byteswap.h can be coded in a
> portable way ?
I can fix the malloc.h include, because that is not needed, but for the
others, I have no idea. Maybe or maybe not.
Regards
Marcel
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-06-11 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 9:51 [Bluez-users] compile on apple nico bats
2008-06-11 13:15 ` Marcel Holtmann [this message]
2008-06-12 9:01 ` nico bats
2008-06-12 9:10 ` 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=1213190155.17870.28.camel@violet.holtmann.net \
--to=marcel@holtmann.org \
--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