mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/8 v3] [x86_64, multilib] Remove all hardcoded paths from glibc.make
Date: Mon, 26 Mar 2012 10:44:33 +0200	[thread overview]
Message-ID: <20120326084433.GF27119@pengutronix.de> (raw)
In-Reply-To: <CANqCtQJE-5p4HYiWraW+_JvL=MU8jTr=HDGA9P8hNE0u7zcs2g@mail.gmail.com>

On Sun, Mar 25, 2012 at 07:34:47PM +0200, Remy Bohmer wrote:
> 2012/3/25 Michael Olbrich <m.olbrich@pengutronix.de>:
> > On Sat, Mar 24, 2012 at 08:07:02PM +0100, Remy Bohmer wrote:
> >>  ifdef PTXCONF_GLIBC_I18N_BIN_LOCALE
> >> -     @$(call install_copy_toolchain_usr, glibc, bin/locale)
> >> +     @$(call install_copy_toolchain_lib, glibc, bin/locale)
> >>  endif
> >
> > 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.

Michael

[1] http://www.pengutronix.de/oselas/toolchain/

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2012-03-26  8:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 19:07 [ptxdist] [PATCH 1/8 v3] [x86_64] libgcc need to be install in /lib64 instead of /lib Remy Bohmer
2012-03-24 19:07 ` [ptxdist] [PATCH 2/8 v3] [x86_64, multilib] Remove all hardcoded paths from glibc.make Remy Bohmer
2012-03-25 11:01   ` Michael Olbrich
2012-03-25 17:34     ` Remy Bohmer
2012-03-26  8:44       ` Michael Olbrich [this message]
2012-03-26 10:09         ` Remy Bohmer
2012-03-27  6:23           ` Michael Olbrich
2012-03-27  7:18             ` Remy Bohmer
2012-03-24 19:07 ` [ptxdist] [PATCH 3/8 v3] [x86_64, multilib] Make packages install their libraries at the right place Remy Bohmer
2012-03-25 10:25   ` Michael Olbrich
2012-03-25 10:41     ` Remy Bohmer
2012-03-25 17:43       ` Remy Bohmer
2012-03-25 18:11         ` Remy Bohmer
2012-03-27 14:09           ` Michael Olbrich
2012-03-24 19:07 ` [ptxdist] [PATCH 4/8 v3] [x86_64, multilib] Install Zlib " Remy Bohmer
2012-03-24 19:07 ` [ptxdist] [PATCH 5/8 v3] [x86_64, multilib] Install Ncurses " Remy Bohmer
2012-03-24 19:07 ` [ptxdist] [PATCH 6/8 v3] [x86_64, multilib] Install Util-linux-ng " Remy Bohmer
2012-03-25 10:51   ` Michael Olbrich
2012-03-25 10:55     ` Remy Bohmer
2012-03-24 19:07 ` [ptxdist] [PATCH 7/8 v3] [x86_64, multilib] Install Readline " Remy Bohmer
2012-03-24 19:07 ` [ptxdist] [PATCH 8/8 v3] [x86_64, multilib] Install Procps " Remy Bohmer

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=20120326084433.GF27119@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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