[yocto] Error building meta-ide-support; 'SNDCTL_DSP_MAPINBUF' undeclared here

Tue Aug 20 16:51:22 PDT 2013

Hi Bryan,

Probably the simplest way is to archive your whole project directory and for
other user, they can import them to workspace, then do reconfigure and
rebuild based on their cross toolchain setup.

Jessica

-----Original Message-----
From: Bryan Evenson [mailto:bevenson at melinkcorp.com] 
Sent: Monday, August 19, 2013 6:54 AM
To: Zhang, Jessica; yocto at yoctoproject.org
Subject: RE: [yocto] Error building meta-ide-support; 'SNDCTL_DSP_MAPINBUF'
undeclared here

Jessica,

> -----Original Message-----
> From: Zhang, Jessica [mailto:jessica.zhang at intel.com]
> Sent: Thursday, August 15, 2013 5:19 PM
> To: Bryan Evenson; yocto at yoctoproject.org
> Subject: RE: [yocto] Error building meta-ide-support; 
> 'SNDCTL_DSP_MAPINBUF' undeclared here
> 
> Ok, 1st of all just build core-image-minimal won't give you libraries 
> that you'll need to do cross development.  The simplest way to build a 
> cross toolchain and sysroot that match your target image is to do 
> "bitbake core-image-mininal -c populate_sdk".  That'll generate a SDK 
> tarball for you.

For some reason on my setup, the command format "bitbake <recipe-name> -c
<task>" never seems to work.  For example, running "bitbake
core-image-minimal -c populate_sdk" produces the error "nothing PROVIDES
'populate_sdk'".  But, issuing "bitbake -c populate_sdk core-image-minimal"
did build the SDK tarball.

And for my setup, I configured the Yocto ADT preferences as follows:
- Standalone pre-built toolchain
- Toolchain Root Location: <SDK tarball extract location>/opt/poky/1.4.1
- Sysroot Location: <SDK tarball extract location>/opt/poky/1.4.1/sysroots

After these selections were made, then "arm926ejste-poky-linux-gnueabi"
showed up as a Target Architecture option.  I saved these settings and
created a simple project using the steps shown in the ADT manual.  After
some minor modifications to configure.ac and Makefile.am for my source
files, I was able to cross-compile a project for my system.

And just to confirm, what files in the project are needed for someone else
to build my project (assuming their toolchain is setup properly)?  Aside
from my source and header files, I know I need configure.ac, autogen.sh, and
Makefile.am from each directory.  And I also need .project and the .settings
directory for the Eclipse project setup.  Anything else that I am missing?

Thanks,
Bryan

> You can follow the developer's manual on how to extract the tarball, 
> then in eclipse your toolchain location should be the directory you 
> extract the tarball at, and sysroot should be the sysroot directory 
> underneath where you extracted your tar ball.
> 
> - Jessica
> 
> -----Original Message-----
> From: Bryan Evenson [mailto:bevenson at melinkcorp.com]
> Sent: Thursday, August 15, 2013 2:12 PM
> To: Zhang, Jessica; yocto at yoctoproject.org
> Subject: RE: [yocto] Error building meta-ide-support; 
> 'SNDCTL_DSP_MAPINBUF'
> undeclared here
> 
> 
> 
> > -----Original Message-----
> > From: Zhang, Jessica [mailto:jessica.zhang at intel.com]
> > Sent: Thursday, August 15, 2013 4:55 PM
> > To: Bryan Evenson; yocto at yoctoproject.org
> > Subject: RE: [yocto] Error building meta-ide-support; 
> > 'SNDCTL_DSP_MAPINBUF' undeclared here
> >
> > Hi Bryan,
> >
> > When you tried to setup your eclipse plugin, what is your toolchain 
> > and what is your sysroot.  Are they built by you or you download
> them?
> >
> 
> I built my own.  I'm using the meta-atmel layer located at 
> https://github.com/evensonbryan/meta-atmel.git, using the instructions 
> shown in the README to download and build.  Only exception is that I 
> have MACHINE set as "at91sam9x5ek" in local.conf.  I did "bitbake 
> core-image- minimal" as the initial build to start off everything; 
> never tried to bitbake meta-ide-support on this system.
> 
> -Bryan
> 
> > - Jessica
> >
> > -----Original Message-----
> > From: yocto-bounces at yoctoproject.org [mailto:yocto- 
> > bounces at yoctoproject.org] On Behalf Of Bryan Evenson
> > Sent: Tuesday, August 13, 2013 9:25 AM
> > To: yocto at yoctoproject.org
> > Subject: [yocto] Error building meta-ide-support;
> 'SNDCTL_DSP_MAPINBUF'
> > undeclared here
> >
> > I am working on installing and setting up the Eclipse IDE plug-in 
> > for Eclipse Juno.  I am using poky/dylan (at the yocto-1.4.1 tag) 
> > for my build environment.  I am to the "Configuring the 
> > Cross-Compiler Options"
> > section
> > from the current Yocto Project mega-manual, and after setting up the 
> > Toolchain Root Location and the Sysroot Location, I get the error 
> > 'Specified toolchain directory does not contain a toolchain 
> > generated with "bitbake meta-ide-support"'.  So, I went back and did 
> > "bitbake meta-ide-
> support"
> > as
> > requested and I am getting the following errors:
> >
> > DEBUG: Executing shell function do_compile
> > NOTE: make -j 2
> >   CC    arm-linux-user/linux-user/syscall.o
> > In file included from
> > /media/sda3/poky/poky-build/tmp/work/i686-linux/qemu-native/1.4.0-
> > r0/qemu-1.
> > 4.0/linux-user/syscall.c:3705:0:
> > /media/sda3/poky/poky-build/tmp/work/i686-linux/qemu-native/1.4.0-
> > r0/qemu-1.
> > 4.0/linux-user/ioctls.h:189:1: error: 'SNDCTL_DSP_MAPINBUF'
> undeclared
> > here
> > (not in a function)
> > /media/sda3/poky/poky-build/tmp/work/i686-linux/qemu-native/1.4.0-
> > r0/qemu-1.
> > 4.0/linux-user/ioctls.h:190:1: error: 'SNDCTL_DSP_MAPOUTBUF'
> undeclared
> > here
> > (not in a function)
> > /media/sda3/poky/poky-build/tmp/work/i686-linux/qemu-native/1.4.0-
> > r0/qemu-1.
> > 4.0/linux-user/ioctls.h:245:1: error: 'SOUND_MIXER_ACCESS' 
> > undeclared here (not in a function)
> > make[1]: *** [linux-user/syscall.o] Error 1
> > make: *** [subdir-arm-linux-user] Error 2
> > make: *** Waiting for unfinished jobs....
> > ERROR: oe_runmake failed
> > ERROR: Function failed: do_compile (see
> > /media/sda3/poky/poky-build/tmp/work/i686-linux/qemu-native/1.4.0-
> > r0/temp/lo
> > g.do_compile.20276 for further information)
> >
> > I did a search and I cannot find these defines anywhere in the i686 
> > sysroot directory, but it exists in my target's sysroot directory.  
> > Is there something wrong with the i686 sysroot setup on my system?  
> > If it matters, I'm doing the build machine is running Ubuntu 12.04.2 
> > LTS.
> >
> > Thanks,
> > Bryan
> >
> >
> >
> >
> > _______________________________________________
> > yocto mailing list
> > yocto at yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 9626 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20130820/f932b6d1/attachment.bin>