From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lsof: fix "'TCP_*' undeclared" build errors
Date: Fri, 2 May 2014 17:29:44 +0200 (CEST) [thread overview]
Message-ID: <61985964.1908854.1399044584132.JavaMail.zimbra@advansee.com> (raw)
In-Reply-To: <1399042764-22388-2-git-send-email-benoit.thebaudeau@advansee.com>
On Friday, May 2, 2014 4:59:24 PM, Beno?t Th?baudeau wrote:
> With some configurations, cross-building lsof results in the following
> errors:
FYI, I had this issue on 64-bit Ubuntu 13.10, building with a custom
cross-toolchain for ARM926EJ-S based on Linaro 2011.08 4.5.4 20110808 and EGLIBC
2.13 and generated using crosstool-NG hg_default at 2617_41bd6777fa4f.
[...]
> diff --git a/package/lsof/lsof.mk b/package/lsof/lsof.mk
> index aa101e4..66d2133 100644
> --- a/package/lsof/lsof.mk
> +++ b/package/lsof/lsof.mk
> @@ -47,7 +47,8 @@ endef
> define LSOF_CONFIGURE_CMDS
> (cd $(@D) ; \
> echo n | $(TARGET_CONFIGURE_OPTS) DEBUG="$(TARGET_CFLAGS)
> $(BR2_LSOF_CFLAGS)" \
> - LSOF_INCLUDE="$(STAGING_DIR)/usr/include" LSOF_CFLAGS_OVERRIDE=1
> ./Configure linux)
> + LSOF_INCLUDE="$(STAGING_DIR)/usr/include" LSOF_CFLAGS_OVERRIDE=1 \
> + LSOF_CC="cc --sysroot $(STAGING_DIR)" ./Configure linux)
It'd be better if $(STAGING_DIR) were quoted.
> $(LSOF_CONFIGURE_WCHAR_FIXUPS)
> $(LSOF_CONFIGURE_LOCALE_FIXUPS)
> endef
> --
> 1.8.3.2
>
>
Beno?t
next prev parent reply other threads:[~2014-05-02 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 14:59 [Buildroot] [PATCH] lsof: do not remove WIDECHARINCL definition Benoît Thébaudeau
2014-05-02 14:59 ` [Buildroot] [PATCH] lsof: fix "'TCP_*' undeclared" build errors Benoît Thébaudeau
2014-05-02 15:29 ` Benoît Thébaudeau [this message]
2014-05-02 15:50 ` Benoît Thébaudeau
2014-05-02 16:27 ` Benoît Thébaudeau
2014-06-09 13:20 ` Thomas Petazzoni
2014-06-09 13:07 ` [Buildroot] [PATCH] lsof: do not remove WIDECHARINCL definition Thomas Petazzoni
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=61985964.1908854.1399044584132.JavaMail.zimbra@advansee.com \
--to=benoit.thebaudeau@advansee.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox