9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] 8c and elf shared libraries
Date: Thu, 12 Jul 2012 05:51:18 +0100	[thread overview]
Message-ID: <20120712055118.2e15abf3@vardo.ethans.dre.am> (raw)
In-Reply-To: <7c8f9ee75eee1c9d33beb57da78e298e@quintile.net>

On Wed, 11 Jul 2012 17:15:26 +0100
"Steve Simon" <steve@quintile.net> wrote:

> Various projects have worked on 8c to make it generate code for other OSs,
> have any of these resulted in code that could generate a very _very_ simple
> ELF shared library sutiable for linux?
>
> -Steve
>

The 8l in Go can produce ELF binaries -- it's the linker rather than
the compiler you want to look at for this. Last I heard, Go's 8l wasn't
compatible with Plan 9's 8c, but there's an 8c in Go so that doesn't
matter too much. I'm sure some Go fans want to use system C libraries
by dynamic linking, but I'm not so sure about producing a linkable
library.

Thinking it over, I'd rather use the regular Linux toolchain for the
task. You can still write sensible C for gcc to compile, and I think
you'll have a lot less work to do. Besides, it's the approach taken by
p9p, inferno, and drawterm, it works well for them. If you're concerned
about compile time just lower the optimisation level or choose a
generic architecture to optimise for.

--
This is obviously some strange usage of the
word "simple" that I was previously unaware of.



  reply	other threads:[~2012-07-12  4:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 16:15 Steve Simon
2012-07-12  4:51 ` Ethan Grammatikidis [this message]
2012-07-12  5:42   ` erik quanstrom
2012-07-17 16:58     ` Ethan Grammatikidis
2012-07-17 21:16   ` Christopher Nielsen
2012-07-17 21:30     ` Steve Simon
2012-07-17 21:56     ` Charles Forsyth
     [not found]     ` <CAOw7k5iVQcNr-SnHVpnCb=FACtaYx8WMFA1oypAfDY1F9-P1Cw@mail.gmail.c>
2012-07-17 21:59       ` erik quanstrom
2012-07-17 22:17         ` Charles Forsyth
2012-07-17 23:22           ` hiro
2012-07-18  7:02             ` steve
2012-07-20 11:45               ` Ethan Grammatikidis
2012-07-28 10:40   ` Uriel

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=20120712055118.2e15abf3@vardo.ethans.dre.am \
    --to=eekee57@fastmail.fm \
    --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).