9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lsub <nemo@lsub.org>
To: "9fans@9fans.net" <9fans@9fans.net>
Cc: "9fans@9fans.net" <9fans@9fans.net>
Subject: Re: [9fans] Building Go on Plan 9
Date: Thu,  1 Dec 2011 20:20:38 +0100	[thread overview]
Message-ID: <AC096DC2-2DAF-4FEF-9939-2D59ABDBDB3B@lsub.org> (raw)

send a change to nix-dev to include the se headers.
the process file describes how to do it.

Another alternative is to make a contrib package for nix
that could be installed with pm.

Perhaps that's a better option.

--
using ipad keyboard. excuse any typos.


On Dec 1, 2011, at 7:29 PM, ality@pbrane.org wrote:

> Charles Forsyth <charles.forsyth@gmail.com> once said:
>> modified library headers?
>
> % ls (386 sys)^/include/go
> 386/include/go/u.h
> 386/include/go/ureg_amd64.h
> 386/include/go/ureg_arm.h
> 386/include/go/ureg_x86.h
> sys/include/go/ar.h
> sys/include/go/bio.h
> sys/include/go/bootexec.h
> sys/include/go/goenv.h
> sys/include/go/libc.h
> sys/include/go/mach.h
> sys/include/go/stdio.h
>
> Some of these are just copies of the standard
> headers and others have a few adjustments that
> the Go toolchain requires. All except mach.h
> have #pragmas that point to the stock location
> in /386/lib/*.a.
>
> Anthony
>
> [/mail/box/nemo/msgs/201112/50]



             reply	other threads:[~2011-12-01 19:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01 19:20 lsub [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-12-01 17:48 Anthony Martin
2011-12-01 17:51 ` erik quanstrom
2011-12-01 18:00 ` John Floren
2011-12-01 18:05   ` Stanley Lieber
2011-12-01 18:14   ` Anthony Martin
2011-12-01 18:19     ` Charles Forsyth
2011-12-01 18:25       ` Lyndon Nerenberg
2011-12-01 19:07         ` Anthony Martin
2011-12-01 19:54           ` Lyndon Nerenberg
2011-12-02  3:39             ` Lucio De Re
2011-12-02 14:33               ` Anthony Martin
2011-12-02 14:57                 ` erik quanstrom
2011-12-02 15:23                   ` Anthony Martin
2011-12-02 17:14                   ` Skip Tavakkolian
2011-12-02 15:19                 ` Lyndon Nerenberg
2011-12-02 15:59                 ` Lucio De Re
2011-12-02 16:09                   ` Lucio De Re
2011-12-02 17:24                 ` ron minnich
2011-12-02 17:55                   ` Lyndon Nerenberg
2011-12-02 17:58                     ` Francisco J Ballesteros
2011-12-02 18:19                       ` ron minnich
     [not found]                       ` <CAP6exYKKqsc0Kwyhxp_LiXf0oRUJ79UYWZM=Ugp2WPZ7TZATwQ@mail.gmail.c>
2011-12-02 21:42                         ` erik quanstrom
2011-12-02 22:12                           ` andrey mirtchovski
2011-12-02 22:13                             ` andrey mirtchovski
2011-12-02 17:58                     ` Lyndon Nerenberg
2011-12-02 18:01                     ` erik quanstrom
2011-12-02  6:34             ` ron minnich
2011-12-02  6:42               ` Lucio De Re
2011-12-02  8:49                 ` Francisco J Ballesteros
2011-12-02 17:21                   ` ron minnich
2011-12-01 18:28       ` Anthony Martin
2011-12-01 18:30         ` erik quanstrom
2011-12-01 18:45           ` Anthony Martin
2011-12-01 18:48             ` Anthony Martin
2011-12-01 18:18 ` Anthony Martin
2011-12-02 14:40   ` Pavel Zholkover
2011-12-02 14:57     ` Anthony Martin

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=AC096DC2-2DAF-4FEF-9939-2D59ABDBDB3B@lsub.org \
    --to=nemo@lsub.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).