[yocto] raspberrypi create_image.rpi-sdimg fails

2015-11-12 Thread Raj Jar
Hi,

This is my poky version

Build Configuration:
BB_VERSION= "1.26.0"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING   = "Ubuntu-14.04"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "raspberrypi"
DISTRO= "poky"
DISTRO_VERSION= "1.8.1"
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
TARGET_FPU= "vfp"
meta
meta-yocto
meta-yocto-bsp= "fido:b74ea963cefffad9fbd91d4eb9b240f6a8c86cd0"
meta-raspberrypi  = "fido:b896a7da70dd7a16ba7ffd664f7747cb37e1d142"

>
> I have 60GB space in my build system still i face
>
> NOTE: Preparing RunQueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> ERROR: Error: The image creation script
> '/home/raj/Projects/raspberry_pi/yacto/poky/raspberrypi_build/tmp/work/raspberrypi-poky-linux-gnueabi/rpi-hwup-image/1.0-r0/temp/create_image.rpi-sdimg'
> returned 1:
> Creating filesystem with Boot partition 20480 KiB and RootFS 77824 KiB
> 0+0 records in
> 0+0 records out
> 0 bytes (0 B) copied, 7.4427e-05 s, 0.0 kB/s
> Model:  (file)
> Disk
> /home/raj/Projects/raspberry_pi/yacto/poky/raspberrypi_build/tmp/deploy/images/raspberrypi/rpi-hwup-image-raspberrypi-20151102024300.rootfs.rpi-sdimg:
> 105MB
> Sector size (logical/physical): 512B/512B
> Partition Table: msdos
> Disk Flags:
>
> Number  Start  EndSizeTypeFile system  Flags
>  1  4194kB  25.2MB  21.0MB  primary  boot, lba
>  2  25.2MB  105MB  79.7MB  primary
>
> mkfs.vfat 2.11 (12 Mar 2005)
> Disk full
> WARNING:
> /home/raj/Projects/raspberry_pi/yacto/poky/raspberrypi_build/tmp/work/raspberrypi-poky-linux-gnueabi/rpi-hwup-image/1.0-r0/temp/create_image.rpi-sdimg:1
> exit 1 from
>  mcopy -i
> /home/raj/Projects/raspberry_pi/yacto/poky/raspberrypi_build/tmp/work/raspberrypi-poky-linux-gnueabi/rpi-hwup-image/1.0-r0/boot.img
> -s
> /home/raj/Projects/raspberry_pi/yacto/poky/raspberrypi_build/tmp/deploy/images/raspberrypi/Image-raspberrypi.bin
> ::kernel.img
>
> ERROR: Function failed: do_rootfs
> ERROR: Logfile of failure stored in:
> /home/raj/Projects/raspberry_pi/yacto/poky/raspberrypi_build/tmp/work/raspberrypi-poky-linux-gnueabi/rpi-hwup-image/1.0-r0/temp/log.do_rootfs.13457
> ERROR: Task 7
> (/home/raj/Projects/raspberry_pi/yacto/poky/meta-raspberrypi/recipes-core/images/
> rpi-hwup-image.bb, do_rootfs) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 1954 tasks of which 1953 didn't need to be
> rerun and 1 failed.
> No currently running tasks (1953 of 1955)
>
> Summary: 1 task failed:
>
> /home/raj/Projects/raspberry_pi/yacto/poky/meta-raspberrypi/recipes-core/images/
> rpi-hwup-image.bb, do_rootfs
>

-- 
Regards,
RAJ M
Mob. # +91-9597208150


Have a great day ahead.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-darwin][PATCH] osx-runtime: OSX Yosemite v10.10

2015-11-12 Thread Trevor Woerner
On 08/12/15 16:01, Bystricky, Juro wrote:
> yes, I ran into the same libgcc problem, I plan on tackling it eventually. 
> Likely some paths are not set correctly.
> For what is worth, try to build the SDK against the poky "dizzy" branch.
> I was able to build Darwin SDK with it. You may need to patch some other 
> files though.
> Anyway, there is new repo 
> https://git.yoctoproject.org/cgit/cgit.cgi/meta-darwin-contrib/
> where I will place some Darwin patches, most notably those I used to build 
> the "dizzy" SDK (later next week).

I can't seem to get even this working (i.e. generating an SDK for MacOSX
using dizzy).

