From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: libc-ports@sourceware.org
Subject: Re: [PATCH] mips: use $dir for path to ldd-rewrite.sed
Date: Thu, 19 Apr 2012 21:39:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1204192130530.31272@digraph.polyomino.org.uk> (raw)
In-Reply-To: <201204191656.41885.vapier@gentoo.org>
On Thu, 19 Apr 2012, Mike Frysinger wrote:
> On Thursday 19 April 2012 16:20:39 Joseph S. Myers wrote:
> > On Thu, 19 Apr 2012, Mike Frysinger wrote:
> > > On Thursday 19 April 2012 15:51:40 Joseph S. Myers wrote:
> > > > On Wed, 18 Apr 2012, Mike Frysinger wrote:
> > > > > The $dest variable is based on the top build dir but we need the ldd
> > > > > rewrite variable to be based on the top source dir, so use $dir.
> > > >
> > > > Could you explain:
> > > please see the URL i posted to carlos that has the background research
> >
> > That certainly doesn't say how you tested the patch (presumably in at
> > least one case that failed before the patch and passed afterwards, but you
> > don't identify what cases).
>
> i showed how it fails today:
> http://sourceware.org/ml/libc-alpha/2012-04/msg00591.html
>
> so after i made my fix, i did the same thing and saw the correct path. i
> didn't build test mips because ia64 was affected by the same issue and fixing it
> there made things build fine. ergo making the same fix to mips should work.
I still don't see a good explanation of what all these variables are,
along the following lines:
* $dir is a directory that may be an absolute path to a directory in an
add-on, if configured using an absolute path to the add-on or a relative
path to the add-on but an absolute path to srcdir, or a relative path to
that directory from the srcdir if both configure-time paths were relative.
* $dest is a path to $dir that is always valid from the top of the build
directory (and is relative if both the source directory and the path to
any add-on were relative, absolute if either of those was absolute).
* $ldd_rewrite_script may be either absolute or relative to the toplevel
source directory, but not relative to the build directory. It is used in
the elf/ subdirectory of the source directory via $(patsubst
$(..)/%,/%,$(..)$(ldd-rewrite-script)), which means "use
$(ldd-rewrite-script) if it's an absolute path, use
../$(ldd-rewrite-script) if it's a relative path".
Is that the correct meaning of the three variables? If so, the patch is
OK, but you need to include such explanations in self-contained patch
submissions to make it clear to readers why the patch is correct without
requiring multiple messages from other threads to be followed.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-04-19 21:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 1:51 Mike Frysinger
2012-04-19 2:23 ` Carlos O'Donell
2012-04-19 2:28 ` Mike Frysinger
2012-04-19 3:10 ` Carlos O'Donell
2012-04-19 19:51 ` Joseph S. Myers
2012-04-19 20:13 ` Mike Frysinger
2012-04-19 20:21 ` Joseph S. Myers
2012-04-19 20:56 ` Mike Frysinger
2012-04-19 21:39 ` Joseph S. Myers [this message]
2012-04-20 3:42 ` Mike Frysinger
2012-04-20 9:27 ` Joseph S. Myers
2012-04-22 15:45 ` Carlos O'Donell
2012-04-24 4:01 ` Mike Frysinger
2012-04-25 4:11 ` Carlos O'Donell
2012-04-22 15:38 ` Mike Frysinger
2012-04-23 9:43 ` Joseph S. Myers
2012-04-24 4:03 ` Mike Frysinger
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=Pine.LNX.4.64.1204192130530.31272@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=vapier@gentoo.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).