From: Jens Staal <staal1978@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] more plan9 software
Date: Tue, 4 Jun 2013 17:41:33 +0200 [thread overview]
Message-ID: <51AE0AAD.2040803@gmail.com> (raw)
In-Reply-To: <55db4cbae97805610a00e5380e4bc473@kw.quanstro.net>
On 2013-06-04 16:43, erik quanstrom wrote:
>> architectures, either the native pcc or ape/cc need to get fixed
>
> what do you mean "fixed"?
>
> - erik
>
sorry, I was not very clear.
What I meant was that I (naturally) tried building with native APE first
but did not manage it. Unfortunately I did not document the problems
properly (nowadays -+ is active by default in cpp I think but there were
more stuff - possibly the "could not initialize bitfields" thing I have
hit some other times) and it is some time ago.
Now I just tried with gcc and it worked so I got a bit excited and
decided to upload as soon as possible (release early and all that).
BTW: I have been trying to adopt the modifications made to the original
port of GCC/binutils to more recent ones to have a i386-plan9 target
cross compiler on another host machine (linux, macosx, ...).
I do unfortunately not have much time playing with it though.
For APE: I probably should update the gcc-apelibs soon, but there seems
to be a state of flux currently with the new rune bits and other
modifications for recent python and go. When would be a good time to
make a snapshot?
next prev parent reply other threads:[~2013-06-04 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 14:47 Serge Ziryukin
2013-06-04 0:00 ` Serge Ziryukin
2013-06-04 14:38 ` Jens Staal
2013-06-04 14:43 ` erik quanstrom
2013-06-04 15:41 ` Jens Staal [this message]
2013-06-04 19:58 ` Jens Staal
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=51AE0AAD.2040803@gmail.com \
--to=staal1978@gmail.com \
--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).