[poky] error in building qt5-image
Niche Consulting India
contact at nicheconsult.in
Wed Jul 31 10:23:22 PDT 2019
there is no option to enforce single build process. Given below is usage of bit bake.
———
> Usage: bitbake [options] [recipename/target recipe:do_task ...]
>
> Executes the specified task (default is 'build') for a given set of target recipes (.bb files).
> It is assumed there is a conf/bblayers.conf available in cwd or in BBPATH which
> will provide the layer, BBFILES and other configuration information.
>
> Options:
> --version show program's version number and exit
> -h, --help show this help message and exit
> -b BUILDFILE, --buildfile=BUILDFILE
> Execute tasks from a specific .bb recipe directly.
> WARNING: Does not handle any dependencies from other
> recipes.
> -k, --continue Continue as much as possible after an error. While the
> target that failed and anything depending on it cannot
> be built, as much as possible will be built before
> stopping.
> -f, --force Force the specified targets/task to run (invalidating
> any existing stamp file).
> -c CMD, --cmd=CMD Specify the task to execute. The exact options
> available depend on the metadata. Some examples might
> be 'compile' or 'populate_sysroot' or 'listtasks' may
> give a list of the tasks available.
> -C INVALIDATE_STAMP, --clear-stamp=INVALIDATE_STAMP
> Invalidate the stamp for the specified task such as
> 'compile' and then run the default task for the
> specified target(s).
> -r PREFILE, --read=PREFILE
> Read the specified file before bitbake.conf.
> -R POSTFILE, --postread=POSTFILE
> Read the specified file after bitbake.conf.
> -v, --verbose Enable tracing of shell tasks (with 'set -x'). Also
> print bb.note(...) messages to stdout (in addition to
> writing them to ${T}/log.do_<task>).
> -D, --debug Increase the debug level. You can specify this more
> than once. -D sets the debug level to 1, where only
> bb.debug(1, ...) messages are printed to stdout; -DD
> sets the debug level to 2, where both bb.debug(1, ...)
> and bb.debug(2, ...) messages are printed; etc.
> Without -D, no debug messages are printed. Note that
> -D only affects output to stdout. All debug messages
> are written to ${T}/log.do_taskname, regardless of the
> debug level.
> -q, --quiet Output less log message data to the terminal. You can
> specify this more than once.
> -n, --dry-run Don't execute, just go through the motions.
> -S SIGNATURE_HANDLER, --dump-signatures=SIGNATURE_HANDLER
> Dump out the signature construction information, with
> no task execution. The SIGNATURE_HANDLER parameter is
> passed to the handler. Two common values are none and
> printdiff but the handler may define more/less. none
> means only dump the signature, printdiff means compare
> the dumped signature with the cached one.
> -p, --parse-only Quit after parsing the BB recipes.
> -s, --show-versions Show current and preferred versions of all recipes.
> -e, --environment Show the global or per-recipe environment complete
> with information about where variables were
> set/changed.
> -g, --graphviz Save dependency tree information for the specified
> targets in the dot syntax.
> -I EXTRA_ASSUME_PROVIDED, --ignore-deps=EXTRA_ASSUME_PROVIDED
> Assume these dependencies don't exist and are already
> provided (equivalent to ASSUME_PROVIDED). Useful to
> make dependency graphs more appealing
> -l DEBUG_DOMAINS, --log-domains=DEBUG_DOMAINS
> Show debug logging for the specified logging domains
> -P, --profile Profile the command and save reports.
> -u UI, --ui=UI The user interface to use (knotty, ncurses or taskexp
> - default knotty).
> --token=XMLRPCTOKEN Specify the connection token to be used when
> connecting to a remote server.
> --revisions-changed Set the exit code depending on whether upstream
> floating revisions have changed or not.
> --server-only Run bitbake without a UI, only starting a server
> (cooker) process.
> -B BIND, --bind=BIND The name/address for the bitbake xmlrpc server to bind
> to.
> -T SERVER_TIMEOUT, --idle-timeout=SERVER_TIMEOUT
> Set timeout to unload bitbake server due to
> inactivity, set to -1 means no unload, default:
> Environment variable BB_SERVER_TIMEOUT.
> --no-setscene Do not run any setscene tasks. sstate will be ignored
> and everything needed, built.
> --setscene-only Only run setscene tasks, don't run any real tasks.
> --remote-server=REMOTE_SERVER
> Connect to the specified server.
> -m, --kill-server Terminate any running bitbake server.
> --observe-only Connect to a server as an observing-only client.
> --status-only Check the status of the remote bitbake server.
> -w WRITEEVENTLOG, --write-log=WRITEEVENTLOG
> Writes the event log of the build to a bitbake event
> json file. Use '' (empty string) to assign the name
> automatically.
> --runall=RUNALL Run the specified task for any recipe in the taskgraph
> of the specified target (even if it wouldn't otherwise
> have run).
> --runonly=RUNONLY Run only the specified task within the taskgraph of
> the specified targets (and any task dependencies those
> tasks may have).
> On 31-Jul-2019, at 10:15 PM, Khem Raj <raj.khem at gmail.com> wrote:
>
> It seems to be a parallel build issue. Try to enforce -j1 and see if that helps
>
> On Wed, Jul 31, 2019 at 8:23 AM Niche Consulting India
> <contact at nicheconsult.in> wrote:
>>
>> hello,
>> i encountered this error when building qt5-image for ubuntu 14.04 on warrior branch.
>>
>>
>> Can someone tell me how to fix this? does this mean i checked out an older version of code?
>>
>> ————
>> # bit bake qt5-image
>> ….
>> n file included from libavdevice/avdevice.h:51,
>> from libavdevice/avdevice.c:23:
>> ./libavformat/avformat.h:2070:17: note: declared here
>> AVOutputFormat *av_oformat_next(const AVOutputFormat *f);
>> ^~~~~~~~~~~~~~~
>> libavdevice/avdevice.c:92:13: warning: 'av_iformat_next' is deprecated [-Wdeprecated-declarations]
>> if (!(prev = av_iformat_next(prev)))
>> ^~
>> In file included from libavdevice/avdevice.h:51,
>> from libavdevice/avdevice.c:23:
>> ./libavformat/avformat.h:2062:17: note: declared here
>> AVInputFormat *av_iformat_next(const AVInputFormat *f);
>> ^~~~~~~~~~~~~~~
>> make[1]: *** write jobserver: Bad file descriptor. Stop.
>> ERROR: oe_runmake failed
>> make: *** [compile] Error 2
>> WARNING: exit code 1 from a shell command.
>> ERROR: Function failed: do_compile (log file is located at /data/build_area/warrior/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/omxplayer/git-r4/temp/log.do_compile.26121)
>>
>> --
>> _______________________________________________
>> poky mailing list
>> poky at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/poky/attachments/20190731/0977b6b9/attachment-0001.html>
More information about the poky
mailing list