All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 07/13] toolchain: move sysroot to host dir
Date: Thu, 16 Dec 2010 11:49:29 +0100	[thread overview]
Message-ID: <20101216114929.0558f286@surf> (raw)
In-Reply-To: <1292353569-30172-8-git-send-email-gustavo@zacarias.com.ar>

Gustavo,

On Tue, 14 Dec 2010 16:06:03 -0300
Gustavo Zacarias <gustavo@zacarias.com.ar> wrote:

> diff --git a/Makefile b/Makefile
> index f6ab07e..d7d6f8d 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -268,8 +268,6 @@ TAR_OPTIONS=$(call qstrip,$(BR2_TAR_OPTIONS)) -xf
>  
>  GNU_TARGET_SUFFIX:=-$(call qstrip,$(BR2_GNU_TARGET_SUFFIX))
>  
> -STAGING_DIR:=$(call qstrip,$(BR2_STAGING_DIR))
> -
>  # packages compiled for the host goes here
>  HOST_DIR:=$(BASE_DIR)/host
>  
> @@ -294,6 +292,8 @@ endif
>  include toolchain/Makefile.in
>  include package/Makefile.in
>  
> +STAGING_DIR:=$(HOST_DIR)/usr/$(REAL_GNU_TARGET_NAME)/sysroot

This change breaks the ccache support, because when
--sysroot=$(STAGING_DIR) is used, STAGING_DIR expands to nothing,
because the definition of STAGING_DIR has been moved *after* the
inclusion of package/Makefile.in. Any reason why you moved the
definition ?

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2010-12-16 10:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 19:05 [Buildroot] [PATCH 00/13] Toolchain rework, take 2 Gustavo Zacarias
2010-12-14 19:05 ` [Buildroot] [PATCH 01/13] gmp: make it a proper package and bump to version 5.0.1 Gustavo Zacarias
2010-12-14 19:05 ` [Buildroot] [PATCH 02/13] php: libgmp was renamed to gmp Gustavo Zacarias
2010-12-14 19:49   ` Yann E. MORIN
2010-12-14 19:05 ` [Buildroot] [PATCH 03/13] mpfr: make it a proper package and bump to version 3.0.0-p8 Gustavo Zacarias
2010-12-14 19:06 ` [Buildroot] [PATCH 04/13] mpc: make it a proper package Gustavo Zacarias
2010-12-14 19:06 ` [Buildroot] [PATCH 05/13] package infra: fix versioned patches for host packages Gustavo Zacarias
2010-12-14 19:54   ` Yann E. MORIN
2010-12-14 19:06 ` [Buildroot] [PATCH 06/13] sstrip: make it a proper package Gustavo Zacarias
2010-12-14 19:06 ` [Buildroot] [PATCH 07/13] toolchain: move sysroot to host dir Gustavo Zacarias
2010-12-14 19:58   ` Yann E. MORIN
2010-12-14 20:45     ` Yann E. MORIN
2010-12-16 10:49   ` Thomas Petazzoni [this message]
2010-12-16 11:00     ` Gustavo Zacarias
2010-12-16 14:13       ` Gustavo Zacarias
2010-12-14 19:06 ` [Buildroot] [PATCH 08/13] uclibc: move tools " Gustavo Zacarias
2010-12-14 19:06 ` [Buildroot] [PATCH 09/13] binutils: make it a proper package Gustavo Zacarias
2010-12-14 20:14   ` Yann E. MORIN
2010-12-14 19:06 ` [Buildroot] [PATCH 10/13] gcc: cleanup and hook Gustavo Zacarias
2010-12-14 19:06 ` [Buildroot] [PATCH 11/13] gcc: install copies of libgcc, libstdc++ and libgcj to the sysroot too Gustavo Zacarias
2010-12-14 19:06 ` [Buildroot] [PATCH 12/13] uclibc: fix program invocation name config option for the snapshot version Gustavo Zacarias
2010-12-14 19:06 ` [Buildroot] [PATCH 13/13] gdb: make it a proper package Gustavo Zacarias

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=20101216114929.0558f286@surf \
    --to=thomas.petazzoni@free-electrons.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 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.