$ cat conf/bblayers.conf

# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "6"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  /z/darwinSDK/layers/meta-poky/meta \
  /z/darwinSDK/layers/meta-poky/meta-yocto \
  /z/darwinSDK/layers/meta-poky/meta-yocto-bsp \
  /z/darwinSDK/layers/meta-darwin-contrib \
  "
BBLAYERS_NON_REMOVABLE ?= " \
  /z/darwinSDK/layers/meta-poky/meta \
  /z/darwinSDK/layers/meta-poky/meta-yocto \



$ cat conf/local.conf

MACHINE ??= "qemux86"
DL_DIR ?= "/home/trevor/devel/Downloads"
DISTRO ?= "poky"
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES = "debug-tweaks"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS = "\
STOPTASKS,${TMPDIR},1G,100K \
STOPTASKS,${DL_DIR},1G,100K \
STOPTASKS,${SSTATE_DIR},1G,100K \
ABORT,${TMPDIR},100M,1K \
ABORT,${DL_DIR},100M,1K \
ABORT,${SSTATE_DIR},100M,1K"
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
ASSUME_PROVIDED += "libsdl-native"
CONF_VERSION = "1"

SDKMACHINE = "i386-darwin"



build config:
$ bitbake core-image-minimal -c populate_sdk

Build Configuration:
BB_VERSION= "1.24.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "openSUSE-project-13.2"
TARGET_SYS= "i586-poky-linux"
MACHINE   = "qemux86"
DISTRO= "poky"
DISTRO_VERSION= "1.7.3"
TUNE_FEATURES = "m32 i586"
TARGET_FPU= ""
meta 
meta-yocto   
meta-yocto-bsp= "dizzy:b38454c2e3a7a58f5397bb16d59e2b0aa71c4a94"
meta-darwin-contrib =
"juro/dizzy/osx-runtime:396962db08ed77c5ee83cd5dd2c301402ec826c1"



meta-darwin-contrib doesn't have a "dizzy" branch, but I tried all of
the "juro/dizzy/*" branches individually without success. Is there
anything obvious I'm doing wrong?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [PATCH 0/6] [meta-mingw] [jethro/master] Update to YP 2.0

2015-11-12 Thread Mark Hatle
The patches referenced in the summary below have previous been sent to
the Yocto Project mailing list.  I have collected them together in the 
combination that works for me with Jethro and Master branches.

They can be inspected at:

http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=mgh/meta-mingw

or git fetched from:

git://git.yoctoproject.org/poky-contrib mgh/meta-mingw

I would recommend we take this and merge them to master, and branch off
for Jethro.


Mark Hatle (3):
  nativesdk-gcc: Add mingw32 named libraries to files list
  meta-environment: Update environment files to batch files
  toolchain-scripts-mingw32: Use short paths (8.3)

Peter Seebach (3):
  gcc-runtime: Drop libgomp for mingw32 runtime
  binutils*.bbappend: Work with all 2.25 versions
  gcc*.bbappend: Work with 5.2.

 classes/toolchain-scripts-mingw32.bbclass  | 88 ++
 recipes-core/meta/meta-environment.bbappend|  4 +
 .../binutils-cross-canadian_2.25%.bbappend |  5 ++
 .../binutils/binutils-cross-canadian_2.25.bbappend |  5 --
 recipes-devtools/gcc/gcc-cross-canadian_%.bbappend |  6 ++
 .../gcc/gcc-cross-canadian_4.9.bbappend|  6 --
 .../gcc/gcc-crosssdk-initial_%.bbappend|  1 +
 .../gcc/gcc-crosssdk-initial_4.9.bbappend  |  1 -
 recipes-devtools/gcc/gcc-crosssdk_%.bbappend   |  1 +
 recipes-devtools/gcc/gcc-crosssdk_4.9.bbappend |  1 -
 recipes-devtools/gcc/gcc-runtime_%.bbappend|  8 ++
 recipes-devtools/gcc/gcc-runtime_4.9.bbappend  |  8 --
 recipes-devtools/gcc/gcc_%.bbappend|  6 ++
 recipes-devtools/gcc/libgcc_%.bbappend |  2 +
 recipes-devtools/gcc/libgcc_4.9.bbappend   |  2 -
 15 files changed, 121 insertions(+), 23 deletions(-)
 create mode 100644 classes/toolchain-scripts-mingw32.bbclass
 create mode 100644 recipes-core/meta/meta-environment.bbappend
 create mode 100644 
