From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [PATCH] SN makefile update
Date: Wed, 12 Mar 2003 19:52:38 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709806071@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709806013@msgid-missing>
On Wed, Mar 12, 2003 at 08:46:04PM +0100, Sam Ravnborg wrote:
> On Tue, Mar 11, 2003 at 03:08:19PM -0800, Jesse Barnes wrote:
> > >
> > > Most of it looks fine to me. However, is the fprom stuff ever going
> > > to be useful to anyone other than SGI users? If not, I'd prefer if
> > > we could put that stuff in an SGI-specific Makefile.
> >
> > Probably not, but I don't know how to put a makefile target like that
> > in arch/ia64/sn/Makefile. Sam, is there a way to do this?
>
> The best proposal I can come up with right now is to accept the
> following command:
> make arch/ia64/sn/fprom/ fprom
>
> That should do the trick, if you go back to a fprom target without path.
>
> So arch/ia64/sn/fprom/Makefile looks something like this:
> .PHONY: fakeprom
> fakeprom: $(obj)/fakeprom
> command to create fprom
>
> Then you may add the whle fakeprom directory only on internal SGI kernels.
> Or you could have a special Makefile for SGI.
>
> Looks OK?
Yeah, that's what I was afraid of, but I guess it'll be ok. David,
can you take everything but the fprom target changes to
arch/ia64/Makefile in the meantime? I can generate another patch for
the stuff above later...
Thanks,
Jesse
prev parent reply other threads:[~2003-03-12 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 5:34 [Linux-ia64] [PATCH] SN makefile update Jesse Barnes
2003-03-11 22:55 ` David Mosberger
2003-03-11 23:08 ` Jesse Barnes
2003-03-12 19:46 ` Sam Ravnborg
2003-03-12 19:52 ` Jesse Barnes [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=marc-linux-ia64-105590709806071@msgid-missing \
--to=jbarnes@sgi.com \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.