From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <51AE0AAD.2040803@gmail.com> Date: Tue, 4 Jun 2013 17:41:33 +0200 From: Jens Staal User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130514 Thunderbird/17.0.6 MIME-Version: 1.0 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> References: <51ADFBF6.2050201@gmail.com> <55db4cbae97805610a00e5380e4bc473@kw.quanstro.net> In-Reply-To: <55db4cbae97805610a00e5380e4bc473@kw.quanstro.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [9fans] more plan9 software Topicbox-Message-UUID: 6315ba1e-ead8-11e9-9d60-3106f5b1d025 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?