Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: sfont@teldat.com (Santiago Font)
Subject: [lttng-dev] LTTng-ust 2.4.0-rc4 build error with uClibc
Date: Thu, 20 Feb 2014 12:35:12 +0100	[thread overview]
Message-ID: <5305E870.5060204@teldat.com> (raw)
In-Reply-To: <5304729F.5040706@mentor.com>

Hi Paul,
      Thank you very much for your help.

      Santi

On 19/02/14 10:00, Woegerer, Paul wrote:
> Hi Santiago,
>
> it looks like uClibc does not have proper support for dlinfo().
>
> You have two options:
>
> Switch to a different C library suitable for embedded systems that does
> have proper support for dlinfo(): http://www.eglibc.org/home
>
> Build without liblttng-ust-dl (simply remove it from the list of SUBDIRS
> in the top-level Makefile.am) and accept that the following LTTng 2.4
> feature is missing in your custom build:
> http://git.lttng.org/?p=lttng-ust.git;a=blob_plain;f=doc/man/lttng-ust-dl.3;hb=HEAD
>
>
> HTH,
> Paul
>
>
> On 02/18/2014 04:56 PM, Santiago Font wrote:
>> Hi,
>>
>> I'm trying to build LTTng-ust using uClibc and I get the following error:
>>
>>                          ustdl.c:95:22: error: 'RTLD_DI_LINKMAP'
>> undeclared (first use in this function)
>>
>> Checking the file dlfcn.h from uClibc, the code defining that enum is
>> disabled by:
>>
>>                          #if 0 /* not supported by uClibc */
>>
>> How can I fix this?
>>
>> Thanks,
>>                Santi
>>
>> _______________________________________________
>> lttng-dev mailing list
>> lttng-dev at lists.lttng.org
>> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>




      reply	other threads:[~2014-02-20 11:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 15:56 Santiago Font
2014-02-19  9:00 ` Woegerer, Paul
2014-02-20 11:35   ` Santiago Font [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=5305E870.5060204@teldat.com \
    --to=sfont@teldat.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