From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Slater, Joseph" <joe.slater@windriver.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] linuxdoc-tools: add dependency on texinfo
Date: Tue, 12 Nov 2013 21:27:27 +0000 [thread overview]
Message-ID: <1384291647.6460.67.camel@ted> (raw)
In-Reply-To: <007BD92917A2324FA403BCF9A464CF8455BE9A7A@ALA-MBA.corp.ad.wrs.com>
On Tue, 2013-11-12 at 20:46 +0000, Slater, Joseph wrote:
>
> > -----Original Message-----
> > From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org]
> > Sent: Tuesday, November 12, 2013 11:45 AM
> > To: Slater, Joseph
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] [PATCH 1/1] linuxdoc-tools: add dependency on texinfo
> >
> > On Tue, 2013-11-12 at 19:02 +0000, Slater, Joseph wrote:
> > > I believe we will use the host makeinfo, if that exists, so we
> > > won't automatically build texinfo-native. But, if we are building
> > > it at the same time we are trying to run makeinfo, we might get
> > > "our" version instead of the host's, and our version might not be
> > > fully installed. At least, that looks like what happened for the
> > > build failure this patch attempts to fix.
> >
> > It would help to have that in the commit message.
> >
> > Equally, does this really solve the problem or does it just move it
> > elsewhere as other applications probably use makeinfo too? :/
>
> It does just move it elsewhere. I don't know if texinfo would be basic
> enough to force it to build early (I'm not sure how to do that), or if
> we just expect packages that need it to depend on it.
Could we simply not install the makeinfo binary in texinfo-native and
always use the one from the host?
Cheers,
Richard
prev parent reply other threads:[~2013-11-12 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 21:49 [PATCH 1/1] linuxdoc-tools: add dependency on texinfo Joe Slater
2013-11-12 10:47 ` Richard Purdie
2013-11-12 19:02 ` Slater, Joseph
2013-11-12 19:45 ` Richard Purdie
2013-11-12 20:46 ` Slater, Joseph
2013-11-12 21:27 ` Richard Purdie [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=1384291647.6460.67.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=joe.slater@windriver.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.