From: jeremie.galarneau@efficios.com (Jérémie Galarneau)
Subject: [lttng-dev] Building Babeltrace
Date: Wed, 6 Nov 2013 15:17:35 -0500 [thread overview]
Message-ID: <CA+jJMxujbk_c2YxHM1NXLssB4irRz2maAWHYU3eDApAJTtRCig@mail.gmail.com> (raw)
In-Reply-To: <CA+jJMxt1ANnowdofJweazFts5f+Rarnx0gwwmDUh-UyMvRYjVg@mail.gmail.com>
Just as a heads-up, you may want to use the latest tarball release
since it appears that I have used glib functions that were not
available in glib 2.22. I'm currently working on a patch to address
this problem.
Cheers,
J?r?mie
On Wed, Nov 6, 2013 at 2:57 PM, J?r?mie Galarneau
<jeremie.galarneau at efficios.com> wrote:
> On Wed, Nov 6, 2013 at 2:00 PM, Paul Thomas <paul.thomas at ise.bc.ca> wrote:
>>
>> 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 for reporting. This commit should fix the error.
>
> commit 1b8180b91647e07b243c472e1f0c6ae198f82585
> Author: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
> Date: Wed Nov 6 14:52:59 2013 -0500
>
> ctf writer BSD compatibily: remove O_DIRECTORY
>
> Not strictly needed, especially since we are creating the directory
> ourself.
>
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
>
>
> Let me know if you still can't build babeltrace with the latest master.
>
> J?r?mie
>
>>
>> Thanks,
>>
>> Paul
>>
>>
>> _______________________________________________
>> lttng-dev mailing list
>> lttng-dev at lists.lttng.org
>> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
>
>
>
> --
> J?r?mie Galarneau
> EfficiOS Inc.
> http://www.efficios.com
--
J?r?mie Galarneau
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2013-11-06 20:17 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 ` [lttng-dev] Building Babeltrace Paul Thomas
2013-11-06 19:57 ` Jérémie Galarneau
2013-11-06 20:17 ` Jérémie Galarneau [this message]
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=CA+jJMxujbk_c2YxHM1NXLssB4irRz2maAWHYU3eDApAJTtRCig@mail.gmail.com \
--to=jeremie.galarneau@efficios.com \
/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