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 04/10] binutils: make it a proper package
Date: Mon, 3 Jan 2011 10:14:58 +0100	[thread overview]
Message-ID: <20110103101458.61270f4a@surf> (raw)
In-Reply-To: <4D1B9D16.1080902@zacarias.com.ar>

On Wed, 29 Dec 2010 17:41:58 -0300
Gustavo Zacarias <gustavo@zacarias.com.ar> wrote:

> >  Gustavo>  $(GCC_BUILD_DIR2)/.configured: $(GCC_DIR)/.patched
> >  Gustavo>  	mkdir -p $(GCC_BUILD_DIR2)
> >  Gustavo> -	-rmdir $(STAGING_DIR)/usr/$(REAL_GNU_TARGET_NAME)/lib
> >  Gustavo> -	mkdir -p $(STAGING_DIR)/lib
> >  Gustavo> -	ln -snf ../../lib $(STAGING_DIR)/usr/$(REAL_GNU_TARGET_NAME)/lib
> >  Gustavo> -	$(if $(BR2_ARCH_IS_64),mkdir -p $(STAGING_DIR)/lib64)
> >  Gustavo> -	$(if $(BR2_ARCH_IS_64),ln -snf ../../lib64 $(STAGING_DIR)/usr/$(REAL_GNU_TARGET_NAME)/lib64)
> > 
> > Why remove this ARCH_IS_64 stuff?
> 
> This is from commit 3c77bab2eeace3ee675bd745ca335fa3dd1630bb which does
> a symlink trick to make libstdc++ available. It's simpler to just copy
> libstdc++ (and libgcj/libgcc while at it) to the sysroot which is fixed
> in patch #5 from my series.

I am not sure about this justification, since I don't see what change
in the toolchain build procedure removes the need for this symbolic
link. Have you actually tested building WebKit on x86_64 for example ?

Thanks,

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:[~2011-01-03  9:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28 19:10 [Buildroot] [PATCH 00/10] Toolchain rework, take 3 Gustavo Zacarias
2010-12-28 19:10 ` [Buildroot] [PATCH 01/10] sstrip: make it a proper package Gustavo Zacarias
2010-12-28 19:10 ` [Buildroot] [PATCH 02/10] toolchain: move sysroot to host dir Gustavo Zacarias
2010-12-28 19:10 ` [Buildroot] [PATCH 03/10] uclibc: move tools " Gustavo Zacarias
2010-12-28 19:10 ` [Buildroot] [PATCH 04/10] binutils: make it a proper package Gustavo Zacarias
2010-12-28 22:38   ` Peter Korsgaard
2010-12-29 20:41     ` Gustavo Zacarias
2010-12-29 20:58       ` Peter Korsgaard
2011-01-03  9:14       ` Thomas Petazzoni [this message]
2011-01-03 10:13         ` Gustavo Zacarias
2010-12-28 19:10 ` [Buildroot] [PATCH 05/10] gcc: install copies of libgcc, libstdc++ and libgcj to the sysroot too Gustavo Zacarias
2010-12-28 19:10 ` [Buildroot] [PATCH 06/10] gdb: make it a proper package Gustavo Zacarias
2010-12-28 19:10 ` [Buildroot] [PATCH 07/10] package: drop sparc64 bits Gustavo Zacarias
2010-12-29 22:15   ` Peter Korsgaard
2010-12-28 19:10 ` [Buildroot] [PATCH 08/10] oprofile: use new libbfd option Gustavo Zacarias
2010-12-28 19:10 ` [Buildroot] [PATCH 09/10] binutils: needs libintl when locales are enabled Gustavo Zacarias
2010-12-28 19:10 ` [Buildroot] [PATCH 10/10] toolchain: drop BR2_CROSS_TOOLCHAIN_TARGET_UTILS option Gustavo Zacarias
2010-12-29 22:15   ` Peter Korsgaard
2010-12-29  8:17 ` [Buildroot] [PATCH 00/10] Toolchain rework, take 3 Peter Korsgaard
2010-12-29 20:43   ` Gustavo Zacarias
2010-12-29 21:04     ` Peter Korsgaard
2010-12-29 22:02       ` 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=20110103101458.61270f4a@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.