From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: b29882@freescale.com
Subject: Re: [PATCH v2] lsof: define linux C library type when using eglibc
Date: Tue, 17 Jul 2012 09:55:28 -0700 [thread overview]
Message-ID: <50059900.6050608@linux.intel.com> (raw)
In-Reply-To: <1342156465-15052-1-git-send-email-b28495@freescale.com>
On 07/12/2012 10:14 PM, b28495@freescale.com wrote:
> From: Ting Liu <b28495@freescale.com>
>
> lsof tries to compile a temp c source file and execute the binary to
> determine linux C library type (file Configure, line 2689-2717).
> It is inpracticable for cross-compilation and may have build issue on
> some distros since it depends on host settings.
>
> Fix below error when building for 64bit target on 64bit host:
> [...]
> | dsock.c:481:44: error: 'TCP_LISTEN' undeclared (first use in this function)
> | dsock.c:482:45: error: 'TCP_CLOSING' undeclared (first use in this function)
> [...]
> | make: *** [dsock.o] Error 1
>
> The actual issue exists in do_configure:
> [...]
> Testing C library type with cc ... done
> Cannot determine C library type; assuming it is not glibc.
>
> Which is in turn caused by missing 'gnu/stubs-32.h" when compiling
> the temp c source file on host:
> [...]
> fatal error: gnu/stubs-32.h: No such file or directory compilation terminated.
>
> file gnu/stubs-32.h is provided by 32bit glibc.
>
> Signed-off-by: Ting Liu <b28495@freescale.com>
> ---
> meta/recipes-extended/lsof/lsof_4.85.bb | 7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-extended/lsof/lsof_4.85.bb b/meta/recipes-extended/lsof/lsof_4.85.bb
> index 5823725..de7ff68 100644
> --- a/meta/recipes-extended/lsof/lsof_4.85.bb
> +++ b/meta/recipes-extended/lsof/lsof_4.85.bb
> @@ -3,7 +3,7 @@ DESCRIPTION = "Lsof is a Unix-specific diagnostic tool. \
> Its name stands for LiSt Open Files, and it does just that."
> SECTION = "devel"
> LICENSE = "BSD"
> -PR = "r1"
> +PR = "r2"
>
> SRC_URI = "ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_${PV}.tar.bz2"
>
> @@ -31,6 +31,11 @@ export LSOF_INCLUDE = "${STAGING_INCDIR}"
> do_configure () {
> export LSOF_AR="${AR} cr"
> export LSOF_RANLIB="${RANLIB}"
> + if [ "x${EGLIBCVERSION}" != "x" ];then
> + LINUX_CLIB=`echo ${EGLIBCVERSION} |sed -e 's,\.,,g'`
> + LINUX_CLIB="-DGLIBCV=${LINUX_CLIB}"
> + export LINUX_CLIB
> + fi
> yes | ./Configure ${LSOF_OS}
> }
>
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-07-17 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 5:14 [PATCH v2] lsof: define linux C library type when using eglibc b28495
2012-07-17 16:55 ` Saul Wold [this message]
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=50059900.6050608@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=b29882@freescale.com \
--cc=openembedded-core@lists.openembedded.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.