($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Brahmmi Boss <brahmmi88@gmail.com>
To: "Reyna, David" <david.reyna@windriver.com>
Cc: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: Query regarding toaster setup in local build mode
Date: Thu, 25 Jan 2018 18:23:11 +0530	[thread overview]
Message-ID: <CAHK8ku1kTg4X30XO9JcHVoQw9Wnjn5x91DMbC2K8oxxT6EKXsA@mail.gmail.com> (raw)
In-Reply-To: <5E53D14CE4667A45B9A06760DE5D13D0F11705E4@ALA-MBC.corp.ad.wrs.com>

[-- Attachment #1: Type: text/plain, Size: 6464 bytes --]

Hi David,

Thank you very much .

Thanks and Regards
   veera

On Thu, Jan 25, 2018 at 4:03 PM, Reyna, David <david.reyna@windriver.com>
wrote:

> Hi,
>
>
>
> > git clone -b daisy git://git.yoctoproject.org/poky.git
>
>
>
> Daisy (YP-1.6)! That is from April 2014! Is there is a compelling reason
> why you are using that release?
>
>
>
> We currently only support Rocko 2.4, Pyro 2.3, and Morty 2.2.
>
>
>
> All of the recent releases fully support both the original local build
> model and the newer remote project build model, so the latest is indeed the
> greatest for those reasons and many more. I do local builds all the time
> with them.
>
>
>
> - David
>
>
>
>
>
>
>
> *From:* Brahmmi Boss [mailto:brahmmi88@gmail.com]
> *Sent:* Thursday, January 25, 2018 2:23 AM
> *To:* Reyna, David
> *Cc:* toaster@yoctoproject.org
> *Subject:* Re: [Toaster] Query regarding toaster setup in local build mode
>
>
>
> Hi David,
>
> Thanks for response. i did exactly the same steps but the result is same
>
> here is the log
>
> veera@veera-OptiPlex-9020:~/toaster$ git clone -b daisy git://
> git.yoctoproject.org/poky.git
> Cloning into 'poky'...
> remote: Counting objects: 390449, done.
> remote: Compressing objects: 100% (93621/93621), done.
> remote: Total 390449 (delta 290749), reused 389781 (delta 290084)
> Receiving objects: 100% (390449/390449), 139.02 MiB | 6.73 MiB/s, done.
> Resolving deltas: 100% (290749/290749), done.
> Checking connectivity... done.
> veera@veera-OptiPlex-9020:~/toaster$ cd poky
> veera@veera-OptiPlex-9020:~/toaster/poky$ . ./oe-init-build-env
> You had no conf/local.conf file. This configuration file has therefore been
> created for you with some default values. You may wish to edit it to use a
> different MACHINE (target hardware) or enable parallel build options to
> take
> advantage of multiple cores for example. See the file for more information
> as
> common configuration options are commented.
>
> The Yocto Project has extensive documentation about OE including a
> reference manual
> which can be found at:
>     http://yoctoproject.org/documentation
>
> For more information about OpenEmbedded see their website:
>     http://www.openembedded.org/
>
> You had no conf/bblayers.conf file. The configuration file has been
> created for
> you with some default values. To add additional metadata layers into your
> configuration please add entries to this file.
>
> The Yocto Project has extensive documentation about OE including a
> reference manual
> which can be found at:
>     http://yoctoproject.org/documentation
>
> For more information about OpenEmbedded see their website:
>     http://www.openembedded.org/
>
>
>
> ### Shell environment set up for builds. ###
>
> You can now run 'bitbake <target>'
>
> Common targets are:
>     core-image-minimal
>     core-image-sato
>     meta-toolchain
>     adt-installer
>     meta-ide-support
>
> You can also run generated qemu images with a command like 'runqemu
> qemux86'
> veera@veera-OptiPlex-9020:~/toaster/poky/build$ . toaster start
> The system will start.
> Syncing...
> Creating tables ...
> Creating table south_migrationhistory
> Installing custom SQL ...
> Installing indexes ...
> Installed 0 object(s) from 0 fixture(s)
>
> Synced:
>  > django.contrib.staticfiles
>  > django.contrib.humanize
>  > south
>
> Not synced (use migrations):
>  - orm
> (use ./manage.py migrate to migrate these)
> Running migrations for orm:
>  - Migrating forwards to 0007_auto__add_helptext.
>  > orm:0001_initial
>  > orm:0002_auto__add_field_build_timespent
>  > orm:0003_timespent
>  - Migration 'orm:0003_timespent' is marked for no-dry-run.
>  > orm:0004_auto__add_field_package_installed_name
>  > orm:0005_auto__add_target_image_file__add_target_file__
> add_field_variablehistor
>  > orm:0006_auto__add_field_target_image_size__add_field_
> target_license_manifest_p
>  > orm:0007_auto__add_helptext
>  - Loading initial data for orm.
> Installed 0 object(s) from 0 fixture(s)
> [1]+  Exit 1                  python $BBBASEDIR/lib/toaster/manage.py
> runserver 0.0.0.0:8000 < /dev/null > ${BUILDDIR}/toaster_web.log 2>&1
> Failed start.
> veera@veera-OptiPlex-9020:~/toaster/poky/build$
>
>
>
>
> On Thu, Jan 25, 2018 at 3:10 PM, Reyna, David <david.reyna@windriver.com>
> wrote:
>
> Hi Veera,
>
>
>
> Since you are using an explicit “source bitbake/bin/toaster” from the
> “poky” directory, I am concerned that your environment is not set up.
>
>
>
> Here is how I do local build captures:
>
>
>
>   $ cd poky
>
>   $ . ./oe-init-build-env
>
>   $ . toaster start
>
>   $ bitbake core-image-base
>
>
>
> Open a browser to “localhost:8000” to watch the build and examine the
> results, and perhaps run additional bitbake build commands.
>
>
>
> When you are all done and want to stop the server:
>
>   $ . toaster stop
>
>
>
> Observe that you need to be in a proper bitbake build environment, and use
> the toaster “start” and “stop” commands.
>
>
>
> - David
>
>
>
>
>
> *From:* toaster-bounces@yoctoproject.org [mailto:toaster-bounces@
> yoctoproject.org] *On Behalf Of *Brahmmi Boss
> *Sent:* Wednesday, January 24, 2018 9:37 PM
> *To:* toaster@yoctoproject.org
> *Subject:* [Toaster] Query regarding toaster setup in local build mode
>
>
>
> Hi,
>
> I am trying to setup toaster  in in build mode locally on ubuntu pc.but i
> got the following errors,
>
> please help to resolve the errors.
>
>
>
> veera@veera-OptiPlex-9020:~/toaster/poky$ source bitbake/bin/toaster
> The system will start.
> Syncing...
> Creating tables ...
> Installing custom SQL ...
> Installing indexes ...
> Installed 0 object(s) from 0 fixture(s)
>
> Synced:
>  > django.contrib.staticfiles
>  > django.contrib.humanize
>  > south
>
> Not synced (use migrations):
>  - orm
> (use ./manage.py migrate to migrate these)
> Running migrations for orm:
> - Nothing to migrate.
>  - Loading initial data for orm.
> Installed 0 object(s) from 0 fixture(s)
> [1]+  Exit 1                  python $BBBASEDIR/lib/toaster/manage.py
> runserver 0.0.0.0:8000 < /dev/null > ${BUILDDIR}/toaster_web.log 2>&1
> Failed start.
> veera@veera-OptiPlex-9020:~/toaster/poky$
>
>
>
> Thanks and Regards
>
>       veera
>
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 15084 bytes --]

      reply	other threads:[~2018-01-25 12:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25  5:36 Query regarding toaster setup in local build mode Brahmmi Boss
2018-01-25  9:40 ` Reyna, David
2018-01-25 10:22   ` Brahmmi Boss
2018-01-25 10:33     ` Reyna, David
2018-01-25 12:53       ` Brahmmi Boss [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=CAHK8ku1kTg4X30XO9JcHVoQw9Wnjn5x91DMbC2K8oxxT6EKXsA@mail.gmail.com \
    --to=brahmmi88@gmail.com \
    --cc=david.reyna@windriver.com \
    --cc=toaster@yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).