From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Fix build of lttng-libust
Date: Mon, 6 Nov 2017 22:12:02 +0100 [thread overview]
Message-ID: <20171106221202.2d23dac4@windsurf> (raw)
In-Reply-To: <CAB4xu_1N3NV_Z7cDYJ4DbKB=0476-axmCZUSaY4_CCA39T-i3A@mail.gmail.com>
Hello,
On Mon, 6 Nov 2017 16:06:10 -0500, Philippe Proulx wrote:
> >
> >>> Since this is anyway just an example, wouldn't it be better to just disable the
> >>> documentation entirely? I.e. teach configure.ac to understand --disable-doc and
> >>> teach Makefile.am to not recurse into doc if docs are disabled?
> >>
> >> No problem with that, for the upstream package this might be more of an issue.
> >
> > Philippe (one of the upstream developers) already said that he'd look into it.
> >
>
> It's in master now, hope it helps:
> <https://github.com/lttng/lttng-ust/commit/08aa9a26779d4ede3de7857fafd03bd6331ba948>.
Thanks!
While you're at it, do you think you could also have a look at
http://autobuild.buildroot.net/results/f46/f46ba3cc8bf3ce979e9391db05780476cbba6ea0/build-end.log ?
I reported it on the lttng mailing list a loooong time ago, and never
got any feedback.
It also happens with musl:
http://autobuild.buildroot.net/results/99b/99bfee5ccd45c945bd607c3a8c0f972338133efc/build-end.log.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-06 21:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 16:31 [Buildroot] [PATCH 1/1] Fix build of lttng-libust Norbert Lange
2017-10-30 19:40 ` Thomas Petazzoni
2017-10-31 10:20 ` Norbert Lange
2017-11-05 16:13 ` Arnout Vandecappelle
2017-11-05 16:31 ` Yann E. MORIN
2017-11-05 19:55 ` Philippe Proulx
2017-11-05 21:10 ` Yann E. MORIN
2017-11-05 21:20 ` Yann E. MORIN
2017-11-05 20:36 ` Norbert Lange
2017-11-05 22:02 ` Arnout Vandecappelle
2017-11-06 21:06 ` Philippe Proulx
2017-11-06 21:12 ` Thomas Petazzoni [this message]
2017-11-06 21:41 ` Philippe Proulx
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=20171106221202.2d23dac4@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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