From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: textinfo failure
Date: Fri, 13 Jun 2014 11:59:52 -0600 [thread overview]
Message-ID: <539B3C18.1090701@mlbassoc.com> (raw)
In-Reply-To: <20140613163159.GO27324@denix.org>
On 2014-06-13 10:32, Denys Dmytriyenko wrote:
> Hi,
>
> The recent texinfo change now breaks at least bison-native for me:
>
> | Traceback (most recent call last):
> | File "/OE/tmp-eglibc/sysroots/x86_64-linux/usr/bin/texinfo-dummy-native/makeinfo", line 109, in <module>
> | "-E option not yet supported" + stub_msg
> | AssertionError: -E option not yet supported
> | This stand-in version of makeinfo is not yet fully capable of emulating the real
> | version from the GNU texinfo suite. If you see this message, file a bug report
> | with details on the recipe that failed.
> |
> | mv: cannot move `.am14993/bison.info' to `.//OE/tmp-eglibc/work/x86_64-linux/bison-native/2.7.1-r0/bison-2.7.1/doc/': No such file or directory
> | make[2]: *** [/OE/tmp-eglibc/work/x86_64-linux/bison-native/2.7.1-r0/bison-2.7.1/doc/bison.info] Error 1
> | make[2]: Leaving directory `/OE/tmp-eglibc/work/x86_64-linux/bison-native/2.7.1-r0/build/doc'
> | make[1]: *** [install-recursive] Error 1
> | make[1]: Leaving directory `/OE/tmp-eglibc/work/x86_64-linux/bison-native/2.7.1-r0/build'
> | make: *** [install] Error 2
> | ERROR: oe_runmake failed
> | WARNING: /OE/tmp-eglibc/work/x86_64-linux/bison-native/2.7.1-r0/temp/run.do_install.13309:1 exit 1 from
> | exit 1
> | ERROR: Function failed: do_install (log file is located at /OE/tmp-eglibc/work/x86_64-linux/bison-native/2.7.1-r0/temp/log.do_install.13309)
> NOTE: recipe bison-native-2.7.1-r0: task do_install: Failed
> ERROR: Task 770 (virtual:native:/home/jenkins/distroless-build/sources/oe-core/meta/recipes-devtools/bison/bison_2.7.1.bb, do_install)
>
Odd - I just built it in a clean tree with Poky/Yocto master
rev 8e0c54cd0e82ffe120f84f495101cd29e6fd06bf.
What did you do to get that 'texinfo-dummy-native' version installed?
None of my builds end up with makeinfo in sysroots.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-06-13 17:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 16:32 textinfo failure Denys Dmytriyenko
2014-06-13 17:59 ` Gary Thomas [this message]
2014-06-13 18:40 ` Eliaser, MaX
2014-06-13 19:11 ` Denys Dmytriyenko
2014-06-13 21:47 ` Eliaser, MaX
2014-06-13 18:37 ` Eliaser, MaX
2016-04-25 21:07 ` J.J. Garcia
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=539B3C18.1090701@mlbassoc.com \
--to=gary@mlbassoc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox