From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <201503112030.t2BKU71p008530@skeeve.com> From: Ryan Gonzalez Date: Thu, 12 Mar 2015 12:53:46 -0500 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=f46d043bdf86f7590905111b1168 Subject: Re: [9fans] ken cc for linux Topicbox-Message-UUID: 4971fd38-ead9-11e9-9d60-3106f5b1d025 --f46d043bdf86f7590905111b1168 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Mar 12, 2015 at 3:50 AM, Aram H=C4=83v=C4=83rneanu = wrote: > On Wed, Mar 11, 2015 at 10:04 PM, Ryan Gonzalez wrote: > > Go had vastly better versions, but it seems they got ripped out > recently. I > > think Go 1.3 may have had them, in which case you'd do something like: > > > > go tool 6c tst.c > > go tool 6l -o tst tst.6 > > First, Go did not have "vastly better versions", Go's compilers came > from Inferno and the back-ends were very minimally modified, mainly to > fix bugs. The linkers and other lower level details were modified a > lot, but they make what you want to do harder, not easier. > Well, they worked with ELF files. > Second, what you typed will try to link with the Go runtime, which is > definitely not what you want. Third, it will not work, at least not > without further work, main is not the entry point. Fourth, you don't > have a standard library available. > I know. ken-cc doesn't give you a standard library either. I'm getting these commands off the top of my head, not a manual somewhere. > > Go's compiler were there for building the Go runtime. To use them for > anything else, you'd need *a lot* of work, much more work than by > starting with the Plan 9/Inferno/Ken-cc directly. > > Eh... > -- > Aram H=C4=83v=C4=83rneanu > > --=20 Ryan [ERROR]: Your autotools build scripts are 200 lines longer than your program. Something=E2=80=99s wrong. http://kirbyfan64.github.io/ --f46d043bdf86f7590905111b1168 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= hu, Mar 12, 2015 at 3:50 AM, Aram H=C4=83v=C4=83rneanu &l= t;aram.h@mgk.ro><= /span> wrote:
On Wed, Ma= r 11, 2015 at 10:04 PM, Ryan Gonzalez <rymg19@gmail.com> wrote:
> Go had vastly better versions, but it seems they got ripped out recent= ly. I
> think Go 1.3 may have had them, in which case you'd do something l= ike:
>
> go tool 6c tst.c
> go tool 6l -o tst tst.6

First, Go did not have "vastly better versions", Go's = compilers came
from Inferno and the back-ends were very minimally modified, mainly to
fix bugs. The linkers and other lower level details were modified a
lot, but they make what you want to do harder, not easier.
=

Well, they worked with ELF files.
=C2=A0
Second, what you typed will try to link with the Go runtime, which is
definitely not what you want. Third, it will not work, at least not
without further work, main is not the entry point. Fourth, you don't have a standard library available.

I kn= ow. ken-cc doesn't give you a standard library either.

I'm getting these commands off the top of my head, not a manua= l somewhere.
=C2=A0

Go's compiler were there for building the Go runtime. To use them for anything else, you'd need *a lot* of work, much more work than by
starting with the Plan 9/Inferno/Ken-cc directly.


Eh...
=C2=A0
--
Aram H=C4=83v=C4=83rneanu




--
Ryan
[ERROR]: Your aut= otools build scripts are 200 lines longer than your program. Something=E2= =80=99s wrong.
--f46d043bdf86f7590905111b1168--