From: Nick Owens <mischief@9.offblast.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Building Go/386
Date: Mon, 2 Sep 2013 15:08:56 -0700 [thread overview]
Message-ID: <20130902220856.GA6254@iota.offblast.org> (raw)
In-Reply-To: <f965ca1f8eca907767a9938e0b12c7ef@brasstown.quanstro.net>
On Mon, Sep 02, 2013 at 05:51:15PM -0400, erik quanstrom wrote:
> On Mon Sep 2 16:51:31 EDT 2013, robpike@gmail.com wrote:
> > I'm pretty sure C defines the include path to be relative to the file
> > that includes it. The compiler's working directory should be
> > irrelevant. I'm also pretty sure Plan 9's compiler gets this right, or
> > at least used to. So more information is required.
>
> that still works, otherwise the kernel would not compile.
>
> - erik
>
the trouble here is that go's src/libmach/8obj.c has '#include
"../cmd/8l/8.out.h"', and 8.out.h now has the newly added '#include
"../ld/textflag.h"'.
i see now that the kernel source has an instance of this, in
/sys/src/9/pc: 'fns.h:1: #include "../port/portfns.h"', but i'm not sure
how that is treated differently from this situation.
i did a small test, and made $home/bin/rc/8c which forces the -p flag of
8c to invoke cpp. when doing ./make.rc in go with this wrapper, the
include appears to be resolved correctly.
fwiw, the standard does not define the mechanism for includes to be
found at all, only that it is implementation-specific [1].
nick
[1] http://www.iso-9899.info/n1256.html#6.10.2
next prev parent reply other threads:[~2013-09-02 22:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 14:36 lucio
2013-08-31 15:11 ` erik quanstrom
2013-08-31 17:09 ` lucio
2013-08-31 18:12 ` lucio
2013-08-31 21:16 ` erik quanstrom
2013-09-02 18:15 ` Nick Owens
2013-09-02 20:50 ` Rob Pike
2013-09-02 21:51 ` erik quanstrom
2013-09-02 22:08 ` Nick Owens [this message]
2013-09-03 0:28 ` erik quanstrom
2013-09-04 6:07 ` lucio
2013-09-07 11:19 ` Anthony Martin
2013-09-07 13:07 ` erik quanstrom
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=20130902220856.GA6254@iota.offblast.org \
--to=mischief@9.offblast.org \
--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).