From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libtasn: fixed cross build issue
Date: Wed, 30 May 2012 17:47:34 +0100 [thread overview]
Message-ID: <1338396454.20169.163.camel@ted> (raw)
In-Reply-To: <lyy5o9zm89.fsf@ensc-virt.intern.sigma-chemnitz.de>
On Wed, 2012-05-30 at 18:07 +0200, Enrico Scholz wrote:
> Richard Purdie <richard.purdie@linuxfoundation.org> writes:
>
> >> | /bin/sh ../libtasn1-2.12-r1/libtasn1-2.12/build-aux/missing --run help2man --info-page libtasn1 \
> >> | --name="ASN.1 DER encoder" \
> >> | --output=asn1Coding.1 ../src/asn1Coding
> >> | help2man: can't get `--help' info from ../src/asn1Coding
> >> | Try `--no-discard-stderr' if option outputs to stderr
> >> | make[3]: *** [asn1Coding.1] Error 1
> >>
> >> which was caused by touching configure.ac which is a dependency of the
> >> generated man pages.
> >>
> >> Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
> >> ---
> >> meta/recipes-support/gnutls/libtasn1_2.12.bb | 10 +++++++++-
> >> 1 files changed, 9 insertions(+), 1 deletions(-)
> >
> > This is just a workaround, I thought we'd found a better way to handle
> > this.
>
> setting HELP2MAN environment to 'true' for cross-builds might be a
> general solution.... But this does not seem to be implemented...
Right, I remember looking into this and its hard to disable. I've pushed
a PATH change to address this problem...
Cheers,
Richard
next prev parent reply other threads:[~2012-05-30 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 15:17 [PATCH] libtasn: fixed cross build issue Enrico Scholz
2012-05-30 15:44 ` Richard Purdie
2012-05-30 16:07 ` Enrico Scholz
2012-05-30 16:47 ` Richard Purdie [this message]
2012-05-30 16:54 ` Enrico Scholz
2012-05-30 17:07 ` Richard Purdie
2012-05-30 17:09 ` Khem Raj
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=1338396454.20169.163.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=enrico.scholz@sigma-chemnitz.de \
--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.