9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 8c and elf shared libraries
Date: Tue, 17 Jul 2012 22:30:47 +0100	[thread overview]
Message-ID: <be97c727ffeba653392dfb6f89cc81b8@quintile.net> (raw)
In-Reply-To: <CAH7AAvpE3OJWg-B4OWTCRYEykft2Zz-PHnMKBFjRsmmfnUK5uQ@mail.gmail.com>

Thanks to all who have replied.

I have spoken to russ; 8l may be able to generate object files soon,
but there is no plan for support for shared libraries.

Its OK, I still have some options:

	use gcc/gas/gld on linux
	generate the shared library as a blind data file on plan9
	modify (hack) an existing linux shared library as a data file on plan9

the first seems the obvious choice but I would rather not have to rely on
an existing linux system, and extracting the correct build options
from linux's build structure is... complex.

its not as vile as it sounds the shared library in question is the
linux vdso systemcall interface and its tiny (three entry points from memory),
its just a shame that I have been unable to come up with an clean way of
generating the file on plan9.

-Steve



  reply	other threads:[~2012-07-17 21:30 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
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 [this message]
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=be97c727ffeba653392dfb6f89cc81b8@quintile.net \
    --to=steve@quintile.net \
    --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).