From: "Jaap A. Haitsma" <jaap@haitsma.org>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] sendto does not compile
Date: Sun, 10 Feb 2008 11:46:16 +0100 [thread overview]
Message-ID: <8a8adccc0802100246s6a242747w2f69a128b36a109e@mail.gmail.com> (raw)
I get the following errors
main.c:355: error: 'marshal_VOID__STRING_STRING_UINT64' undeclared
(first use in this function)
main.c:355: error: (Each undeclared identifier is reported only once
main.c:355: error: for each function it appears in.)
main.c:359: error: 'marshal_VOID__UINT64' undeclared (first use in
this function)
Jaap
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2008-02-10 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 10:46 Jaap A. Haitsma [this message]
2008-02-10 10:49 ` [Bluez-devel] sendto does not compile Bastien Nocera
2008-02-10 17:26 ` Jaap A. Haitsma
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=8a8adccc0802100246s6a242747w2f69a128b36a109e@mail.gmail.com \
--to=jaap@haitsma.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