mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [ptxdist] [PATCH 3/9 v2] [x86_64, multilib] Remove all hardcoded paths from glibc.make
Date: Sun, 25 Mar 2012 13:29:56 +0200	[thread overview]
Message-ID: <20120325112956.GE27119@pengutronix.de> (raw)
In-Reply-To: <CANqCtQJ-NXOWaPSrkBfGhno2wU0E=S4B71kpjJbTzjLz=JirXw@mail.gmail.com>

On Sat, Mar 24, 2012 at 07:24:30PM +0100, Remy Bohmer wrote:
> Hi,
> 
> 2012/3/23 Michael Olbrich <m.olbrich@pengutronix.de>:
> > On Mon, Mar 19, 2012 at 10:14:46PM +0100, Remy Bohmer wrote:
> >> These hardcoded paths do not work for a multilib environment where
> >> libraries are typically installed in /lib64 for x86-64 instead of /lib
> >> All correct paths can be found by interrogating the compiler toolchain
> >> for the location of these files.
> >
> > Can't you use $(CROSS_LIB_DIR) here? I'd like to avoid larger changes to
> > install_copy_toolchain.sh. This depends a lot on the toolchain and is
> > rather difficult to test.
> 
> Are you sure you want this? Of course it can be done, but it feels
> what somewhat redundant if we add an explicit path here.
> After rebase on top of your gcc changes it is just a 1 line change.
> Well, let's do the following: I first do the rebase, and see from
> there how it looks. Adding CROSS_LIB_DIR can be done version 4 of the
> patchset ;-)

Keep it as it is for now. I think the paths are extra hints to find the
libs. But this really depends on the toolchain. I don't know if this is
still necessary.
Marc: this is your code, can you comment on that?

Michael

-- 
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-25 11:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 21:14 [ptxdist] [PATCH 1/9 v2] [x86_64] Add x86_64 architecture strings Remy Bohmer
2012-03-19 21:14 ` [ptxdist] [PATCH 2/9 v2] [x86_64] libgcc need to be install in /lib64 instead of /lib Remy Bohmer
2012-03-19 21:14 ` [ptxdist] [PATCH 3/9 v2] [x86_64, multilib] Remove all hardcoded paths from glibc.make Remy Bohmer
2012-03-23  7:42   ` Michael Olbrich
2012-03-24 18:24     ` Remy Bohmer
2012-03-25 11:29       ` Michael Olbrich [this message]
2012-03-19 21:14 ` [ptxdist] [PATCH 4/9 v2] [x86_64, multilib] Make packages install their libraries at the right place Remy Bohmer
2012-03-24 11:04   ` Michael Olbrich
2012-03-24 11:06     ` Michael Olbrich
2012-03-19 21:14 ` [ptxdist] [PATCH 5/9 v2] [x86_64, multilib] Install Zlib " Remy Bohmer
2012-03-19 21:14 ` [ptxdist] [PATCH 6/9 v2] [x86_64, multilib] Install Ncurses " Remy Bohmer
2012-03-19 21:14 ` [ptxdist] [PATCH 7/9 v2] [x86_64, multilib] Install Util-linux-ng " Remy Bohmer
2012-03-19 21:14 ` [ptxdist] [PATCH 8/9 v2] [x86_64, multilib] Install Readline " Remy Bohmer
2012-03-19 21:14 ` [ptxdist] [PATCH 9/9 v2] [x86_64, multilib] Install Procps " Remy Bohmer
2012-03-23  7:53 ` [ptxdist] [PATCH 1/9 v2] [x86_64] Add x86_64 architecture strings Michael Olbrich
2012-03-24 18:29   ` Remy Bohmer
2012-03-26  8:50     ` Michael Olbrich

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=20120325112956.GE27119@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=mkl@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