From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] package/gdb: simplify the disable doc hook
Date: Mon, 1 Feb 2016 19:30:35 +0100 [thread overview]
Message-ID: <56AFA44B.3030804@mind.be> (raw)
In-Reply-To: <20160201160123.15b3470f@free-electrons.com>
On 01-02-16 16:01, Thomas Petazzoni wrote:
> Romain,
>
> On Mon, 1 Feb 2016 15:22:27 +0100, Romain Naour wrote:
>
>> diff --git a/package/gdb/gdb.mk b/package/gdb/gdb.mk
>> index 3b0f501..65b2e67 100644
>> --- a/package/gdb/gdb.mk
>> +++ b/package/gdb/gdb.mk
>> @@ -53,13 +53,8 @@ endif
>>
>> # Prevent gdb to build the documentation
>> define GDB_DISABLE_DOC
>> - $(SED) '/^SUBDIRS =/ s/doc//' $(@D)/gdb/Makefile.in
>> - if test -e $(@D)/bfd/doc/Makefile.in ; then \
>> - $(SED) 's/^INFO_DEPS =.*$$/INFO_DEPS =/' $(@D)/bfd/doc/Makefile.in ; \
>> - fi
>> - if test -e $(@D)/gprof/Makefile.in ; then \
>> - $(SED) 's/^INFO_DEPS =.*$$/INFO_DEPS =/' $(@D)/gprof/Makefile.in ; \
>> - fi
>> + echo "#!/bin/sh" > $(@D)/missing
>> + echo "exit 0" >> $(@D)/missing
>
> Is "missing" only used to check for makeinfo, or also for other things ?
>
> We also have makeinfo related hacks in the gcc and binutils packages,
> which basically consists in pointing them to "missing" as being the
> makeinfo program.
IUC, the 'missing' program will only be used if there is no makeinfo installed
on the system. So if your build host happens to have makeinfo, the documentation
will be built after all.
I don't think that is a good thing, so ac_cv_prog_MAKEINFO=missing should
probably be added as well...
>
> It is really annoying that we have to do those hacks :-/
Maybe an easier workaround is to add a directory support/wrappers in the PATH
that has empty definitions or other wrappers for programs that we want to work
around.
Regards,
Arnout
>
> Thomas
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2016-02-01 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 14:22 [Buildroot] [RFC] package/gdb: simplify the disable doc hook Romain Naour
2016-02-01 15:01 ` Thomas Petazzoni
2016-02-01 18:30 ` Arnout Vandecappelle [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=56AFA44B.3030804@mind.be \
--to=arnout@mind.be \
--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