Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Microbit_Ubuntu <microbit@virginbroadband.com.au>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/8] ltrace: fix build failure
Date: Sat, 15 May 2010 21:19:27 +1000	[thread overview]
Message-ID: <1273922367.2046.3.camel@ubuntu> (raw)
In-Reply-To: <0878af525699db6c1298ecb340f7ffdd95541045.1273836748.git.thomas.petazzoni@free-electrons.com>

Hi Thomas,

On Fri, 2010-05-14 at 13:37 +0200, Thomas Petazzoni wrote:
> ltrace failed to build because of missing arguments to gcc to find the
> header files. This is due to the fact that the existing ltrace.mk was
> setting CC and LD at build time to incorrect values. Keeping the
> values set at configure time is just the right thing to do.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
>  package/ltrace/ltrace.mk |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/package/ltrace/ltrace.mk b/package/ltrace/ltrace.mk
> index c99f223..4a6811d 100644
> --- a/package/ltrace/ltrace.mk
> +++ b/package/ltrace/ltrace.mk
> @@ -54,8 +54,7 @@ $(LTRACE_DIR)/.configured: $(LTRACE_DIR)/.patched
>  	touch $@
>  
>  $(LTRACE_DIR)/$(LTRACE_BINARY): $(LTRACE_DIR)/.configured
> -	$(MAKE) CC=$(TARGET_CC) LD=$(TARGET_CROSS)ld ARCH=$(LTRACE_ARCH) \
> -		-C $(LTRACE_DIR)
> +	$(MAKE) ARCH=$(LTRACE_ARCH) -C $(LTRACE_DIR)
>  
>  $(TARGET_DIR)/$(LTRACE_TARGET_BINARY): $(LTRACE_DIR)/$(LTRACE_BINARY)
>  	#$(MAKE) DESTDIR=$(TARGET_DIR) ARCH=$(LTRACE_ARCH)  -C $(LTRACE_DIR) install


Is this why I also observed this problem with ltrace which I posted on
4/05/10 ? :

> 2. ltrace-0.5
> the OS path for sysdeps gets set to :
> OS := linux-uclibcgnueabi
> whereas internal toolchain 2010.02 produces at start of Makefile :
> OS = linux-gnu
> This results in an unknown path to /sysdeps/
> Has anyone come across this behaviour before ?
> I can workaround for now by manually changing Makefile and then 
> resuming build.

> I can't find the common denominator - I think it has to do with CC 
> being set --sysroot=...... whereas the internal toolchain produces
> --isysroot=......   ?????

TIA
-- 
Best regards,
Kris

  reply	other threads:[~2010-05-15 11:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14 11:37 [Buildroot] [pull request] Pull request for branch 2010-05-14-fixes Thomas Petazzoni
2010-05-14 11:37 ` [Buildroot] [PATCH 1/8] Add a BR2_NEEDS_GETTEXT option Thomas Petazzoni
2010-05-14 13:21   ` Lionel Landwerlin
2010-05-17  7:47   ` Peter Korsgaard
2010-05-19 11:33     ` Thomas Petazzoni
2010-05-14 11:37 ` [Buildroot] [PATCH 2/8] Make all package using gettext rely on BR2_NEEDS_GETTEXT Thomas Petazzoni
2010-05-17  7:46   ` Peter Korsgaard
2010-05-14 11:37 ` [Buildroot] [PATCH 3/8] libcap: fix build failure Thomas Petazzoni
2010-05-17  7:49   ` Peter Korsgaard
2010-05-19 11:30     ` Thomas Petazzoni
2010-05-19 11:50       ` Peter Korsgaard
2010-05-14 11:37 ` [Buildroot] [PATCH 4/8] libcgicc: fix package after autotools infrastructure conversion Thomas Petazzoni
2010-05-14 11:37 ` [Buildroot] [PATCH 5/8] ltrace: fix build failure Thomas Petazzoni
2010-05-15 11:19   ` Microbit_Ubuntu [this message]
2010-05-19 11:28     ` Thomas Petazzoni
2010-05-14 11:37 ` [Buildroot] [PATCH 6/8] gettext: make only available if BR2_NEEDS_GETTEXT is set Thomas Petazzoni
2010-05-14 13:24   ` Lionel Landwerlin
2010-05-14 11:37 ` [Buildroot] [PATCH 7/8] avahi: needs IPv6 Thomas Petazzoni
2010-05-17  7:55   ` Peter Korsgaard
2010-05-17 13:00   ` Peter Korsgaard
2010-05-14 11:37 ` [Buildroot] [PATCH 8/8] external toolchain: check BR2_INSTALL_LIBSTDCPP 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=1273922367.2046.3.camel@ubuntu \
    --to=microbit@virginbroadband.com.au \
    --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