9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Loader dependencies
Date: Wed, 10 Apr 2013 10:01:39 -0400	[thread overview]
Message-ID: <ac6efc58b21282ab4e63f3611334e4b7@kw.quanstro.net> (raw)
In-Reply-To: <CAGGHmKGSi4B6MPw0THOmLQXF-t8WF+pG3WPBnT0h4BQ7=y2KZA@mail.gmail.com>

On Wed Apr 10 02:00:35 EDT 2013, sstallion@gmail.com wrote:

> I understand the taxonomy. I'm commenting on the general laziness of the
> change. Given that many of us tend to work on acl changes in isolation,
> this is an annoyance at best.

i think you misspelled "conservitivism."  ☺  imo, the elf patch
did a complete job of consolidating elf support, and
in some cases extending it to all elf-supporing arches.

what it didn't do is create an ld directory, but that's
a seperate issue.  and i could understand resisting adding it.

but i agree that an ld directory is probablly justified now,
and would simplify maintence.  for example, the recent
library search change that touched every linker, not just
the ld directory.  (there are more than 2 files that would
be in it.)  maybe it would also help for uimage support.

i considered doing this a few weeks ago, but the potential
differences with sources kept me from it.

regardless of the directory name, in your case the fix is
to copy the donor directory to the same parent as your
test linker.

- erik



      reply	other threads:[~2013-04-10 14:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  5:04 Steven Stallion
2013-04-10  5:49 ` David du Colombier
2013-04-10  5:58   ` lucio
2013-04-10  6:05     ` Steven Stallion
2013-04-10  9:19       ` Charles Forsyth
2013-04-10  5:59   ` Steven Stallion
2013-04-10 14:01     ` erik quanstrom [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=ac6efc58b21282ab4e63f3611334e4b7@kw.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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 NNTP newsgroup(s).