From: Khem Raj <raj.khem@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: help2man
Date: Mon, 03 Oct 2011 12:06:32 -0700 [thread overview]
Message-ID: <4E8A07B8.8090009@gmail.com> (raw)
In-Reply-To: <1317297541.12332.85.camel@ted>
On 9/29/2011 4:58 AM, Richard Purdie wrote:
> The more I look at and think about help2man, the more it looks like
> something we just shouldn't need/use.
>
> In summary, it runs a binary and captures its --help output. This rules
> it out from being useful in most cross compiling scenarios, i.e. all
> target packages.
right. This should be disabled for cross builds. May be it should be
disabled in autotools bbclass do_configure itself.
>
> In the -native/-cross cases, we don't really care about man pages.
>
> I'm therefore thinking we should really just drop the dependency and
> symlink help2man to /bin/false. The missing script in autotools should
> then just silently touch the man page files instead of regenerating
> them.
>
> I tried to figure out which recipes actually use help2man:
>
> $ grep HELP2MAN * -r --exclude=Makefile.in 2> /dev/null | grep -v missing
>
> and against a core-image-sato this gave:
>
> libtool
> libtasn1
> gettext
> automake
> autoconf
> flex
> bison
> m4
>
> which isn't that many recipes to go and beat up manually if necessary.
> It certainly doesn't warrant a global include in autotools.bbclass IMO.
>
> Cheers,
>
> Richard
>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2011-10-03 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 11:58 help2man Richard Purdie
2011-10-03 19:06 ` Khem Raj [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=4E8A07B8.8090009@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.