All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jordan Yelloz <jordan@yelloz.me>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] fwup: blanked out MANS to avoid running help2man
Date: Mon, 13 Jun 2016 15:09:50 -0700	[thread overview]
Message-ID: <f85d6266-1fc1-8a0d-ade0-42955031e308@yelloz.me> (raw)
In-Reply-To: <CA+-urNQTQdVJqimMzBEJG3i7-cAEbvPirPJJZ-+-WZ_fEZ52yQ@mail.gmail.com>

On 06/13/2016 02:51 PM, Frank Hunleth wrote:
> Hi Jordan,
> 
> How about the following for disabling 'help2man'?
> 
> # help2man doesn't work when cross compiling
> FWUP_CONF_ENV = ac_cv_path_HELP2MAN=''
> 
> This is similar to what's done for the torsmo package, and it seems a
> little more obvious in purpose.
> 

Good point, I will post a new patch with this change instead.

>> +FWUP_INSTALL_TARGET_OPTS = install-exec DESTDIR=$(TARGET_DIR)
> 
> The only other file that should be installed is the bash completions
> file. That's automatically removed from the target unless you have
> bash enabled.
> 

This was actually necessary with my inferior patch because help2man was
still needed to produce the man page which was part of the `install'
target but with your approach it's no longer needed.

--
Jordan

  reply	other threads:[~2016-06-13 22:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13  2:38 [Buildroot] [PATCH 1/1] fwup: blanked out MANS to avoid running help2man Jordan Yelloz
2016-06-13  3:11 ` [Buildroot] [PATCH v2 " Jordan Yelloz
2016-06-13  5:26   ` [Buildroot] [PATCH v3 " Jordan Yelloz
2016-06-13 21:51     ` Frank Hunleth
2016-06-13 22:09       ` Jordan Yelloz [this message]
2016-06-13 22:15     ` [Buildroot] [PATCH v4 1/1] fwup: blanked out HELP2MAN_PATH autoconf value Jordan Yelloz
2016-06-14 13:45       ` Frank Hunleth
2016-06-13  3:13 ` [Buildroot] [PATCH v2 1/1] iptables: exported AR=$(TARGET_AR) to make Jordan Yelloz
2016-07-05 13:03   ` Thomas Petazzoni

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=f85d6266-1fc1-8a0d-ade0-42955031e308@yelloz.me \
    --to=jordan@yelloz.me \
    --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 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.