9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Phil Kulin <schors@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] building Alef language
Date: Sun, 22 Sep 2019 10:08:24 +0300	[thread overview]
Message-ID: <CAK=u2EU_ywfiY1uUDSgxz0zN56ztgVMCof2bKO1kYVca2-r+Hg@mail.gmail.com> (raw)
In-Reply-To: <CA+cCjXrrZ6uNitmh8d-gvkfCBG=FyYw3HE2qa=Rj3Vr_2LeFhg@mail.gmail.com>

Yes. But this requires writing wrapper code as in /sys/src/libc/9sys/write.c
I have no reason to do this. But writing wrapper may be better

On Sun, Sep 22, 2019 at 2:02 AM Rodrigo G. López <rodrigosloop@gmail.com> wrote:
>
> wth. they are the same plus an offset, which you can set to -1LL to replicate the behavior of read(2) (/sys/src/libc/9sys/read.c)
>
>
> -rodri
>
> On Sat, Sep 21, 2019, 10:45 PM Phil Kulin <schors@gmail.com> wrote:
>>
>> Ok. 9front doesn't have write and read syscalls. I patched
>> sys/src/alef/lib/sys/mkfile I translated _write to write and _read to
>> read. Yes, dirty hack. But I don't understand pwrite and pread
>> syscalls internals.
>>
>> ItT'S WORK!!!
>>
>> I'm worried I can't fix sys/src/alef/lib/rt/mkfile
>> I patch libA.a manually every time
>>
>> On Sat, Sep 21, 2019 at 8:58 PM Phil Kulin <schors@gmail.com> wrote:
>> >
>> > Problem probably in sys/src/alef/lib/rt/ near librt.8.a
>> > Build process passes with warning about file existing
>> >
>> > Manual command:
>> > ar vu /386/lib/alef/libA.a sys/src/alef/lib/386/*.8
>> > reduces number of error messages when test builds
>> >
>> > There are only:
>> > ALEFassert: undefined: write
>> > ALEFassert: undefined: read
>> >
>> >
>> > On Sat, Sep 21, 2019 at 5:05 PM Phil Kulin <schors@gmail.com> wrote:
>> > >
>> > > Thank you. I used this snapshot and I built alef. But I couldn't build
>> > > tests. And can't build any alef program.
>> > >
>> > > I think, than linker can't find /$object/lib/alef path (386 in my case)
>> > >
>> > > On Sat, Sep 21, 2019 at 5:41 AM Sean Hinchee <henesy.dev@gmail.com> wrote:
>> > > >
>> > > > As rodri states BurnZeZ has a copy of Alef he got building and kind of
>> > > > running under 9front/386. I kind of got the same thing at one point, but
>> > > > his is way better :)
>> > > >
>> > > > I know a snapshot of it is on mycroftiv's public grid around
>> > > > /n/griddisk/burnzez
>> > > >
>> > > > I don't know if he has a public version-controlled copy.
>> > > >
>> > > > Cheers,
>> > > > Sean
>> > > >
>> > > > On 9/20/19 2:05 PM, Rodrigo G. López wrote:
>> > > > > somebody please summon The BurnZeZ.
>> > > > >
>> > > > >
>> > > > > -rodri
>> > > > >
>> > > > > On Fri, Sep 20, 2019, 10:46 PM Phil Kulin <schors@gmail.com
>> > > > > <mailto:schors@gmail.com>> wrote:
>> > > > >
>> > > > >     I try to build Alef language
>> > > > >     latest 9front iso
>> > > > >
>> > > > >     %9fs 9pio
>> > > > >     # I don't know why, but "tar x alef.tgz" command do nothing...
>> > > > >     %tarfs /n/sources/extra/alef.tgz
>> > > > >     %dircp /n/tapefs/sys /sys
>> > > > >     % cd /sys/src/alef
>> > > > >     % mk all
>> > > > >     mk $objtype.all
>> > > > >     @{cd v; mk all }
>> > > > >     @{cd k; mk all }
>> > > > >     @{cd 8; mk all }
>> > > > >     @{cd lib; mk all }
>> > > > >     yacc -d ../port/parl.y
>> > > > >
>> > > > >     conflicts: 2 shift/reduce
>> > > > >     mv y.tab.h ../port/y.tab.h
>> > > > >     8c -w -I../port cinit.c
>> > > > >     8c -w -I../port code.c
>> > > > >     machdep.h:329 ../port/parl.h:332 cinit.c:6 syntax error, last name:
>> > > > >     Fconv
>> > > > >     mk: 8c -w -I../port cinit.c  : exit status=rc 40921: 8c 40925: error
>> > > > >     machdep.h:329 ../port/parl.h:332 code.c:6 syntax error, last name: Fconv
>> > > > >     mk: @{cd v; mk ...  : exit status=rc 40909: rc 40911: mk 40912: error
>> > > > >     mk: mk $objtype.all  : exit status=rc 40906: mk 40908: error
>> > > > >     %
>> > > > >
>> > > > >     I think that problem in "Fconv" definition...
>> > > > >
>> > > > >     --
>> > > > >     Non nobis Domine non nobis sed Nomini Tuo da gloriam
>> > > > >     Phil Kulin
>> > > > >
>> > > >
>> > >
>> > >
>> > > --
>> > > Non nobis Domine non nobis sed Nomini Tuo da gloriam
>> > > Phil Kulin
>> >
>> >
>> >
>> > --
>> > Non nobis Domine non nobis sed Nomini Tuo da gloriam
>> > Phil Kulin
>>
>>
>>
>> --
>> Non nobis Domine non nobis sed Nomini Tuo da gloriam
>> Phil Kulin



-- 
Non nobis Domine non nobis sed Nomini Tuo da gloriam
Phil Kulin



  reply	other threads:[~2019-09-22  7:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20 20:45 Phil Kulin
2019-09-20 21:05 ` Rodrigo G. López
2019-09-21  2:40   ` Sean Hinchee
2019-09-21  3:14     ` Lucio De Re
2019-09-21 12:33       ` hiro
2019-09-22  7:46       ` Phil Kulin
2019-09-22  9:38         ` Rodrigo G. López
2019-09-22  9:44           ` Ethan Gardener
2019-09-23  1:01         ` Sean Hinchee
2019-09-24  9:53           ` Steve Simon
2019-09-24 11:25             ` hiro
2019-09-24 11:56               ` Rodrigo G. López
2019-09-25  6:40                 ` Sergey Zhilkin
2019-09-25 17:35                   ` Steve Simon
2019-10-08 15:06                     ` Sergey Zhilkin
2019-10-08 19:50                       ` Phil Kulin
2019-10-08 20:24                         ` Sergey Zhilkin
2019-10-08 21:54                           ` Steve Simon
2019-09-21 14:05     ` Phil Kulin
2019-09-21 17:58       ` Phil Kulin
2019-09-21 20:45         ` Phil Kulin
2019-09-21 23:00           ` Rodrigo G. López
2019-09-22  7:08             ` Phil Kulin [this message]
2019-09-22  9:27 ` Ethan Gardener
2019-09-22  9:33   ` Phil Kulin

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='CAK=u2EU_ywfiY1uUDSgxz0zN56ztgVMCof2bKO1kYVca2-r+Hg@mail.gmail.com' \
    --to=schors@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).