linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: How about a few symlinks.....
Date: Tue, 7 Aug 2001 16:23:37 -0700	[thread overview]
Message-ID: <20010807162337.I22821@mikef-linux.matchmail.com> (raw)
In-Reply-To: <3B7056AA.EAE5CEE1@mvista.com>


On Tue, Aug 07, 2001 at 04:59:22PM -0400, Dan Malek wrote:
>
> While editing some Makefiles I was wondering what people thought
> of using symlinks to processor dependent files instead of nested
> ifdefs in Makefiles?
>
> For starters, make arch/ppc/kernel/head.S a symlink to the appropriate
> one in that directory, and derive the name to use from one of the
> config options.  I thought I would ask before demonstrating the change.
>

Also, include/asm is just a lymlink to asm-${arch}.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-08-07 23:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07 20:59 How about a few symlinks Dan Malek
2001-08-07 21:04 ` Matt Porter
2001-08-07 23:23 ` Mike Fedyk [this message]
2001-08-08  0:21   ` Tom Rini

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=20010807162337.I22821@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).