From: Alan Modra <amodra@bigpond.net.au>
To: Kazu Hirata <kazu@codesourcery.com>
Cc: Daniel Jacobowitz <drow@false.org>, binutils@sourceware.org
Subject: Re: [patch] ldfile.c: Fix the search path ordering for a linker script.
Date: Thu, 02 Apr 2009 22:36:00 -0000 [thread overview]
Message-ID: <20090402223633.GD15456@bubble.grove.modra.org> (raw)
In-Reply-To: <49D4F902.8090203@codesourcery.com>
On Thu, Apr 02, 2009 at 01:42:26PM -0400, Kazu Hirata wrote:
> If -T is explicitly specified anywhere in the command line:
> we search:
> current directory
> search -L directories
> what find_scripts_dir finds
> else
> we search
> current directory
> what find_scripts_dir finds
> search -L directories
I would be happy with your current patch if you changed the existing
call to ldfile_open_command_file after ldemul_get_script in ldmain.c
to call a new function that only searched find_scripts_dir directory.
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2009-04-02 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 2:50 Kazu Hirata
2009-04-02 4:49 ` Alan Modra
2009-04-02 13:16 ` Daniel Jacobowitz
2009-04-02 17:42 ` Kazu Hirata
2009-04-02 22:36 ` Alan Modra [this message]
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=20090402223633.GD15456@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=kazu@codesourcery.com \
/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).