All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: "Ourada, Paul" <Paul.Ourada@Covidien.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: Trying to create OpenDDS recipe
Date: Thu, 28 Jul 2011 14:48:46 -0700	[thread overview]
Message-ID: <4E31D93E.2000606@linux.intel.com> (raw)
In-Reply-To: <2A069A8019B2DF43BD330EE490B1EF527F2A16@TAMANS-BE04.thcg.net>

Hi Paul,

On 07/19/2011 07:41 AM, Ourada, Paul wrote:
> I hope this is the correct place to post this. If not, please let me
> know.

This is the right place. In the future please don't reply to an existing
post as your message then gets threaded with the one you replied to
(likely why you didn't receive a response so far - that I see anyway).

> 
> I'm trying to create a recipe for OpenDDS. The recipe works so far as
> fetching, unpacking, and configuration. Or it seems to. :) Part of the
> configuration piece is that it also pulls down ACE+TAO real-time CORBA.
> This part works fine as well.
> 
> I set S as follows to match the unpacking directories enforced by the
> tar file:
> 
> S = ${WORKINGDIR}/DDS
> 
> The package comes with a configuration script pre-built, and it expects
> to be told where glibc is. So, I write do_configure as follows:
> 
> EXTRA_OECONF = "-glibc=${STAGING_DIR}/${MACHINE}/usr"
> 
> do_configure() {
>     ${S}/configure ${EXTRA_OECONF}
> }
> 
> The problem that I run into is during compilation. I write the following
> for do_compile()
> 
> do_compile() {
>     oenote ${STAGING_DIR}
>     cd ${S} && make
> }

Is there a reason you are overriding configure and compile? These appear
to be autoconf projects, which should just work for recipes using
autotools.bbclass.

