Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] [PATCH lttng-ust 1/4] Add support for musl libc to ust-dlfcn.h
Date: Tue, 31 May 2016 04:38:20 +0000 (UTC)	[thread overview]
Message-ID: <1078683747.23560.1464669500716.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <1464640293-10157-1-git-send-email-mjeanson@efficios.com>

All merged into master, stable-2.8. The commit marked
"fix" that apply to 2.7 has been backported.

----- On May 30, 2016, at 10:31 PM, Michael Jeanson mjeanson at efficios.com wrote:

> Signed-off-by: Michael Jeanson <mjeanson at efficios.com>
> ---
> include/lttng/ust-dlfcn.h | 4 ++++
> 1 file changed, 4 insertions(+)
> 
> diff --git a/include/lttng/ust-dlfcn.h b/include/lttng/ust-dlfcn.h
> index c92f1bb..7471d94 100644
> --- a/include/lttng/ust-dlfcn.h
> +++ b/include/lttng/ust-dlfcn.h
> @@ -31,6 +31,7 @@
> #error "Please include lttng/ust-dlfcn.h before dlfcn.h."
> #endif /* _DLFCN_H */
> 
> +#ifdef __GLIBC__
> /*
>  * glibc declares dlsym() and dlerror() with __attribute__((leaf)) (see
>  * THROW annotation). Unfortunately, this is not in sync with reality,
> @@ -57,5 +58,8 @@ extern int dlclose(void *__handle) __nonnull ((1));
> extern void *dlsym(void *__restrict __handle,
> 		__const char *__restrict __name) __nonnull ((2));
> extern char *dlerror(void);
> +#else
> +#include <dlfcn.h>
> +#endif /* __GLIBC__ */
> 
> #endif /* _LTTNG_UST_DLFCN_H */
> --
> 2.7.4

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com


      parent reply	other threads:[~2016-05-31  4:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30 20:31 Michael Jeanson
2016-05-30 20:31 ` [lttng-dev] [PATCH lttng-ust 2/4] Fix: strerror_r behavior is glibc specific Michael Jeanson
2016-05-30 20:31 ` [lttng-dev] [PATCH lttng-ust 3/4] Fix: use limits.h in ust-elf test Michael Jeanson
2016-05-30 20:31 ` [lttng-dev] [PATCH lttng-ust 4/4] Use config.h to detect sched_getcpu support Michael Jeanson
2016-05-31  4:38 ` Mathieu Desnoyers [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=1078683747.23560.1464669500716.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@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