All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Mills <wmills@ti.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: yocto@yoctoproject.org
Subject: Re: build failure on ubuntu 64bits development system
Date: Wed, 18 Jan 2012 09:57:17 -0500	[thread overview]
Message-ID: <4F16DDCD.2020701@ti.com> (raw)
In-Reply-To: <4F16DC5D.9070903@mlbassoc.com>



On 01/18/2012 09:51 AM, Gary Thomas wrote:
> On 2012-01-18 07:42, James Abernathy wrote:
>>
>>
>> On Wed, Jan 18, 2012 at 9:30 AM, James Abernathy 
>> <jfabernathy@gmail.com <mailto:jfabernathy@gmail.com>> wrote:
>>
>>
>>
>>     On Wed, Jan 18, 2012 at 7:55 AM, James Abernathy 
>> <jfabernathy@gmail.com <mailto:jfabernathy@gmail.com>> wrote:
>>
>>         I just built a new development pc and installed Ubuntu 11.10 
>> x64.  I wonder if there are any new requirements to building Yocto in 
>> that environment?  I got an error right
>>         off, but then it complete the first 63 task and stopped 
>> successfully.  error below:
>>
>>         jim@ubuntu:~/poky/build-cdv$ bitbake core-image-sato
>>         Pseudo is not present but is required, building this first 
>> before the main build
>>         Parsing recipes: 100% 
>> |#################################################| Time: 00:00:25
>>         Parsing of 797 .bb files complete (0 cached, 797 parsed). 
>> 1037 targets, 22 skipped, 0 masked, 0 errors.
>>         ERROR: Execution of event handler 'run_buildstats' failed
>>         Traceback (most recent call last):
>>            File "run_buildstats(e)", line 18, in 
>> run_buildstats(e=<bb.event.BuildStarted object at 0x4c338d0>)
>>            File "buildstats.bbclass", line 21, in 
>> set_device(e=<bb.event.BuildStarted object at 0x4c338d0>)
>>         UnboundLocalError: local variable 'rdev' referenced before 
>> assignment
>>
>>
>>         Any ideas?
>>
>>         JIm A
>>
>>
>>     I went back and tried using the tarballs for poky edison and 
>> cedartrail bsp and the errors don't occur.  So I'm guessing the issue 
>> isn't related to Ubuntu 32 vs. 64 bit.
>>
>>
>> I spoke too soon. Same error in edison tarballs.  I looked at the 
>> code and I can see an place were rdev could go un assigned. If you 
>> fell out of the for loop without passing any of
>> the if conditions, rdev would be unassigned.  That must be what is 
>> happening in Ubuntu 11.10 x64
>>
>> Anybody building with Ubuntu 11.10 x64?  This doesn't happen on x32
>>
>> Jim A
>>
>>
>> def set_device(e):
>>      tmpdir = bb.data.getVar('TMPDIR', e.data, True)
>>      try:
>>          os.remove(bb.data.getVar('DEVFILE', e.data, True))
>>      except:
>>          pass
>>      
>> ############################################################################
>>      # We look for the volume TMPDIR lives on. To do all disks would 
>> make little
>>      # sense and not give us any particularly useful data. In theory 
>> we could do
>>      # something like stick DL_DIR on a different partition and this 
>> would
>>      # throw stats gathering off. The same goes with SSTATE_DIR. 
>> However, let's
>>      # get the basics in here and work on the cornercases later.
>>      
>> ############################################################################
>>      device=os.stat(tmpdir)
>>      majordev=os.major(device.st_dev)
>>      minordev=os.minor(device.st_dev)
>>      for line in open("/proc/diskstats", "r"):
>>          if majordev == int(line.split()[0]) and minordev == 
>> int(line.split()[1]):
>>             rdev=line.split()[2]
>>      file = open(bb.data.getVar('DEVFILE', e.data, True), "w")
>>      file.write(rdev)
>>      file.close()
>
> Can you show what the differences are between /proc/diskstats
> on the two systems?  That's obviously what's causing the error.
>

If your build dir is encyptfs or a fuse device or anything that is not a 
direct block device you will get this error.  This is to be fixed in 
1.1.1 but encyptfs will still have other problems.




  reply	other threads:[~2012-01-18 14:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18 12:55 build failure on ubuntu 64bits development system James Abernathy
2012-01-18 14:30 ` James Abernathy
2012-01-18 14:42   ` James Abernathy
2012-01-18 14:51     ` Gary Thomas
2012-01-18 14:57       ` William Mills [this message]
2012-01-18 15:04         ` James Abernathy
2012-01-18 15:15           ` William Mills
2012-01-18 15:25             ` James Abernathy
2012-01-18 15:31               ` Martin Jansa
2012-01-18 16:06               ` William Mills
2012-01-18 16:17                 ` Jim Abernathy
2012-01-18 16:32                   ` Saul Wold
2012-01-18 17:05                     ` Jim Abernathy
2012-01-18 21:34                       ` Darren Hart
2012-01-19 13:55                         ` Jim Abernathy
2012-01-19 15:44                           ` William Mills
2012-01-19 17:44                           ` Darren Hart
2012-01-19 20:11                             ` Jim Abernathy
2012-01-18 21:31               ` Darren Hart
2012-01-18 15:01       ` James Abernathy

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=4F16DDCD.2020701@ti.com \
    --to=wmills@ti.com \
    --cc=gary@mlbassoc.com \
    --cc=yocto@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 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.