> 
> This works right up until there is a compile error in ACE+TAO. Of
> course, I build the entire DDS package, including ACE+TAO, with no
> hiccups in Ubuntu, so I understand that this is a
> cross-compile/environment issue.
> 
> The compile error is that it cannot find features.h, which is clearly in
> ${STAGING_LIBDIR}/${MACHINE}/usr/include. The compile command which is
> being executed is as follows (this is going to be ugly, let me know if
> there's a better way to include this, such as a pastebin somewhere):

This is better - the pastebin isn't as reliable, and having it inline to
review and for future reference is much preferred.

> 
> | make[1]: Entering directory
> `/opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE
> _wrappers/TAO/TAO_IDL'
> | 
> | GNUmakefile:
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/TAO/TAO_IDL/GNUmakefile.TAO_IDL_EXE MAKEFLAGS=w
> | 
> | i586-poky-linux-g++ -march=i586
> --sysroot=/opt/yocto/poky-5.0.1-build/tmp/sysroots/qemux86
> -fvisibility=hidden -fvisibility-inlines-hidden -W -Wall -Wpointer-arith
> -ggdb -pipe -D_REENTRANT -DACE_HAS_AIO_CALLS -D_GNU_SOURCE
> -I/opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/AC
> E_wrappers -DACE_HAS_EXCEPTIONS -DACE_NO_INLINE -I../.. -Iinclude
> -Ibe_include -Ife -I.. -DTAO_IDL_PREPROCESSOR=\"i586-poky-linux-g++
> -march=i586 --sysroot=/opt/yocto/poky-5.0.1-build/tmp/sysroots/qemux86\"
> -c -o .obj/driver/drv_preproc.o driver/drv_preproc.cpp
> | <command-line>:0:22: warning: missing terminating " character
> | In file included from
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/ace/config-linux-common.h:30:0,
> |                  from
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/ace/config-linux.h:14,
> |                  from
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/ace/config.h:1,
> |                  from
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/ace/config-macros.h:24,
> |                  from
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/ace/config-lite.h:24,
> |                  from
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/ace/os_include/os_limits.h:21,
> |                  from include/idl_defines.h:70,
> |                  from driver/drv_preproc.cpp:70:
> |
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE_
> wrappers/ace/config-posix.h:7:20: fatal error: unistd.h: No such file or
> directory

Do you see unistd.h under /opt/yocto/poky-5.0.1-build/tmp/sysroots/qemux86 ?


> | compilation terminated.
> | make[1]: *** [.obj/driver/drv_preproc.o] Error 1
> | make[1]: Leaving directory
> `/opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/ACE
> _wrappers/TAO/TAO_IDL'
> | make: *** [TAO_IDL_EXE] Error 2
> | ERROR: Function 'do_compile' failed (see
> /opt/yocto/poky-5.0.1-build/tmp/work/i586-poky-linux/opendds-2.3-r0/temp
> /log.do_compile.17412 for further information)
> NOTE: package opendds-2.3-r0: task do_compile: Failed
> ERROR: Task 5
> (/opt/yocto/poky-bernard-5.0.1/meta/recipes-middleware/opendds/opendds_2
> .3.bb, do_compile) failed with exit code '1'
> 
> The thing that is puzzling me is that --sysroot seems to be pointing in
> the general direction of ${STAGING_DIR} and so the include directive,
> #include <features.h> should be good. I have checked, and features.h is
> in the /usr/include subdirectory there.

I see unistd.h missing, not features.h.

--
Darren

> 
> Does anyone have a clue they could lend me?
> 
> Thanks,
> 
> Paul E. Ourada
> Sr. Principal Software Engineer
> Covidien, Energy-based Devices
> 5920 Longbow Drive
> Boulder, CO 80301
> paul.ourada@covidien.com
> www.covidien.com
> Main: 303-530-2300
> Ofc: 303-581-6940
> Fax: 303-581-6741
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2011-07-28 21:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-19  5:21 [PATCH 0/5] Add support for PowerPC e500v2/SPE Kumar Gala
2011-07-19  5:21 ` [PATCH 1/5] gcc: Add gcc configure for PowerPC e500v2/SPE embedded floating point ABI Kumar Gala
2011-07-19  5:21   ` [PATCH 2/5] tclibc-*glibc: Utilize TARGET_FPU for gnuspe setting Kumar Gala
2011-07-19  5:21     ` [PATCH 3/5] tune-ppce500v2: Add a tune file for PowerPC e500v2 cores Kumar Gala
2011-07-19  5:21       ` [PATCH 4/5] openssl: Add handling for linux-gnuspe-powerpc Kumar Gala
2011-07-19  5:21         ` [PATCH 5/5] flac: fix build issues with e500v2 (gnuspe) toolchain Kumar Gala
2011-07-19  6:01       ` [PATCH 3/5] tune-ppce500v2: Add a tune file for PowerPC e500v2 cores Khem Raj
2011-07-19  6:25         ` Kumar Gala
2011-07-19  6:08     ` [PATCH 2/5] tclibc-*glibc: Utilize TARGET_FPU for gnuspe setting Khem Raj
2011-07-19  6:28       ` Kumar Gala
2011-07-19  6:04   ` [PATCH 1/5] gcc: Add gcc configure for PowerPC e500v2/SPE embedded floating point ABI Khem Raj
2011-07-19  6:47     ` Kumar Gala
2011-07-19 14:07       ` [yocto] " Kumar Gala
2011-07-19 14:07         ` Kumar Gala
2011-07-19 14:41         ` Trying to create OpenDDS recipe Ourada, Paul
2011-07-28 21:48           ` Darren Hart [this message]
2011-07-28 23:16             ` Ourada, Paul
2011-07-29  0:00               ` Darren Hart
2011-07-19 15:02       ` [PATCH 1/5] gcc: Add gcc configure for PowerPC e500v2/SPE embedded floating point ABI Khem Raj
2011-07-19  6:00 ` [PATCH 0/5] Add support for PowerPC e500v2/SPE Khem Raj
2011-07-19  7:44 ` Koen Kooi
2011-07-19 13:17   ` Kumar Gala
2011-07-19 15:32     ` Saul Wold
2011-07-19 15:40       ` Kumar Gala
2011-07-19 15:42         ` Saul Wold

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=4E31D93E.2000606@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=Paul.Ourada@Covidien.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.