From: bame@riverrock.org
To: Alan Modra <alan@linuxcare.com.au>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] new method for 64-bit parisc tree
Date: Thu, 02 Nov 2000 09:20:24 -0700 [thread overview]
Message-ID: <m13rN6H-001Vp3C@chalet> (raw)
In-Reply-To: Your message of "Thu, 02 Nov 2000 19:51:19 +1100." <Pine.LNX.4.21.0011021825100.26717-100000@front.linuxcare.com.au>
I want to hear concerns because without serious ones I'm going to
make this change next week...
= Instead, can't you simply play tricks with -I, and add a symbolic link
= asm -> ../asm-parisc in asm-parisc64)? The idea being to end up with
= an include path looking like
= "-I $(TOPDIR)/include -I $(TOPDIR)/include/asm"
=
= That way, asm/foo.h is found by the first -I if we have asm-parisc64/foo.h,
= and is found by the second if asm-parisc/foo.h exists but not
= asm-parisc64/foo.h. Hmm, you might also need -I-
That would function fine for header files, but not for source files
where something like VPATH might work, but is not available to us. It's
worth noting that both -I and VPATH tricks mean if you have an error
in or need to change a file, you may have to examine two
directories to figure out where it really lives. The symbolic link
scheme solves some of that problem.
-P
next prev parent reply other threads:[~2000-11-02 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 17:59 [parisc-linux] new method for 64-bit parisc tree Paul Bame
2000-11-02 8:51 ` Alan Modra
2000-11-02 16:20 ` bame [this message]
2000-11-07 18:15 ` [parisc-linux] 64-bit BUILD CHANGES Paul Bame
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=m13rN6H-001Vp3C@chalet \
--to=bame@riverrock.org \
--cc=alan@linuxcare.com.au \
--cc=parisc-linux@thepuffingroup.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