Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: paul.thomas@ise.bc.ca (Paul Thomas)
Subject: [lttng-dev] Building Babeltrace
Date: Wed, 6 Nov 2013 19:00:58 +0000	[thread overview]
Message-ID: <F98AC8DFC04DC741915F3DFB00515DBEE897275C@Thetis.ISE-DOM.local> (raw)
In-Reply-To: <F98AC8DFC04DC741915F3DFB00515DBEE8972716@Thetis.ISE-DOM.local>

Hello:

I get the following when building babeltrace from git:

make[4]: Entering directory `/rt_linux/babeltrace/formats/ctf/writer'
  CC     writer.lo
writer.c: In function 'bt_ctf_writer_create':
writer.c:118: error: 'O_DIRECTORY' undeclared (first use in this function)
writer.c:118: error: (Each undeclared identifier is reported only once
writer.c:118: error: for each function it appears in.)
writer.c: In function 'validate_identifier':
writer.c:564: warning: implicit declaration of function 'g_hash_table_contains'
writer.c: In function 'writer_init':
writer.c:741: warning: implicit declaration of function 'g_hash_table_add'
make[4]: *** [writer.lo] Error 1
make[4]: Leaving directory `/rt_linux/babeltrace/formats/ctf/writer'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/rt_linux/babeltrace/formats/ctf'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/rt_linux/babeltrace/formats'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/rt_linux/babeltrace'
make: *** [all] Error 2

I am running Debian:  gcc/g++ 4.4.5-8
Linux debian-rt 2.6.31.51 #1 SMP PREEMPT i686 GNU/Linux

Should I be compiling from a tarball instead?

Thanks,

Paul




  parent reply	other threads:[~2013-11-06 19:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 18:09 [lttng-dev] Unable to configure babeltrace, lttv Paul Thomas
2013-11-06 18:36 ` Yannick Brosseau
2013-11-06 19:00 ` Paul Thomas [this message]
2013-11-06 19:57   ` [lttng-dev] Building Babeltrace Jérémie Galarneau
2013-11-06 20:17     ` Jérémie Galarneau
2013-11-06 20:22     ` Paul Thomas

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=F98AC8DFC04DC741915F3DFB00515DBEE897275C@Thetis.ISE-DOM.local \
    --to=paul.thomas@ise.bc.ca \
    /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