recipes-devtools/binutils/binutils-cross-canadian_2.25%.bbappend
 delete mode 100644 
recipes-devtools/binutils/binutils-cross-canadian_2.25.bbappend
 create mode 100644 recipes-devtools/gcc/gcc-cross-canadian_%.bbappend
 delete mode 100644 recipes-devtools/gcc/gcc-cross-canadian_4.9.bbappend
 create mode 100644 recipes-devtools/gcc/gcc-crosssdk-initial_%.bbappend
 delete mode 100644 recipes-devtools/gcc/gcc-crosssdk-initial_4.9.bbappend
 create mode 100644 recipes-devtools/gcc/gcc-crosssdk_%.bbappend
 delete mode 100644 recipes-devtools/gcc/gcc-crosssdk_4.9.bbappend
 create mode 100644 recipes-devtools/gcc/gcc-runtime_%.bbappend
 delete mode 100644 recipes-devtools/gcc/gcc-runtime_4.9.bbappend
 create mode 100644 recipes-devtools/gcc/gcc_%.bbappend
 create mode 100644 recipes-devtools/gcc/libgcc_%.bbappend
 delete mode 100644 recipes-devtools/gcc/libgcc_4.9.bbappend

-- 
1.9.3

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Building yocto with hard float support

2015-11-12 Thread Mark Hatle
On 11/12/15 3:17 AM, Toby Gomersall wrote:
> Hi,
> 
> I want to build yocto with hard float support. I understand that I can
> point the EXTERNAL_TOOLCHAIN variable at the appropriate external hard
> float compiler (gcc-5-arm-linux-gnueabihf). However, I was wondering if
> there was anything within the yocto project to do this?

I'm going to be pedantic for a second.. bear with me.

ARM has two ABIs, the standard EABI which passes floating point values via
integer registers and EABIHF that passes floating point values via floating
point registers.

EABI allows hardware floating point along with neon or any other core specific
optimizations.

EABIHF requires a specific set and size of VFP registers.

The Yocto Project is capable of building for both ABIs with whatever
combinations of optimizations you need.

The ABI and default processor optimization is configured by the 'DEFAULTTUNE'
parameter.  This is typically defined in your machine configuration file, either
explicitly or implicitly via the including of the tune files.


So for example, if you have an ARMv5 CPU you would likely use:

DEFAULTTUNE="armv5e"

This would select ARM EABI, no VFP.

alternatively you could do:

DEFAULTTUNE="armv5e-vfp"

This would select ARM EABI w/ VFP floating point.

OR

(what I think you are actually trying to ask)

DEFAULTTUNE="armv5ehf-vfp"

This would select ARM EABIHF w/ VFP floating point.


So start with your machine and determine which defaulttune (bitbake -e) you have
selected.  Adjust it to a compatible setting for the ABI and processor
optimizations that you wish to use.

> I'm concerned that future updates to an external compiler might affect
> my build and I would prefer to use a method from within the yocto project.

Unless you have a specific need, I don't recommend external compilers.  The
Yocto Project compilers and configurations are well tested and high quality.
While using an external compiler is support by some vendors, it adds complexity
that may not be beneficial.  (Sometimes support and other aspects of commercial
offerings outweigh the complexity..)

> Thank you,
> Toby
> 
> 
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Rsh is not working

2015-11-12 Thread Raghavendra Kakarla
Hi All,


I built RFS for yocto with the enabling of all  the inetutils.


When I boot up the kernel on my board and while running the "rsh  
ls" command i got the "permission denied" error.


But when i run the command "rsh " it successfully login into the 
remote machine.


Could you please help the resolving this issue.


Thanks and Regards,

Raghavendra K.

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Building yocto with hard float support

2015-11-12 Thread Toby Gomersall
Hi,

I want to build yocto with hard float support. I understand that I can
point the EXTERNAL_TOOLCHAIN variable at the appropriate external hard
float compiler (gcc-5-arm-linux-gnueabihf). However, I was wondering if
there was anything within the yocto project to do this?

I'm concerned that future updates to an external compiler might affect
my build and I would prefer to use a method from within the yocto project.

Thank you,
Toby



signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto