public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jaap A. Haitsma" <jaap@haitsma.org>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] sendto does not compile
Date: Sun, 10 Feb 2008 18:26:17 +0100	[thread overview]
Message-ID: <8a8adccc0802100926l23fec3b3x8a8484980016b375@mail.gmail.com> (raw)
In-Reply-To: <1202640586.3491.84.camel@cookie.hadess.net>

On Feb 10, 2008 11:49 AM, Bastien Nocera <hadess@hadess.net> wrote:
>
>
> On Sun, 2008-02-10 at 11:46 +0100, Jaap A. Haitsma wrote:
> > 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)
>
> It's defined in common/marshal.h which is generated from
> common/marshal.list. You need to generate that file, or simply run make
> from the root.
>
Thanks, that's it. Somehow my dependecies were borked.

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

      reply	other threads:[~2008-02-10 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10 10:46 [Bluez-devel] sendto does not compile Jaap A. Haitsma
2008-02-10 10:49 ` Bastien Nocera
2008-02-10 17:26   ` Jaap A. Haitsma [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=8a8adccc0802100926l23fec3b3x8a8484980016b375@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