From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-bk0-f44.google.com ([209.85.214.44]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1SC6rZ-00084i-1D for ptxdist@pengutronix.de; Mon, 26 Mar 2012 12:09:22 +0200 Received: by bkuw5 with SMTP id w5so4457236bku.31 for ; Mon, 26 Mar 2012 03:09:09 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20120326084433.GF27119@pengutronix.de> References: <1332616028-32312-1-git-send-email-linux@bohmer.net> <1332616028-32312-2-git-send-email-linux@bohmer.net> <20120325110146.GD27119@pengutronix.de> <20120326084433.GF27119@pengutronix.de> Date: Mon, 26 Mar 2012 12:09:08 +0200 Message-ID: From: Remy Bohmer Subject: Re: [ptxdist] [PATCH 2/8 v3] [x86_64, multilib] Remove all hardcoded paths from glibc.make Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Hi Michael, 2012/3/26 Michael Olbrich : > On Sun, Mar 25, 2012 at 07:34:47PM +0200, Remy Bohmer wrote: >> 2012/3/25 Michael Olbrich : >> > On Sat, Mar 24, 2012 at 08:07:02PM +0100, Remy Bohmer wrote: >> >> =A0ifdef PTXCONF_GLIBC_I18N_BIN_LOCALE >> >> - =A0 =A0 @$(call install_copy_toolchain_usr, glibc, bin/locale) >> >> + =A0 =A0 @$(call install_copy_toolchain_lib, glibc, bin/locale) >> >> =A0endif >> > >> > This breaks with my toolchain: >> > [...] >> > install_copy_toolchain_lib: bin/locale not found >> > [...] >> > >> > I guess, in your toolchain this is in lib[64]/bin because you need on = for >> > each. >> >> Correct, these are indeed for example in >> /arm-none-linux-gnueabi/libc/usr/lib/bin/locale. >> What toolchain are you using? So, I can reproduce it here and fix it. > > Any OSELAS.Toolchain[1] should do. The CodeSourcery toolchains should work > as well, with the current code. > Which toolchain are you using? This code should realy be cleaned up, if I > ever find the time for it. I think it would be a good I idea to have > multiple toolchains at hand for it. I am not sure I understood you correctly. You mentioned that it breaks with your toolchain... Does it work with OSELAS, or does it not? We are using CodeSourcery toolchains for ia32 and ARM (several different releases since 2009-2011), furthermore we are using toolchains build with crosstool-ng. I tested with all of them, and these compilers work. I did NOT test with OSELAS toolchains (since the last time I checked there was no Windows hosted equivalent for the application developers besides the Linux hosted toolchains.) Kind regards, Remy -- = ptxdist mailing list ptxdist@pengutronix.de