| Welcome to AT91SAM Community Forum http://www.at91.com/samphpbb/ |
|
| Problems building Angstrom for AT91SAM9x5-EK http://www.at91.com/samphpbb/viewtopic.php?f=12&t=20805 |
Page 1 of 1 |
| Author: | otangrot [ Tue Apr 24, 2012 4:25 pm ] |
| Post subject: | Problems building Angstrom for AT91SAM9x5-EK |
I am using Ubuntu 10.04 LTS and is trying to follow the instructions at Linux4SAM to make my own Angstrom build and tool chain. When running bitbake I get the following error which prevents any progress: NOTE: Handling BitBake files: \ (5636/7326) [76 %]ERROR: SRCREV was used yet no valid SCM was found in SRC_URI NOTE: <class 'bb.fetch.ParameterError'>: while evaluating: ${@bb.fetch.get_srcrev(d)} NOTE: <class 'bb.fetch.ParameterError'>: while evaluating: 1.1.0+hgr${SRCPV} NOTE: <class 'bb.fetch.ParameterError'>: while evaluating: ${PN}-${EXTENDPE}${PV}-${PR} NOTE: <class 'bb.fetch.ParameterError'>: while evaluating: ${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PF} NOTE: <class 'bb.fetch.ParameterError'>: while evaluating: ${WORKDIR}/cacao NOTE: <class 'bb.fetch.ParameterError'>: while evaluating: ${S} ERROR: while parsing /home/oloft/oe/openembedded/recipes/cacao/cacao-native_hg.bb I don't really understand why the cacao Java VM is included in the build, if I can remove it or why it fails. But since I can't find any other who has the same problem as me I suspect something is wrong on my build host. Any help to resolve this is appreciated. Olof |
|
| Author: | bevenson [ Tue Apr 24, 2012 8:25 pm ] |
| Post subject: | Re: Problems building Angstrom for AT91SAMx5-EK |
I had a ton of problems getting my initial build working. The first problem I had was following the wrong set of instructions. Make sure you're following the ones here: http://www.at91.com/linux4sam/bin/view/ ... gstrom_9x5. The other problem was I had a typo in my local.conf file and the Bitbake recipe file paths weren't being recognized. Under oe_at91sam/recipes/local.conf, make sure that you have BBFILES set as: Code: BBFILES := "${TOPDIR}/openembedded/recipes/*/*.bb ${TOPDIR}/oe_at91sam/recipes/*/*.bb" and that in oe_at91sam/recipes/site.conf you have BBFILES set as: Code: BBFILES = "${TOPDIR}/openembedded/recipes/*/*.bb ${TOPDIR}/oe_at91sam/recipes/*/*.bb" Then just make sure you bitbake base-image before anything else, because this is needed to create the build environment. If you followed the suggested directory tree, this should be all you need to do. |
|
| Author: | otangrot [ Wed Apr 25, 2012 8:24 am ] |
| Post subject: | Re: Problems building Angstrom for AT91SAMx5-EK |
Thanks for your reply, alas I still get the same fault. I assume TOPDIR is refers to shell variable. I can't find any thing that set it in my environment. I tried using BBPATH set by the oe_env.sh but now I got some other comments about the bitbake version being to low. |
|
| Author: | otangrot [ Wed Apr 25, 2012 8:43 am ] |
| Post subject: | Re: Problems building Angstrom for AT91SAMx5-EK |
Another thing I noticed was this build message: NOTE: Parsing finished. 0 cached, 0 parsed, 0 skipped, 0 masked. NOTE: Cache is clean, not saving. NOTE: build Angstrom ${DISTRO_VERSION}: started Build Configuration: BB_VERSION = "1.8.18" METADATA_BRANCH = "<unknown>" METADATA_REVISION = "<unknown>" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "at91sam9x5ek" DISTRO = "angstrom" DISTRO_VERSION = "v20120425" TARGET_FPU = "soft" This is strange because the oe_at91sam/conf/local.conf sets DISTRO to "angstrom-2010.x" Nor do I understand where bitbake got the value of DISRO_VERSION from. It seems to be todays (!) date. |
|
| Author: | otangrot [ Wed Apr 25, 2012 11:12 am ] |
| Post subject: | Re: Problems building Angstrom for AT91SAM9x5-EK |
I changed the version of bitbake and it is still something wrong in the configuration files. I get this error message now: oloft@ubuntu:~/EmbeddedLinux/oe$ bitbake base-image WARNING: No bb files matched BBFILE_PATTERN_upstream '$(OE_DIR)/openembedded/' WARNING: No bb files matched BBFILE_PATTERN_at91overlay '$(OE_DIR)/oe_at91sam/' Build Configuration: BB_VERSION = "1.12.0" METADATA_BRANCH = "<unknown>" METADATA_REVISION = "<unknown>" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "at91sam9x5ek" DISTRO = "angstrom" DISTRO_VERSION = "v20120425" TARGET_FPU = "soft" ERROR: Nothing PROVIDES 'base-image' ERROR: Command execution failed: Traceback (most recent call last): File "/home/oloft/EmbeddedLinux/oe/bitbake/lib/bb/command.py", line 102, in runAsyncCommand commandmethod(self.cmds_async, self, options) File "/home/oloft/EmbeddedLinux/oe/bitbake/lib/bb/command.py", line 200, in buildTargets command.cooker.buildTargets(pkgs_to_build, task) File "/home/oloft/EmbeddedLinux/oe/bitbake/lib/bb/cooker.py", line 730, in buildTargets taskdata.add_provider(localdata, self.status, k) File "/home/oloft/EmbeddedLinux/oe/bitbake/lib/bb/taskdata.py", line 353, in add_provider self.add_provider_internal(cfgData, dataCache, item) File "/home/oloft/EmbeddedLinux/oe/bitbake/lib/bb/taskdata.py", line 373, in add_provider_internal raise bb.providers.NoProvider(item) NoProvider: base-image I use the OE_DIR set by the oe_env.sh now. But the two warnings indicates that something more (some file?) is expected but I don't understand what. Can anyone explain? |
|
| Author: | bevenson [ Wed Apr 25, 2012 3:12 pm ] |
| Post subject: | Re: Problems building Angstrom for AT91SAM9x5-EK |
Those two warnings that you're getting about "No bb files matched BBFILE_PATTERN..." is what I was getting when I had issues with my local.conf file. Verify your setup as follows: 1. Verify your working directory structure is as shown here: http://www.at91.com/linux4sam/bin/view/ ... oryTree_3x. The directory they have called "stuff" can be called whatever you want (for the purpose of this message, I'll assume you called it "stuff"). But, the directory called "openembedded" MUST be called "openembedded" and the directory called "oe_at91sam" MUST be called "oe_at91sam". 2. The METADATA_BRANCH should be listed as "2011.03-maintenance" and the METADATA_REVISION will be related to the revision that you extracted from the main Git repository. Go to your "openembedded" directory and type Code: git status It should say "On branch 2011.03-maintenance". If not, then you may have made a mistake with obtaining the Open Embedded data from the Git repository.3. To build, be sure you are in your "stuff" directory and then enter at the command line: Code: source oe_env.sh .bitbake base-image 4. In oe_env.sh and in local.conf, be sure you are using curly braces {} around all variable references. For example, here's the contents of my stuff/oe_at91sam/conf/site.conf: Code: BBFILES = "${TOPDIR}/openembedded/recipes/*/*.bb ${TOPDIR}/oe_at91sam/recipes/*/*.bb" And here's the contents of my stuff/oe_at91sam/conf/local.confBBFILE_COLLECTIONS = "upstream at91overlay" BBFILE_PATTERN_upstream = "${TOPDIR}/openembedded/" BBFILE_PRIORITY_upstream = "1" BBFILE_PATTERN_at91overlay = "${TOPDIR}/oe_at91sam/" BBFILE_PRIORITY_at91overlay = "5" Code: # And here's the contents of my stuff/oe_env.sh# OpenEmbedded local configuration file (sample) # # Please visit the Wiki at http://openembedded.org/ for more info. # # # Be SURE to read this file in its entirety and the GettingStarted page on the # wiki before proceeding. # # Once you have done that, remove the line at the end of this # file and build away. # # WARNING: lines starting with a space (' ') will result in parse failures. # Remove '# ' from commented lines to activate them. # # NOTE: Do NOT use $HOME in your paths, BitBake does NOT expand ~ for you. If you # must have paths relative to your homedir use ${HOME} (note the {}'s there # you MUST have them for the variable expansion to be done by BitBake). Your # paths should all be absolute paths (They should all start with a / after # expansion. Stuff like starting with ${HOME} or ${TOPDIR} is ok). # Use this to specify where BitBake should place the downloaded sources into DL_DIR = "${TOPDIR}/oe_sources/" # Delete the line below. Then specify which .bb files to consider for # your build. Typically this will be something like BBFILES = "/path/to/openembedded/recipes/*/*.bb" BBFILES := "${TOPDIR}/openembedded/recipes/*/*.bb ${TOPDIR}/oe_at91sam/recipes/*/*.bb" # Use the BBMASK below to instruct BitBake to _NOT_ consider some .bb files # This is a regular expression, so be sure to get your parenthesis balanced. # BBMASK = "/(nonworking|obsolete)/" # Comment this if your host distribution does not provide the # help2man tool. #ASSUME_PROVIDED += "help2man-native" # Uncomment this if your host distribution has recent enough Linux # Kernel header files. Utilities we use to generate certain types of # target filesystems need somewhat recent header files. # ASSUME_PROVIDED += "linux-libc-headers-native" # Uncomment this if you want to use a prebuilt toolchain. You will need to # provide packages for toolchain and additional libraries yourself. You also # have to set PATH in your environment to make sure BitBake finds additional binaries. # ASSUME_PROVIDED += "virtual/${TARGET_PREFIX}gcc virtual/libc" # Uncomment this if you are building Linux 2.4 Embedix kernels. # i.e. openzaurus-sa-2.4.18 and openzaurus-pxa-2.4.18 - and don't forget # to rename the binaries as instructed in the Wiki. # Most users do not need this anymore thankfully! # ASSUME_PROVIDED += "virtual/arm-linux-gcc-2.95" # Select between multiple alternative providers, if more than one is eligible. PREFERRED_PROVIDERS = "virtual/qte:qte virtual/libqpe:libqpe-opie" PREFERRED_PROVIDERS += " virtual/libsdl:libsdl-x11" PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc-initial:gcc-cross-initial" PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc-intermediate:gcc-cross-intermediate" PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc:gcc-cross" PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}g++:gcc-cross" # Uncomment this to specify where BitBake should create its temporary files. # Note that a full build of everything in OpenEmbedded will take GigaBytes of hard # disk space, so make sure to free enough space. The default TMPDIR is # <build directory>/tmp # Don't use symlinks in in the path to avoid problems # TMPDIR = /usr/local/projects/oetmp # Uncomment this to specify a machine to build for. See the conf directory # for machines currently known to OpenEmbedded. This will automatically take care # of TARGET_ARCH MACHINE ?= "at91sam9x5ek" # Use this to specify the target architecture. Note that this is only # needed when building for a machine not known to OpenEmbedded. Better use # the MACHINE attribute (see above) # TARGET_ARCH = "arm" # Use this to specify the target operating system. The default is "linux", # for a normal linux system with glibc. Set this to "linux-uclibc" if you want # to build a uclibc based system. # Normally the DISTRO of your choosing will take care of this # TARGET_OS = "linux" # TARGET_OS = "linux-uclibc" # Uncomment this to select a distribution policy. See the conf directory # for distributions currently known to OpenEmbedded. # Although it no longer contain version number in the (file-)name # openzaurus-unstable is a so called "versioned" distro, i.e. they # explicitely select specific versions of various packages. # Stay away from unversioned distros unless you really know what you are doing DISTRO = "angstrom-2010.x" # So far, angstrom.conf sets ENABLE_BINARY_LOCALE_GENERATION # to generate binary locale packages at build time using qemu-native and # thereby guarantee i18n support on all devices. If your build breaks on # qemu-native consider disabling ENABLE_BINARY_LOCALE_GENERATION (note that # this breaks i18n on devices with less than 128MB RAM) or installing # a working third-party qemu (e.g. provided by your distribution) and # adding qemu-native to ASSUME_PROVIDED. Caveat emptor, since third-party # qemus lack patches needed to work with various OE targets. # ENABLE_BINARY_LOCALE_GENERATION = "0" # ASSUME_PROVIDED += "qemu-native" # If ENABLE_BINARY_LOCALE_GENERATION is set to "1", you can limit locales # generated to the list provided by GLIBC_GENERATE_LOCALES. This is huge # time-savior for developmental builds. Format: list of locale.encoding pairs # with spaces as separators. # GLIBC_GENERATE_LOCALES = "en_US.UTF-8 en_GB.UTF-8 de_DE.UTF-8" # Uncomment this to select a particular major kernel version if the MACHINE setting # supports more than one major kernel version. Currently this is suported by the # following MACHINE types: poodle, tosa and simpad. # MACHINE_KERNEL_VERSION = "2.6" # Uncomment one of these to build packages during the build process. # This is done automatically if you set DISTRO (see above) # INHERIT = "package_ipk" # INHERIT = "package_tar" # Add the required image file system types below. Valid are # jffs2, tar(.gz|bz2), cpio(.gz), cramfs, ext2(.gz), ext3(.gz), ext4(.gz|.bz2), # squashfs, squashfs-lzma IMAGE_FSTYPES = "jffs2 tar.bz2 ubi ubifs" # Uncomment this if you want to keep the temporary rootfs # directory, this can be useful during development. # (Note that this rootfs is NOT usuable as NFS export.) IMAGE_KEEPROOTFS = "1" # Uncomment this to enable the use of ccache when building. Due to # the nature of our builds this is only helpful in cases when one # is rebuilding a recipe or set of recipes, repeatedly. # CCACHE = "${@bb.which(bb.data.getVar('PATH', d, 1), 'ccache') and 'ccache '}" # Uncomment this to disable the parse cache (not recommended). # CACHE = "" # Uncomment this if you want BitBake to emit debugging output # BBDEBUG = "yes" # Use DEBUG_BUILD to build packages with DEBUG_OPTIMIZATION instead of # FULL_OPTIMIZATION. # # DEBUG_BUILD = "1" # If you want to have unstripped ready-to-debug binaries, set this to "no", # although for debugging you can use automatically produced -dbg packages. # If you need to have completely undebuggable builds, set this to "full", # by default gnu.debuglink section is left in the binaries after stripping, so # this might be useful if you want to have checksum-level binary consistency # across successive builds. # PACKAGE_STRIP = "no" # Uncomment these to build a package such that you can use gprof to profile it. # NOTE: This will only work with 'linux' targets, not # 'linux-uclibc', as uClibc doesn't provide the necessary # object files. Also, don't build glibc itself with these # flags, or it'll fail to build. # # PROFILE_OPTIMIZATION = "-pg" # SELECTED_OPTIMIZATION = "${PROFILE_OPTIMIZATION}" # LDFLAGS =+ "-pg" # Uncomment this to enable parallel make. # This allows make to spawn mutliple processes to take advantage of multiple # processors. Useful on SMP machines. This may break some packages - we're # in the process of marking these so let us know if you find any. PARALLEL_MAKE = "-j 4" # Uncomment to run multiple bitbake threads in parallel. # Bitbake can do multiple jobs in parallel: Its a good idea make use of # all available resources: e.g. to download sources while some other # piece of software is compiled. BB_NUMBER_THREADS = "2" # Uncomment this if you want BitBake to emit the log if a build fails. BBINCLUDELOGS = "yes" # Uncomment this if you want to install shared libraries directly under their SONAME, # rather than installing as the full version and symlinking to the SONAME. # PACKAGE_SNAP_LIB_SYMLINKS = "1" # -- Custom configuration -- # To save space #INHERIT += "rm_work" # Cache values of all SRCREV variables first time it runs #BB_SRCREV_POLICY = "cache" Code: export OE_DIR=${PWD} Compare that to your setup.export BBPATH=${OE_DIR}/oe_at91sam:${OE_DIR}/openembedded if [ -z ${ORG_PATH} ] ; then ORG_PATH=${PATH} export ORG_PATH fi export PATH=${OE_DIR}/bitbake/bin:$PATH if [ -z ${ORG_LD_LIBRARY_PATH} ] ; then ORG_LD_LIBRARY_PATH=${LD_LIBRARY_PATH} export ORG_LD_LIBRARY_PATH fi export LD_LIBRARY_PATH= export LANG=C export BB_ENV_EXTRAWHITE="MACHINE DISTRO ANGSTROM_MODE" 5. When you do get the build working, you'll need a lot of diskspace. I suggest at least 50 GB free in the volume which you are building. If you're tight on space, uncomment the "INHERIT += "rm_work"" line in local.conf. You can get by with 30 GB if you have to that way. |
|
| Author: | otangrot [ Wed Apr 25, 2012 9:42 pm ] |
| Post subject: | Re: Problems building Angstrom for AT91SAM9x5-EK |
I checked points 1-4 on a clean Fedora 16 machine (64-bit) instead of the VM i used earlier in this post: Code: [olof@localhost oe]$ cd openembedded/ [olof@localhost openembedded]$ git status # On branch 2011.03-maintenance nothing to commit (working directory clean) [olof@localhost openembedded]$ cd .. [olof@localhost oe]$ grep BBFILES oe_at91sam/conf/local.conf # your build. Typically this will be something like BBFILES = "/path/to/openembedded/recipes/*/*.bb" BBFILES := "${OE_DIR}/openembedded/recipes/*/*.bb ${OE_DIR}/oe_at91sam/recipes/*/*.bb" [olof@localhost oe]$ grep BBFILES oe_at91sam/conf/site.conf BBFILES = "${OE_DIR}/openembedded/recipes/*/*.bb ${OE_DIR}/oe_at91sam/recipes/*/*.bb" [olof@localhost oe]$ grep BBFILE_PATTERN oe_at91sam/conf/site.conf BBFILE_PATTERN_upstream = "${OE_DIR}/openembedded/" BBFILE_PATTERN_at91overlay = "${OE_DIR}/oe_at91sam/" [olof@localhost oe]$ source ./oe_env.sh [olof@localhost oe]$ echo $OE_DIR /home/olof/oe I still use OE_DIR since there is nothing that sets TOPDIR to a sane value not does your oe_env.sh set it. If you type 'echo $TOPDIR' what is the result? [olof@localhost oe]$ bitbake base-image WARNING: No bb files matched BBFILE_PATTERN_upstream '${OE_DIR}/openembedded/' WARNING: No bb files matched BBFILE_PATTERN_at91overlay '${OE_DIR}/oe_at91sam/' Build Configuration: BB_VERSION = "1.12.0" METADATA_BRANCH = "2011.03-maintenance" METADATA_REVISION = "21613e4" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "at91sam9x5ek" DISTRO = "angstrom" DISTRO_VERSION = "v20120425" TARGET_FPU = "soft" ERROR: Nothing PROVIDES 'base-image' ERROR: Command execution failed: Traceback (most recent call last): File "/home/olof/oe/bitbake/lib/bb/command.py", line 102, in runAsyncCommand commandmethod(self.cmds_async, self, options) File "/home/olof/oe/bitbake/lib/bb/command.py", line 200, in buildTargets command.cooker.buildTargets(pkgs_to_build, task) File "/home/olof/oe/bitbake/lib/bb/cooker.py", line 730, in buildTargets taskdata.add_provider(localdata, self.status, k) File "/home/olof/oe/bitbake/lib/bb/taskdata.py", line 353, in add_provider self.add_provider_internal(cfgData, dataCache, item) File "/home/olof/oe/bitbake/lib/bb/taskdata.py", line 373, in add_provider_internal raise bb.providers.NoProvider(item) NoProvider: base-image Fedora 16 was set up according to http://wiki.openembedded.org/wiki/OEand ... _15_and_16 with the addition of python.ply and python-progressbar required by bitbake. |
|
| Author: | bevenson [ Thu Apr 26, 2012 10:21 pm ] |
| Post subject: | Re: Problems building Angstrom for AT91SAM9x5-EK |
If I'm reading things correctly, TOPDIR is a temporary variable that Bitbake creates and uses. If you haven't already tried it, try switching all your references to OE_DIR to TOPDIR in the places that I have it and give it a try. |
|
| Author: | otangrot [ Fri Apr 27, 2012 5:37 pm ] |
| Post subject: | Re: Problems building Angstrom for AT91SAM9x5-EK |
Hi, thanks for your patience. It sort of builds on the Ubuntu machine now and using TOPDIR do seem to work in that environment. I do still get the warning as shown in the exeprt form the bitbake console screen below. Code: NOTE: Angstrom DOES NOT support fso-apm because regular apmd is good enough | ETA: 00:01:32 NOTE: Angstrom DOES NOT support ipkg because ipkg has been superseded by opkg ETA: 00:01:14 NOTE: Angstrom DOES NOT support bluez-utils because bluez-utils 3.x has been replaced by bluez4 NOTE: Angstrom DOES NOT support libiconv because the glibc builtin iconv replacement is used Parsing recipes: 100% |#####################################################| Time: 00:03:38 Parsing of 7349 .bb files complete (0 cached, 7349 parsed). 7996 targets, 365 skipped, 2 masked, 0 errors. WARNING: No bb files matched BBFILE_PATTERN_upstream '$(TOPDIR)/openembedded/' WARNING: No bb files matched BBFILE_PATTERN_at91overlay '$(TOPDIR)/oe_at91sam/' Build Configuration: BB_VERSION = "1.12.0" METADATA_BRANCH = "2011.03-maintenance" METADATA_REVISION = "21613e4" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "at91sam9x5ek" DISTRO = "angstrom" DISTRO_VERSION = "v20120427" TARGET_FPU = "soft" NOTE: Resolving any missing task censored dependencies So something is definitely broken in the files I down loaded. And as you can see DISTRO is still not was was set in local.conf and DISTRO_VERSION is some ad hoc date. This certainly makes me wonder if what get build is something that will be even partly functional. And I still can't replicate setting up the build environment on the reference machine which annoys me. Updated: I changed to TOPDIR on my Fedora machine and now it builds there too. Oddly the warning mentioned above does not occur. I guess site.conf on my Ubuntu machine is stil messed up somehow. But DISTRO and DISTRO_VERSION is still not what I expect. The checksum in binutils-2.20.1 was wrong and I saw some error about a fault URL flashing by so there are some issues with the recipes from the openembedded release. |
|
| Author: | bevenson [ Mon Apr 30, 2012 2:37 pm ] |
| Post subject: | Re: Problems building Angstrom for AT91SAM9x5-EK |
Quote: WARNING: No bb files matched BBFILE_PATTERN_upstream '$(TOPDIR)/openembedded/' WARNING: No bb files matched BBFILE_PATTERN_at91overlay '$(TOPDIR)/oe_at91sam/' Check your oe_at91sam/conf/site.conf file. Bitbake wants curly braces {} around variables, not parentheses (). I think you have "$(TOPDIR)", not "${TOPDIR}" in your site.conf file. While you're at it, double check your local.conf and your other configuration files to make sure you are using curly braces around all your variables like TOPDIR, OE_DIR, etc. The DISTRO and DISTRO_VERSION are correct. DISTRO is stating that you are building the Angstrom distribution, which is a refinement of Open Embedded. DISTRO_VERSION is the date which you are performing the image build. That will update with the current date every time you do a build. I had the same issue with the binutils checksums. I replaced the checksums in the binutils recipe with the reported checksums from the download. You will also run into one more issue near completion of the image build. udev and bluez4 will both want to provide hid2hci. At least that's the error I had with udev-1.65 and bluez-4.92. This library has moved from udev to bluez. To fix this error: 1. Run "bitbake -c unpack udev". 2. Open udev's Makefile.am in your favorite editor. 3. Remove the section that references hid2hci. It's about 5 or 6 lines. With these fixes you should be able to build images without issues. |
|
| Author: | otangrot [ Thu May 03, 2012 8:46 pm ] |
| Post subject: | Re: Problems building Angstrom for AT91SAM9x5-EK |
Thanks, I can confirm the difference was the use of () instead of {}. I seem to get another less easy fixed problem: Code: make[4]: Entering directory `/home/olof/oe/tmp/work/x86_64-linux/glib-2.0-native-2.28.0-r1/glib-2.28.0/glib' CCLD gtester ./.libs/libglib-2.0.so: undefined reference to `GLIB_MEM_FREE' ./.libs/libglib-2.0.so: undefined reference to `GLIB_SLICE_ALLOC' ./.libs/libglib-2.0.so: undefined reference to `GLIB_MEM_REALLOC' ./.libs/libglib-2.0.so: undefined reference to `GLIB_SLICE_FREE' ./.libs/libglib-2.0.so: undefined reference to `GLIB_MEM_ALLOC' ./.libs/libglib-2.0.so: undefined reference to `GLIB_QUARK_NEW' collect2: ld returned 1 exit status make[4]: *** [gtester] Error 1 Does anyone have a fix for that too? |
|
| Author: | koan [ Fri May 04, 2012 10:35 am ] |
| Post subject: | Re: Problems building Angstrom for AT91SAM9x5-EK |
It's too hard to fix every problem you face to, your patches are welcome though You can also try a supported distro included in OE: http://www.kaeilos.com/download |
|
| Author: | otangrot [ Sat May 05, 2012 2:55 pm ] |
| Post subject: | Re: Problems building Angstrom for AT91SAM9x5-EK |
Is my hardware supported by any distro in OE? I have faild to identify any sofar. |
|
| Author: | koan [ Sat May 05, 2012 4:34 pm ] |
| Post subject: | Re: Problems building Angstrom for AT91SAM9x5-EK |
Actually looks like that Atmel has preferred to create their own overlay in this case. Code: http://www.at91.com/linux4sam/bin/view/Linux4SAM/BuildAngstrom_9x5 This archive contains the configuration files, recipes that will overload the original ones from the OpenEmbedded project. wget ftp://ftp.linux4sam.org/pub/oe/linux4sa ... t91sam.tgz Unfortunately this has to be tested in a fresh build environment. BTW at last you have to set the proper target machine with Code: MACHINE ?= "at91sam9x5ek" P.S. I can offer commercial support for this task if needed. |
|
| Author: | otangrot [ Sun May 06, 2012 8:26 am ] |
| Post subject: | Re: Problems building Angstrom for AT91SAM9x5-EK |
I do try to follow the descriptions on the Linux4SAM site, thought it was obvious from the experpts above. Thanks for the offer but I am poorly funded and my project is more a review of technology maturity and learning. If I had a business deadline I might have considered the bid. Seems like bitbake base-image finnished building on my Fedora machine after this: glibc-2.0_2.28.0.bb changed -EXTRA_OECONF_virtclass-native = "" +EXTRA_OECONF_virtclass-native = "--disable-dtrace --disable-systemtap" The change was inspired by https://lists.yoctoproject.org/pipermai ... 04571.html but I ended up changing another file. I have no clue if this actually will reslut in a stable system in the end. Seems lite the x11-at91sam9-image target doesn't build due to a bluetooth package problem described above. |
|
| Page 1 of 1 | All times are UTC + 1 hour [ DST ] |
| Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/ |
|



Forum