thanx Dalon
kernel complied by editing this line.
my main task was to add net snmp in yocto .for this purpose i added this
line in local.conf .by after compliation (i got no error or warning
related to snmp) .no snmp founld in rootfs generated by bibake??
IMAGE_INSTALL+="net-snmp-server net-snmp-client net-snmp-libs net-snmp-mibs"
this line i added in local conf.
> i spoke too soon, this appears to occur when building the image. i
> initially tested just the kernel build. Changing
>
> to
>
> PACKAGE_CLASSES ?= "package_ipk"
>
> does get you much further on in the compile.
>
> Thanks,
> Dalon
>
> On Tue, Jun 21, 2016 at 12:21 PM, Dalon Westergreen <dwest...@gmail.com>
> wrote:
>
>> i dont see any issues with your local.conf. it matches mine aside from
>> mine specifying the 4.1 ltsi kernel. I suspect this could be a host
>> machine config issue, and will refer you to the yocto documentation for
>> jethro.
>>
>> --dalon
>>
>>
>> On Tue, Jun 21, 2016 at 10:20 AM, <sandeepk_si...@bel.co.in> wrote:
>>
>>> hii my local conf is
>>> /////////////////////////////
>>> #
>>> # This file is your local configuration file and is where all local
>>> user
>>> settings
>>> # are placed. The comments in this file give some guide to the options
>>> a
>>> new user
>>> # to the system might want to change but pretty much any configuration
>>> option can
>>> # be set in this file. More adventurous users can look at
>>> local.conf.extended
>>> # which contains other examples of configuration which can be placed in
>>> this file
>>> # but new users likely won't need any of them initially.
>>> #
>>> # Lines starting with the '#' character are commented out and in some
>>> cases the
>>> # default values are provided as comments to show people example
>>> syntax.
>>> Enabling
>>> # the option is a question of removing the # character and making any
>>> change to the
>>> # variable as required.
>>>
>>> #
>>> # Machine Selection
>>> #
>>> # You need to select a specific machine to target the build with. There
>>> are a selection
>>> # of emulated machines available which can boot and run in the QEMU
>>> emulator:
>>> #
>>> MACHINE="cyclone5"
>>> #MACHINE ?= "qemuarm"
>>> #MACHINE ?= "qemuarm64"
>>> #MACHINE ?= "qemumips"
>>> #MACHINE ?= "qemuppc"
>>> #MACHINE ?= "qemux86"
>>> #MACHINE ?= "qemux86-64"
>>> #
>>> # There are also the following hardware board target machines included
>>> for
>>> # demonstration purposes:
>>> #
>>> #MACHINE ?= "beaglebone"
>>> #MACHINE ?= "genericx86"
>>> #MACHINE ?= "genericx86-64"
>>> #MACHINE ?= "mpc8315e-rdb"
>>> #MACHINE ?= "edgerouter"
>>> #
>>> # This sets the default machine to be qemux86 if no other machine is
>>> selected:
>>> MACHINE ??= "qemux86"
>>>
>>> #
>>> # Where to place downloads
>>> #
>>> # During a first build the system will download many different source
>>> code
>>> tarballs
>>> # from various upstream projects. This can take a while, particularly
>>> if
>>> your network
>>> # connection is slow. These are all stored in DL_DIR. When wiping and
>>> rebuilding you
>>> # can preserve this directory to speed up this part of subsequent
>>> builds.
>>> This directory
>>> # is safe to share between multiple builds on the same machine too.
>>> #
>>> # The default is a downloads directory under TOPDIR which is the build
>>> directory.
>>> #
>>> #DL_DIR ?= "${TOPDIR}/downloads"
>>>
>>> #
>>> # Where to place shared-state files
>>> #
>>> # BitBake has the capability to accelerate builds based on previously
>>> built output.
>>> # This is done using "shared state" files which can be thought of as
>>> cache
>>> objects
>>> # and this option determines where those files are placed.
>>> #
>>> # You can wipe out TMPDIR leaving this directory intact and the build
>>> would regenerate
>>> # from these files if no changes were made to the configuration. If
>>> changes were made
>>> # to the configuration, only shared state files where the state was
>>> still
>>> valid would
>>> # be used (done using checksums).
>>> #
>>> # The default is a sstate-cache directory under TOPDIR.
>>> #
>>> #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
>>>
>>> #
>>> # Where to place the build output
>>> #
>>> # This option specifies where the bulk of the building work should be
>>> done
>>> and
>>> # where BitBake should place its temporary files and output. Keep in
>>> mind
>>> that
>>> # this includes the extraction and compilation of many applications and
>>> the toolchain
>>> # which can use Gigabytes of hard disk space.
>>> #
>>> # The default is a tmp directory under TOPDIR.
>>> #
>>> #TMPDIR = "${TOPDIR}/tmp"
>>>
>>> #
>>> # Default policy config
>>> #
>>> # The distribution setting controls which policy settings are used as
>>> defaults.
>>> # The default value is fine for general Yocto project use, at least
>>> initially.
>>> # Ultimately when creating custom policy, people will likely end up
>>> subclassing
>>> # these defaults.
>>> #
>>> DISTRO ?= "poky"
>>> # As an example of a subclass there is a "bleeding" edge policy
>>> configuration
>>> # where many versions are set to the absolute latest code from the
>>> upstream
>>> # source control systems. This is just mentioned here as an example,
>>> its
>>> not
>>> # useful to most new users.
>>> # DISTRO ?= "poky-bleeding"
>>>
>>> #
>>> # Package Management configuration
>>> #
>>> # This variable lists which packaging formats to enable. Multiple
>>> package
>>> backends
>>> # can be enabled at once and the first item listed in the variable will
>>> be
>>> used
>>> # to generate the root filesystems.
>>> # Options are:
>>> # - 'package_deb' for debian style deb files
>>> # - 'package_ipk' for ipk files are used by opkg (a debian style
>>> embedded
>>> package manager)
>>> # - 'package_rpm' for rpm style packages
>>> # E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
>>> # We default to rpm:
>>> PACKAGE_CLASSES ?= "package_rpm"
>>>
>>> #
>>> # SDK/ADT target architecture
>>> #
>>> # This variable specifies the architecture to build SDK/ADT items for
>>> and
>>> means
>>> # you can build the SDK packages for architectures other than the
>>> machine
>>> you are
>>> # running the build on (i.e. building i686 packages on an x86_64 host).
>>> # Supported values are i686 and x86_64
>>> #SDKMACHINE ?= "i686"
>>>
>>> #
>>> # Extra image configuration defaults
>>> #
>>> # The EXTRA_IMAGE_FEATURES variable allows extra packages to be added
>>> to
>>> the generated
>>> # images. Some of these options are added to certain image types
>>> automatically. The
>>> # variable can contain the following options:
>>> # "dbg-pkgs" - add -dbg packages for all installed packages
>>> # (adds symbol information for debugging/profiling)
>>> # "dev-pkgs" - add -dev packages for all installed packages
>>> # (useful if you want to develop against libs in
>>> the
>>> image)
>>> # "ptest-pkgs" - add -ptest packages for all ptest-enabled
>>> packages
>>> # (useful if you want to run the package test
>>> suites)
>>> # "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
>>> # "tools-debug" - add debugging tools (gdb, strace)
>>> # "eclipse-debug" - add Eclipse remote debugging support
>>> # "tools-profile" - add profiling tools (oprofile, exmap, lttng,
>>> valgrind)
>>> # "tools-testapps" - add useful testing tools (ts_print, aplay,
>>> arecord
>>> etc.)
>>> # "debug-tweaks" - make an image suitable for development
>>> # e.g. ssh root access has a blank password
>>> # There are other application targets that can be used here too, see
>>> # meta/classes/image.bbclass and meta/classes/core-image.bbclass for
>>> more
>>> details.
>>> # We default to enabling the debugging tweaks.
>>> EXTRA_IMAGE_FEATURES = "debug-tweaks"
>>>
>>> #
>>> # Additional image features
>>> #
>>> # The following is a list of additional classes to use when building
>>> images which
>>> # enable extra features. Some available options which can be included
>>> in
>>> this variable
>>> # are:
>>> # - 'buildstats' collect build statistics
>>> # - 'image-mklibs' to reduce shared library files size for an image
>>> # - 'image-prelink' in order to prelink the filesystem image
>>> # - 'image-swab' to perform host system intrusion detection
>>> # NOTE: if listing mklibs & prelink both, then make sure mklibs is
>>> before
>>> prelink
>>> # NOTE: mklibs also needs to be explicitly enabled for a given image,
>>> see
>>> local.conf.extended
>>> # NOTE: image-prelink is currently broken due to problems with the
>>> prelinker. It is advised
>>> # that you do NOT run the prelinker at this time.
>>> USER_CLASSES ?= "buildstats image-mklibs"
>>>
>>> #
>>> # Runtime testing of images
>>> #
>>> # The build system can test booting virtual machine images under qemu
>>> (an
>>> emulator)
>>> # after any root filesystems are created and run tests against those
>>> images. To
>>> # enable this uncomment this line. See classes/testimage(-auto).bbclass
>>> for
>>> # further details.
>>> #TEST_IMAGE = "1"
>>> #
>>> # Interactive shell configuration
>>> #
>>> # Under certain circumstances the system may need input from you and to
>>> do
>>> this it
>>> # can launch an interactive shell. It needs to do this since the build
>>> is
>>> # multithreaded and needs to be able to handle the case where more than
>>> one parallel
>>> # process may require the user's attention. The default is iterate over
>>> the available
>>> # terminal types to find one that works.
>>> #
>>> # Examples of the occasions this may happen are when resolving patches
>>> which cannot
>>> # be applied, to use the devshell or the kernel menuconfig
>>> #
>>> # Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE
>>> 3.x
>>> only), none
>>> # Note: currently, Konsole support only works for KDE 3.x due to the
>>> way
>>> # newer Konsole versions behave
>>> #OE_TERMINAL = "auto"
>>> # By default disable interactive patch resolution (tasks will just fail
>>> instead):
>>> PATCHRESOLVE = "noop"
>>>
>>> #
>>> # Disk Space Monitoring during the build
>>> #
>>> # Monitor the disk space during the build. If there is less that 1GB of
>>> space or less
>>> # than 100K inodes in any key build location (TMPDIR, DL_DIR,
>>> SSTATE_DIR),
>>> gracefully
>>> # shutdown the build. If there is less that 100MB or 1K inodes, perform
>>> a
>>> hard abort
>>> # of the build. The reason for this is that running completely out of
>>> space can corrupt
>>> # files and damages the build in ways which may not be easily
>>> recoverable.
>>> # It's necesary to monitor /tmp, if there is no space left the build
>>> will
>>> fail
>>> # with very exotic errors.
>>> BB_DISKMON_DIRS = "\
>>> STOPTASKS,${TMPDIR},1G,100K \
>>> STOPTASKS,${DL_DIR},1G,100K \
>>> STOPTASKS,${SSTATE_DIR},1G,100K \
>>> STOPTASKS,/tmp,100M,100K \
>>> ABORT,${TMPDIR},100M,1K \
>>> ABORT,${DL_DIR},100M,1K \
>>> ABORT,${SSTATE_DIR},100M,1K \
>>> ABORT,/tmp,10M,1K"
>>>
>>> #
>>> # Shared-state files from other locations
>>> #
>>> # As mentioned above, shared state files are prebuilt cache data
>>> objects
>>> which can
>>> # used to accelerate build time. This variable can be used to configure
>>> the system
>>> # to search other mirror locations for these objects before it builds
>>> the
>>> data itself.
>>> #
>>> # This can be a filesystem directory, or a remote url such as http or
>>> ftp.
>>> These
>>> # would contain the sstate-cache results from previous builds (possibly
>>> from other
>>> # machines). This variable works like fetcher MIRRORS/PREMIRRORS and
>>> points to the
>>> # cache locations to check for the shared objects.
>>> # NOTE: if the mirror uses the same structure as SSTATE_DIR, you need
>>> to
>>> add PATH
>>> # at the end as shown in the examples below. This will be substituted
>>> with
>>> the
>>> # correct path within the directory structure.
>>> #SSTATE_MIRRORS ?= "\
>>> #file://.*
>>> http://someserver.tld/share/sstate/PATH;downloadfilename=PATH
>>> \n \
>>> #file://.* file:///some/local/dir/sstate/PATH"
>>>
>>>
>>> #
>>> # Qemu configuration
>>> #
>>> # By default qemu will build with a builtin VNC server where graphical
>>> output can be
>>> # seen. The two lines below enable the SDL backend too. By default
>>> libsdl-native will
>>> # be built, if you want to use your host's libSDL instead of the
>>> minimal
>>> libsdl built
>>> # by libsdl-native then uncomment the ASSUME_PROVIDED line below.
>>> PACKAGECONFIG_append_pn-qemu-native = " sdl"
>>> PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
>>> #ASSUME_PROVIDED += "libsdl-native"
>>> GCCVERSION="linaro-5.2"
>>> DEFAULTTUNE="cortexa9hf-neon"
>>> PREFERRED_PROVIDER_virtual/kernel="linux-altera"
>>> PREFERRED_VERSION_linux-altera="4.2%"
>>>
>>> IMAGE_INSTALL+="net-snmp-server net-snmp-client net-snmp-libs
>>> net-snmp-mibs"
>>> # CONF_VERSION is increased each time build/conf/ changes incompatibly
>>> and
>>> is used to
>>> # track the version of this file when it was generated. This can safely
>>> be
>>> ignored if
>>> # this doesn't mean anything to you.
>>> CONF_VERSION = "1"
>>>
>>>
>>> ////////////////////
>>> > why is it trying to create rpms? the default is ipks.
>>> >
>>> > /home/san/build/tmp/work/cortexa9hf-vfp-neon-poky-
>>> > linux-gnueabi/libgcc/linaro-5.2-r2015.11-2/temp/log.do_
>>> > package_write_rpm.5391
>>> >
>>> > please attach or share your local.conf.
>>> >
>>> > On Tue, Jun 21, 2016 at 8:03 AM, <sandeepk_si...@bel.co.in> wrote:
>>> >
>>> >> hii
>>> >>
>>> >> i followed instruction for building yocto with meta altera .but i
>>> got
>>> >> some
>>> >> error
>>> >>
>>> >>
>>> >>
>>> >> san@san-VirtualBox:~/build$ bitbake virtual/bootloader
>>> >>
>>> >> Loading cache: 100% |###########################################|
>>> ETA:
>>> >> 00:00:00
>>> >> Loaded 1405 entries from dependency cache.
>>> >> Parsing recipes: 100% |#########################################|
>>> Time:
>>> >> 00:00:15
>>> >> Parsing of 959 .bb files complete (951 cached, 8 parsed). 1412
>>> targets,
>>> >> 65
>>> >> skipped, 0 masked, 0 errors.
>>> >> NOTE: Resolving any missing task queue dependencies
>>> >>
>>> >> Build Configuration:
>>> >> BB_VERSION = "1.28.0"
>>> >> BUILD_SYS = "i686-linux"
>>> >> NATIVELSBSTRING = "Ubuntu-12.04"
>>> >> TARGET_SYS = "arm-poky-linux-gnueabi"
>>> >> MACHINE = "cyclone5"
>>> >> DISTRO = "poky"
>>> >> DISTRO_VERSION = "2.0.2"
>>> >> TUNE_FEATURES = "arm armv7a vfp neon callconvention-hard
>>> cortexa9"
>>> >> TARGET_FPU = "vfp-neon"
>>> >> meta
>>> >> meta-yocto
>>> >> meta-yocto-bsp =
>>> "jethro:ddbc13155f4db5d98976dc93b586c0be4fc740d1"
>>> >> meta-altera =
>>> "jethro:0bf4195d09e23007c2b5a6a365dffa8ec5d518d3"
>>> >> meta-linaro-toolchain =
>>> >> "jethro:7390e4fd59f547f83efe128cb7040ad7c2da0d40"
>>> >>
>>> >> NOTE: Preparing RunQueue
>>> >> NOTE: Executing SetScene Tasks
>>> >> NOTE: Executing RunQueue Tasks
>>> >> ERROR: Function failed: BUILDSPEC (log file is located at
>>> >>
>>> >>
>>> /home/san/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/libgcc/linaro-5.2-r2015.11-2/temp/log.do_package_write_rpm.5391)
>>> >> ERROR: Logfile of failure stored in:
>>> >>
>>> >>
>>> /home/san/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/libgcc/linaro-5.2-r2015.11-2/temp/log.do_package_write_rpm.5391
>>> >> Log data follows:
>>> >> | DEBUG: Executing python function sstate_task_prefunc
>>> >> | DEBUG: Python function sstate_task_prefunc finished
>>> >> | DEBUG: Executing python function do_package_write_rpm
>>> >> | DEBUG: Executing python function read_subpackage_metadata
>>> >> | DEBUG: Python function read_subpackage_metadata finished
>>> >> | DEBUG: Executing python function do_package_rpm
>>> >> | DEBUG: Executing python function write_specfile
>>> >> | NOTE: Creating RPM package for libgcc1
>>> >> | NOTE: Creating RPM package for libgcc-s-dev
>>> >> | NOTE: Creating RPM package for libgcc-s-dbg
>>> >> | DEBUG: Python function write_specfile finished
>>> >> | DEBUG: PKGWRITEDIR:
>>> >>
>>> >>
>>> /home/san/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/libgcc/linaro-5.2-r2015.11-2/deploy-rpms/cortexa9hf_vfp_neon
>>> >> | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common',
>>> 'arm-32',
>>> >> 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi',
>>> >> 'common']
>>> >> | DEBUG: Executing shell function BUILDSPEC
>>> >> | error: line 4: invalid tag value("^[A-Za-z0-9+._]+$") Release:
>>> >> Release:
>>> >> r2015.11-2
>>> >> | error: Package has no %description:
>>> >> libgcc-linaro+5.2.cortexa9hf_vfp_neon
>>> >> | Building target platforms: cortexa9hf_vfp_neon-poky-linux-gnueabi
>>> >> | WARNING: exit code 1 from a shell command.
>>> >> | DEBUG: Python function do_package_rpm finished
>>> >> | DEBUG: Python function do_package_write_rpm finished
>>> >> | ERROR: Function failed: BUILDSPEC (log file is located at
>>> >>
>>> >>
>>> /home/san/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/libgcc/linaro-5.2-r2015.11-2/temp/log.do_package_write_rpm.5391)
>>> >> ERROR: Task 171
>>> >> (/home/san/poky/meta-linaro/meta-linaro-toolchain/recipes-devtools/gcc/
>>> >> libgcc_linaro-5.2.bb,
>>> >> do_package_write_rpm) failed with exit code '1'
>>> >> NOTE: Tasks Summary: Attempted 350 tasks of which 346 didn't need to
>>> be
>>> >> rerun and 1 failed.
>>> >> No currently running tasks (349 of 358)
>>> >>
>>> >> Summary: 1 task failed:
>>> >>
>>> /home/san/poky/meta-linaro/meta-linaro-toolchain/recipes-devtools/gcc/
>>> >> libgcc_linaro-5.2.bb,
>>> >> do_package_write_rpm
>>> >> Summary: There was 1 WARNING message shown.
>>> >> Summary: There was 1 ERROR message shown, returning a non-zero exit
>>> >> code.
>>> >> san@san-VirtualBox:~/build$
>>> >>
>>> >>
>>> >>
>>> >> anybody have any idea whats going wrong in bitbake??
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> संदीप सिंह / Sandeep Singh
>>> >> वरिष्ठ अभियंता (वि एवं
>>> अभि.) /
>>> >> SE (D&E)
>>> >> भारत इलेक्ट्रॉनिक्स
>>> >> लिमिटेड / Bharat Electronics Ltd.
>>> >> कोटद्वार/ Kotdwara – 246149
>>> >> उतारखंड /UttaraKhand
>>> >> भारत / India
>>> >> दूरभाष / Phone: 01382 – 236720
>>> >>
>>> >>
>>> >>
>>> >> Every 3000 Sheets of paper costs us a tree.. Save trees... Conserve
>>> >> Trees. Don't print this email or any Files unless you really need
>>> to!!!!
>>> >> Confidentiality Notice
>>> >>
>>> >> The information contained in this electronic message and any
>>> >> attachments to this message are intended for the exclusive use of
>>> >> the addressee(s) and may contain confidential or privileged
>>> >> information. If you are not the intended recipient, please notify
>>> >> the sender at Bharat Electronics or supp...@bel.co.in immediately
>>> >> and destroy all copies of this message and any attachments.
>>> >>
>>> >> _______________________________________________
>>> >> Rfi mailing list
>>> >> Rfi@lists.rocketboards.org
>>> >> http://lists.rocketboards.org/cgi-bin/mailman/listinfo/rfi
>>> >>
>>> >
>>>
>>>
>>> संदीप सिंह / Sandeep Singh
>>> वरिष्ठ अभियंता (वि एवं अभि.)
>>> /
>>> SE (D&E)
>>> भारत इलेक्ट्रॉनिक्स
>>> लिमिटेड / Bharat Electronics Ltd.
>>> कोटद्वार/ Kotdwara – 246149
>>> उतारखंड /UttaraKhand
>>> भारत / India
>>> दूरभाष / Phone: 01382 – 236720
>>>
>>>
>>>
>>> Every 3000 Sheets of paper costs us a tree.. Save trees... Conserve
>>> Trees. Don't print this email or any Files unless you really need
>>> to!!!!
>>> Confidentiality Notice
>>>
>>> The information contained in this electronic message and any
>>> attachments to this message are intended for the exclusive use of
>>> the addressee(s) and may contain confidential or privileged
>>> information. If you are not the intended recipient, please notify
>>> the sender at Bharat Electronics or supp...@bel.co.in immediately
>>> and destroy all copies of this message and any attachments.
>>>
>>>
>>
>
संदीप सिंह / Sandeep Singh
वरिष्ठ अभियंता (वि एवं अभि.) /
SE (D&E)
भारत इलेक्ट्रॉनिक्स
लिमिटेड / Bharat Electronics Ltd.
कोटद्वार/ Kotdwara – 246149
उतारखंड /UttaraKhand
भारत / India
दूरभाष / Phone: 01382 – 236720
Every 3000 Sheets of paper costs us a tree.. Save trees... Conserve
Trees. Don't print this email or any Files unless you really need to!!!!
Confidentiality Notice
The information contained in this electronic message and any
attachments to this message are intended for the exclusive use of
the addressee(s) and may contain confidential or privileged
information. If you are not the intended recipient, please notify
the sender at Bharat Electronics or supp...@bel.co.in immediately
and destroy all copies of this message and any attachments.
_______________________________________________
Rfi mailing list
Rfi@lists.rocketboards.org
http://lists.rocketboards.org/cgi-bin/mailman/listinfo/rfi
