Anyone using Ubuntu 8.04 Hardy Heron with Mokomakefile or OE
ml at e4net.com
Mon Jul 21 23:55:07 CEST 2008
I tried this over the weekend, so yes pretty recently.
It maybe related to using KUbuntu (but unlikely).
Seems at least one other has done it, but another is reporting the same errors I get but they have
KUbuntu too. (I can't think why that would make a difference though).
Vijay Vaidyanathan wrote:
> Hi ...
>> On Jul 21, 2008, at 12:30 PM, Jim Morris wrote:
>>> Before I go and spend another 4 hours on this, is anyone successfully
>>> using the latest Ubuntu to
>>> build via Mokomakefile or OE?
> I just completed (last week) creating an Amazon EC2 image with a full
> ASU build ... I did have to make a few minor changes along the way, and
> I think I updated the Wiki (unless I forgot something!) for the most
> part. Did you try your rebuild recently?
> The one thing I did notice is that if you use the parallel make options
> I did get some failures that went away when I switched to a
> non-parallelized make. If you dont need an unattended rebuild, you can
> just run the make again and it will usually work. If you need an
> unattended build, a non-parallelized make will work.
> The AMI was based on Ubuntu 8.04 and then applying all updates. I did
> set up a machine that did a clean build of ASU with no errors.
> I have two images of Hardy Heron 8.04 - one is just the machine that
> *can* do a clean build and the other (much larger!) image is that of a
> machine that has just done a clean build (of ASU).
> I havent tested the resulting kernels etc so I havent made the AMIs
> public yet.
> If someone else has the time/enthusiasm to test the distributions I
> built, I'd be happy to mark the AMIs public, just let me know via email.
> Else I will probably get to it sometime over the next week.
> - VV
> PS: If you aren't familiar with Amazon EC2, it is basically your "server
> in the sky" hosted by Amazon to which you get root/ssh access. You are
> billed per hour for your server, starting at $0.10 per hour. It is
> something of a pain to set up your amazon account, but once you have
> that going, it is very easy to run, access and terminate server
> instances. The only serious limitation right now the disk space is
> "ephemeral" in the sense that when you terminate an instance, all the
> disk space evaporates as well, unless you bundle it into the root file
> system and create a new image (which is what I did). Amazon has a
> mechanism for persistent file storage in beta. Details on EC2 are at
> http://www.amazon.com/ec2/ along with tutorials and such.
Jim Morris, http://blog.wolfman.com
More information about the devel