From: Jens Staal <staal1978@gmail.com>
To: libffi-discuss@sourceware.org
Subject: libffi on i386 Plan9/APE
Date: Mon, 03 Dec 2012 05:58:00 -0000 [thread overview]
Message-ID: <1431145.hgiI9FWO1y@krypton> (raw)
Hi
I managed to sort-of build libffi on Plan9 under the ANSI-POSIX ENVIRONMENT.
On this OS only a static library can be built.
The configure choked on a couple of things assuming GNU coreutils-behavior
(the command "cut" does not exist, and I needed to sed away a couple of
options from ls and mv), so I ended up manually adjusting files that failed to
be configured (so there is lots of room for improvements on my port).
Two files under x86 (unix.S and sysv.S) are GAS ASM, which is different from
Plan9 ASM so they could not be compiled into objects. Are there C variants of
those files available?
Are those two object files essential for libffi function? What are the
relevant tests to do of libffi.a ?
next reply other threads:[~2012-12-03 5:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 5:58 Jens Staal [this message]
2012-12-03 9:27 ` Andrew Haley
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=1431145.hgiI9FWO1y@krypton \
--to=staal1978@gmail.com \
--cc=libffi-discuss@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).