From: Mark Brown <mkbrown32@hotmail.com>
To: Andrew Jeffery <andrew@aj.id.au>, Lei YU <mine260309@gmail.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Storage requirements for OpenBMC VirtualBox/Ubuntu build
Date: Thu, 19 Apr 2018 06:16:40 +0000 [thread overview]
Message-ID: <BY2PR02MB13309DE59A88051E5FB73ABFAEB50@BY2PR02MB1330.namprd02.prod.outlook.com> (raw)
In-Reply-To: <1524118080.2476417.1343258432.7A83D343@webmail.messagingengine.com>
Yes, I remember that it was "quilt" with reference to "u-boot".
What is the exact git command sequence to update the
openbmc clone I have to merge with your fix ?
________________________________________
From: Andrew Jeffery <andrew@aj.id.au>
Sent: Wednesday, April 18, 2018 11:08 PM
To: Mark Brown; Lei YU
Cc: openbmc@lists.ozlabs.org
Subject: Re: Storage requirements for OpenBMC VirtualBox/Ubuntu build
On Thu, 19 Apr 2018, at 14:54, Mark Brown wrote:
> In my Ubuntu 16.04.4, I used Vboxmanage to increase to 40GB (33GB sda1),
> which was not enough,
> so I doubled it to 80GB (73GB sda1) and
> then it ran through approximately 3,000 of the 4,000 tasks,
> then had an Error "/bin/sh"..."not found"..."quilt".
> whereis shows that "quilt" is installed, so this makes no sense.
> I am running Ubuntu 16.04.4, not 14.04 .
> Any ideas ?
>
I accidentally broke the u-boot recipe recently whilst resolving other bugs[1], but the break has been fixed[2]. Try updating your local branch and building again.
Hope that helps,
Andrew
[1] https://gerrit.openbmc-project.xyz/#/c/9954/
[2] https://gerrit.openbmc-project.xyz/#/c/10117/
next prev parent reply other threads:[~2018-04-19 6:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 2:10 Storage requirements for OpenBMC VirtualBox/Ubuntu build Mark Brown
2018-04-19 4:58 ` Lei YU
2018-04-19 5:24 ` Mark Brown
2018-04-19 6:08 ` Andrew Jeffery
2018-04-19 6:16 ` Mark Brown [this message]
2018-04-19 6:25 ` Andrew Jeffery
2018-04-21 20:52 ` Mark Brown
2018-04-23 0:56 ` Andrew Jeffery
2018-04-23 14:20 ` Mark Brown
2018-04-23 21:38 ` Andrew Jeffery
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=BY2PR02MB13309DE59A88051E5FB73ABFAEB50@BY2PR02MB1330.namprd02.prod.outlook.com \
--to=mkbrown32@hotmail.com \
--cc=andrew@aj.id.au \
--cc=mine260309@gmail.com \
--cc=openbmc@lists.ozlabs.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.