[9fans] Someone made a Wayland compositor based on Rio, Wio

[Ryan Gonzalez]

https://wio-project.org/

2/10 name, 9/10 demo, can't win it all I guess ¯\_(ツ)_/¯

Re: [9fans] I prefer cropping images in Plan 9

[Ryan Gonzalez]

On July 21, 2018 8:21:10 AM "Ethan A. Gardener"  wrote:

I just had to crop a bunch of images in the Gimp, and recalled how much I 
prefer doing it in Plan 9; it's so much less frustrating. In the Gimp, it's 
either a matter of estimating numbers (for a quick, casual job on visual 
media), or select, copy, paste into new window. In the latter case, when 
you save it, you have to find the directory and the file8749832710473name; 
not fun. Also, I'm not practised at this; I'm no good at cropping with my 
brain, so I had to zoom, resize the window, and select very carefully so 
selecting didn't move the image in the window.


In Plan 9, which isn't even made for the job, it's not without its 
frustrations, but it's got fewer of them than the Gimp. Open the image in 
page; use the plumber or otherwise enter the full path so you can 
copy/paste it later. Zoom and adjust the window as you like. In another 
window, grep for the filename (or the directory, or whatever,) in 
/dev/wsys/*/label, and type cd and send the directory part. (Of course, 
copy/paste or send the file name.) Then:

crop -i 4 window | topng > path/filename.png
This is the part where you'll likely want to copy the full original path. 
That's one done. On to the next image, which presumably is open in the same 
instance of page so you don't have to cd or anything. `cat label` to get 
its full name and path. (It's possible only 9front's page puts the path in 
the label, I don't know.)


To be fair, if you're using a command line, you might as well be using 
ImageMagick (not criticizing your points or anything, just playing devil's 
advocate).




It's an operating system with few pretensions and only clunky image editing 
tools, versus a powerful two-decade-mature image editing suite. Loading and 
saving the files is no worse in Plan 9 than it is in the Gimp with its 
oh-so-modern file selector, and the actual cropping part is easier in Plan 9!



If anyone's waiting for news of my OS where everything is done from an 
interpreter prompt, I got distracted for a while but I'm on it again now. 
I'm staying with Forth but looking at alternatives to swap drop and roll -- 
I mean stack manipulation primitives. Not to start a discussion here, but 
I've decided it will have a single tree of names for all permanent storage 
despite supporting architectures without a filesystem. Disk blocks could be 
a directory of numbers under /b0, /b1 etc. OFW's non-volatile environment 
variables could be a single-level directory under /nv. Actual local 
filesystems, including the host's, could go under /f. Perhaps other 
resources could go in the same tree as virtual files, but I'm not building 
that bridge until I see the river. It's off topic for this list, so perhaps 
mail replies to me privately?


While I'm replying here, might as well point out that, if you're going to 
do this, I think one thing that could maybe be interesting would be for the 
files to potentially contain rich data, not just plain text? Kind of like 
TempleOS or systemd's journal does.




Any suggestions for a mailing list provider? My primary requirement is low 
maintenance. I see many projects use Google Groups, but would like 
suggestions for others if you have them.




Google Groups and Freelist are the best. Google Groups has a terrible UI 
but also has better spam filters IME.



--
The lyf so short, the craft so long to lerne. -- Chaucer

Re: [9fans] the fossil (tm) stolen

[Ryan Gonzalez]

Not really much of a problem; no one really uses Fossil either.

On April 14, 2018 10:08:21 PM Andre Wingor  wrote:


zapp, bros!

did you hear about fossil-scm.org?
mr. hipp stolen your's cool trademark 8^D

--
andr.ru


--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
https://refi64.com/

[9fans] I just realized Linux supports 9p as a file system

[Ryan Gonzalez]

https://github.com/torvalds/linux/tree/master/fs/9p

--
Ryan (ライアン)
Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else
http://refi64.com

[9fans] What exactly *is* 9pcloud?

[Ryan Gonzalez]

Seems like a "private" browser-local file hosting thingymajig? I'm
struggling to figure out why everything ends up disappearing from the
"Remote Filesystem" side, why the scrollbars are minuscule, and I just
really don't get it...

-- 
Ryan (ライアン)
Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else
http://refi64.com/

Re: [9fans] Upspin - a respin of 9p?

[Ryan Gonzalez]

https://upspin.googlesource.com/upspin/

*looks at mascot*

Eh, Glenda's cuter. This looks like a sleep-deprived crack-addicted mobster
chick.

--
Ryan (ライアン)
Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else
http://refi64.com

On Feb 23, 2017 2:30 AM, "Bakul Shah"  wrote:

> https://upspin.io/doc/overview.md
>
> Upspin provides a global name space to name all your files. Given an
> Upspin name, a file can be shared securely, copied efficiently without
> “download” and “upload”, and accessed from anywhere that has a network
> connection.
> 
> Upspin can name information from any data service, not just traditional
> files.
> 
> Initial impression:
>
> IMHO, its usefulness is integrating a bunch of things. A path has a global
> user id (u...@foo.com) as a root, which is looked up in (what I would
> call) a root server. From it you find the directory server which stores the
> metadata for the remaining path. From this you find the data server where
> the file or data source is actually located and an ID meaningful to the
> server (like qid but can be a content sha1 sum). The directory server also
> checks if the requester is allowed access and presumably gives her a public
> key of the root user to be able to decrypt the data.
>
> Clearly, if the source is not an ordinary file, there can be no sha1 sum
> -- presumably the directory server doesn't care.
>
> The overview talks about the design being geared toward friends and family
> (ala Dropbox?) but the only thing I see that would be hard to scale is the
> fact a dir tree has an ACL. A dir server may also end up being a bottleneck.
>
> User data can be protected by the owner but the dir server needs to be
> able to read metadata such as ACL, data location etc.
>
> Not sure if the design allows for dynamic bind/mount. This would require a
> more flexible dir server structure... (I haven't read the code so this is
> pure speculation). But I'm wondering if something the CPU command can be
> implemented. May be there is a protocol to attach your own dir server.
>
> Renames are probably not handled to avoid atomicity (just speculating). Or
> may depend on a dir server.
>
> ACLs are for dir trees. From the syntax it looks like you can add more
> access in a sub tree but not remove it.
>
> I'd have preferred a capability scheme instead of ACLs -- need to think
> more about this.
>

Re: [9fans] Why getenv replaces \0 with spaces in the returned value?

[Ryan Gonzalez]

Just a wild guess, but I think it could be because getenv just returns a null-
terminated string with no indication of its length. If C code were to do
pretty much anything on the environment variable in question, it would always
be truncated. e.g. with VAR=ABC\0DEF, the C string processing functions would
assume it ended after ABC.

  

As a side note, Linux does nothing and simply returns it as-is. I wonder why
the Posix guys haven't added a getenv_n(var, ) function yet...

  

\--  

Ryan (ライアン)

Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else



  
On Jan 18 2017, at 10:47 am, Giacomo Tesio  wrote:  

> Hi, last night I noticed this strange post processing in 4th edition's  
getenv:
https://github.com/brho/plan9/blob/master/sys/src/libc/9sys/getenv.c#L34-L41

>

> seek(f, 0, 0);  
r = read(f, ans, s);  
if(r >= 0) {  
ep = ans + s - 1;  
for(p = ans; p < ep; p++)  
if(*p == '\0')  
*p = ' ';  
ans[s] = '\0';  
}

>

> Anybody know why this replacement is done?  
It does not seem a good fix to read/write or read/truncate races, but  
I can't find a better explanation.

>

>  
Giacomo

[9fans] Trying to boot 9front from a GPT USB stick

[Ryan Gonzalez]

Ok, so I installed Plan 9 onto a GPT-formatted USB stick and am trying to
boot it. Problem is, it isn't working. I get:


pbsok
no fat


My GRUB entry looks like this:


insmod part_gpt
set root='(hd2,9)'
chainloader +1


I found this thread:

https://groups.google.com/forum/m/#!msg/comp.os.plan9/tK6LsVDZtjw/VtkTwBQRJfYJ

so I tried marking the Plan 9 partition with the boot and legacy_boot
flags. It didn't change anything.

One thing I've noticed is that, with other OSs on the USB, I've had to add
a "boot delay" flag of some kind in order for the USB stick to get picked
up. Maybe I need to do something like that here?

--
Ryan (ライアン)
Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else
http://kirbyfan64.github.io/

Re: [9fans] Plan 9 5th Edition

[Ryan Gonzalez]

...which got shut down earlier this year:

https://opensource.googleblog.com/2015/03/farewell-to-google-code.html?m=1

--
Ryan (ライアン)
Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else
http://kirbyfan64.github.io/

On Nov 19, 2016 8:41 PM, "hiro" <23h...@gmail.com> wrote:

> i have heard good things about google code
>
>

Re: [9fans] Purism laptops

[Ryan Gonzalez]

Those things really aren't cheap, are they...

On Fri, Nov 11, 2016 at 12:51 PM, James A. Robinson 
wrote:

> Have folks seen https://puri.sm/ ?  Their description of how they are
> trying
> to put together "open" hardware (not 100% there yet) makes me wonder if
> it'd be open enough w/re to hardware specs to make it a target for Plan 9
> porting/support.
>
> Jim
>
>


-- 
Ryan (ライアン)
Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else
http://kirbyfan64.github.io/

Re: [9fans] 9front sam in plan9port.

[Ryan Gonzalez]

> It's kind of like a bastard child of vim and Plan 9's acme editor

I almost died laughing at this. :O

On Mon, May 23, 2016 at 4:28 PM, Skip Tavakkolian <
skip.tavakkol...@gmail.com> wrote:

> since it's a slow news day, i'm throwing this in. i'm neither condoning
> use of it nor disparaging it.
>
> https://github.com/driusan/de
>
>
> On Mon, May 23, 2016 at 1:27 PM Mart Zirnask 
> wrote:
>
>> looks like Rob King added ctrl-b (ctrl-k in his case) to deadpixi's
>> sam about a month ago. cool. :)
>>
>> https://github.com/deadpixi/sam/commit/cdbdf04093a76cd3634e59e127bfd8f7a5083b20#diff-22f470141ff9a8838525c57e45bcdb63
>>
>> On 23 May 2016 at 10:25, Mart Zirnask  wrote:
>> >> I wasn't able to get it working remotely because the additional 'rsam'
>> >> command doesn't seem to be built. I haven't looked at that yet though.
>> >
>> > I can't confirm for now if it was built for me on Tiny Core Linux. The
>> > source and makefile for 'rsam' are included and also documented,
>> > though.
>> > it also doesn't have the 'E' command.
>> >
>> > btw, is 9front's ctrl-b patch (for switching to the command window)
>> > available somewhere?
>> > I'm really interested in having that keyboard shortcut in this version
>> of sam.
>> >
>> > best,
>> > Mart
>>
>>


-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] store NaN() to memory traps on 386 (387)

[Ryan Gonzalez]

Not crash into a flaming ball of (very vague) fire?

On Mon, May 2, 2016 at 2:17 PM, erik quanstrom 
wrote:

> On Mon May  2 12:07:58 PDT 2016, cinap_len...@felloff.net wrote:
> >
> > > file under: awk was really designed for pre-posix unix.  :-)
> >
> > its not just about awk. whenever you want to convert a string to
> > a floating point number under plan9 you'll have to deal with this
> > problem:
> >
> > cpu% seq nan
> > seq 11791387: suicide: sys: fp: invalid operation fppc=0x2635
> status=0x8081 pc=0x122f
>
> that seems reasonable to me.  what could seq possibly do with nan?
>
> - erik
>
>


-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] FP register usage in Plan9 assembler

[Ryan Gonzalez]

On February 4, 2016 6:04:49 AM CST, lu...@proxima.alt.za wrote:
>> Plan 9 assembly is nice because it looks mostly the
>> same, and the simple addressing modes are mostly consistent, but it's
>> far from being really consistent between architectures.
>
>Personally, I agree with the view that trying to generalise assemblers
>across platforms is chasing a chimera.  I loved the Univac assembler I
>cut my teeth on and nothing has ever given me even a hint of the
>comfort I found there.  But I got used to the 8088 assembler and
>managed to do some convincing work with it (I won't list the number of
>issues I thought were total mindlessness by a crowd of engineers with
>no visible theoretical background).
>
>On today's platforms, assembler is not an option, it is a nightmare.
>Add all the hardware trickery that belongs to microprocessors, not to
>an adult computer, doesn't make anything more palatable.  Really, why
>should the job of arranging memory on start up belong in the kernel
>and not in a piece of dedicated logic that gets the job done and then
>gets out of the way permanently, preferably switches off?
>
>One of these day some hardware engineer will figure a way to move the
>logic of the power supply into the CPU.  No, wait, we already have
>voltage selections at different temperature as a kernel function, I
>believe!
>
>Bottom line?  Bless the Go Gods for having successfully subverted much
>of this nonsense by providing a cross-platform development tool that
>actually does what it says on the tin, despite efforts by the hardware
>suppliers to relegate software development (the real thing, not
>kid-scripting - or is it script-kidding?) to the smallest viable elite
>of life-challenged droids.
>

*cough* that's what people said about Java *cough*

>I really do feel better now, doctor!
>
>Lucio.

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] FP register usage in Plan9 assembler

[Ryan Gonzalez]

On February 4, 2016 10:09:49 AM CST, lu...@proxima.alt.za wrote:
>> *cough* that's what people said about Java *cough*
>
>What, that Java does what it says on the tin? Which tin?

Almost forgot:

The AbstractBeanPartAluminumRecyclableTinFactory that makes 
AbstractPartAluminumRecyclableTinLists, which contain 
AbstractPartAluminumRecyclableTins.

>
>Lucio.

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] FP register usage in Plan9 assembler

[Ryan Gonzalez]

On February 4, 2016 10:09:49 AM CST, lu...@proxima.alt.za wrote:
>> *cough* that's what people said about Java *cough*
>
>What, that Java does what it says on the tin? Which tin?
>

cross-platform development tool

>Lucio.

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Compiling ken-cc on Linux

[Ryan Gonzalez]

On November 29, 2015 3:41:45 AM CST, Vasudev Kamath <vasu...@copyninja.info> 
wrote:
>Ryan Gonzalez <rym...@gmail.com> writes:
>
>>>That took compilation further but now it breaks at point 4 in your
>>>issue. I hope I won't encounter more new issues :-).
>>>
>>
>> Ah, yes, I completely forgot about that part. :/ Good luck with the
>> rest of the compilation! You'll need it!
>
>Yes indeed. Now I'm having following error, after applying patch you
>mentioned in the comment.
>
>cc -m32  -o o.out y.tab.o lex.o
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/libcc.a
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/libbio.a
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/lib9.a
>
>(cd 6c; mk  all)
>mk: no recipe to make 'div.o'
>
>So there is no div.c under src/cmd/6c. I see that old mkfile mkfile_o
>has div.c but I don't know where original source file went. Removing
>div.$O\ from mkfile gives the following error.
>
>cc -m32  -o o.out cgen.o enam.o list.o mul.o peep.o reg.o sgen.o swt.o
>txt.o pswt.o pgen.o
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/libcc.a
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/libbio.a
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/lib9.a
>
>cgen.o: In function `cgen':
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:320:
>undefined reference to `sdiv2'
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:323:
>undefined reference to `smod2'
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:425:
>undefined reference to `sdivgen'
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:427:
>undefined reference to `udivgen'
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:632:
>undefined reference to `sdiv2'
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:635:
>undefined reference to `smod2'
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:759:
>undefined reference to `sdivgen'
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/6c/cgen.c:762:
>undefined reference to `udivgen'
>collect2: error: ld returned 1 exit status
>mk: cc -m32  ...  : exit status=exit(1)
>mk: for j in ...  : exit status=exit(1)
>mk: for j in ...  : exit status=exit(1)
>
>In both case I'm hitting dead end. Any hints for going forward?.

Well, the 6* compilers don't work ATM anyway, so I think you can just comment 
out the relevant lines in src/cmd/mkfile.
-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Compiling ken-cc on Linux

[Ryan Gonzalez]

On November 28, 2015 12:42:25 AM CST, da Tyga  wrote:
>I have been following this discussion about the C compiler and can no
>longer stop myself from making a (snarky?) comment.
>

If you thing this is snarky, you've never visited the Final Fantasy XV board on 
GameFAQs! ;)

>The K standard for C was very much written when the C language was a
>higher than assembler language for the PDP-11 (at least that's how I
>became
>acquainted with it back in 1976).  Most of us, in those days, welcomed
>something that was more high level than macro-assembler and yet
>amenable to
>writing operating systems and utilities (unlike FORTRAN, ALGOL and
>COBOL of
>that era).  Many of us would use the -s switch to check the generated
>assembler code and in some cases even modify the assembler code for
>selected functions to get exactly the desired result.
>
>The PDP-11 had a rather simple instruction set, thus the compiler
>produced
>relatively predictable code.  The undefined behaviours in many cases
>meant
>that at least on the PDP-11 we would know what to expect.  It was only
>once
>code was ported to other systems that these assumptions started getting
>sorely tested.
>
>Fast forward to present time, we have a bloated C standard and even
>more
>bloated C++ standards.  The target instruction sets are rich with lots
>of
>special case instructions; out of sequence execution; multi-level
>caches
>add further constraints.  So today's compilers need to analyse complex
>source code to run with good performance on extremely complex targets. 
>We
>shouldn't forget that in the case of the x86 family the compilers need
>to
>optimise for an ever evolving instruction set and retain backward
>compatibility across earlier variants.
>

I think the issue is trying to fix a broken problem. Perfect compatibility is 
pretty much impossible, but most attempts done to fix it just shift the pain to 
somewhere else. What's the quote about complexity not disappearing, just moving 
around?

I prefer languages that prefer correctness to perfect, cross-platform APIs that 
consist of 2000 functions, and no one knows what the hell half of them do.

>
>On 28 November 2015 at 12:01, erik quanstrom 
>wrote:
>
>> > Funny, but actually I was wondering if there is any subtle issue in
>the
>> > standards of the C language that makes it somehow hard to
>implement.
>> > For example I've met a few times weird implementations of libraries
>and
>> > frameworks dictated by broken standards: once they are in, they can
>never
>> > be removed due to backward compatibility. I thought that Charles
>(that
>> also
>> > implemented the Limbo compiler) might have referenced these kind of
>> issues
>> > in his pun.
>>
>> i think the simple answer is: no.  but many folks just love
>complexity,
>> and are
>> determined to find it.  if you give such a person one problem,
>they'll
>> come back
>> with two problems.  i call these folks complicators.  don't be a
>> complicator.
>>
>> (i have to remind myself this from time to time.)
>>
>> - erik
>>
>>

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.
CURRENTLY LISTENING TO: The Key We've Lost (Xenoblade Chronicles X)

Re: [9fans] Compiling ken-cc on Linux

[Ryan Gonzalez]

Try going to the top of mathi.h and putting:

#undef isnan
#undef isinf

Stupid macros that don't look like macros.

On November 27, 2015 10:50:20 AM CST, Vasudev Kamath <vasu...@copyninja.info> 
wrote:
>
>Hi Ryan,
>
>Ryan Gonzalez <rym...@gmail.com> writes:
>> See
>>
>https://bitbucket.org/plan9-from-bell-labs/9-cc/issues/1/problems-building-under-x64-linux
>> for some tips on fixing various errors you may encounter, including
>> this one. (I opened that issue like 8 months ago...)
>
>I followed your reported issue. I could fix first 2 points but I get
>different error after that.
>
>(cd src/libmath; mk  all)
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/libmath.a
>doesn't exist: assuming it will be an archive
>cc -c -m32 -g -O
>-I/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/include
>-I/home/vasudev/Documents/C_programming/compilers/9-cc/include
>-DLINUX_386 blas.c
>In file included from
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/include/lib9.h:9:0,
> from blas.c:1:
>/usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and
>_SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
># warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
>_DEFAULT_SOURCE"
>   ^
>In file included from
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/include/lib9.h:19:0,
> from blas.c:1:
>/home/vasudev/Documents/C_programming/compilers/9-cc/include/mathi.h:59:12:
>error: expected identifier or ‘(’ before ‘sizeof’
> extern int isnan(double);
>^
>mk: cc -c -m32 ...  : exit status=exit(1)
>mk: for j in ...  : exit status=exit(1)
>
>I tried to find sizeof in mathi.h but I can't really find
>anything. (Yeah there is no sizeof in either mathi.h or related
>files). 
>
>I'm unsure what the error is indicating. Any idea on how to proceed
>further?.

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Compiling ken-cc on Linux

[Ryan Gonzalez]

On November 27, 2015 11:16:02 AM CST, Vasudev Kamath <vasu...@copyninja.info> 
wrote:
>Ryan Gonzalez <rym...@gmail.com> writes:
>
>> Try going to the top of mathi.h and putting:
>>
>> #undef isnan
>> #undef isinf
>>
>> Stupid macros that don't look like macros.
>
>That worked. Even I didn't realize those as macros. But now I land in
>new error.
>
>/usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and
>_SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
># warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
>_DEFAULT_SOURCE"
>   ^
>In file included from
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/include/lib9.h:19:0,
> from fdlibm/fdlibm.h:2,
> from fdlibm/s_isnan.c:20:
>fdlibm/s_isnan.c:22:6: error: expected identifier or ‘(’ before
>‘sizeof’
>  int isnan(double x)
>  ^
>mk: cc -c -m32 ...  : exit status=exit(1)
>mk: for j in ...  : exit status=exit(1)
>
>So I went and put #undef isnan again before #include "fdlibm.h" in
>s_isnan.c and now I stop at a new error, again not mentioned in your
>reported issue.
>
>Posix.c: In function ‘myctime’:
>Posix.c:9:9: warning: implicit declaration of function ‘ctime’
>[-Wimplicit-function-declaration]
>  return ctime();
> ^
>Posix.c:9:9: warning: return makes pointer from integer without a cast
>[-Wint-conversion]
>cc -m32  -o o.out ar.o Posix.o
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/libmach.a
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/libbio.a
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/lib9.a
>
>ar.o: In function `page':
>/home/vasudev/Documents/C_programming/compilers/9-cc/src/cmd/iar/ar.c:1120:
>warning: the use of `mktemp' is dangerous, better use `mkstemp' or
>`mkdtemp'
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/libmach.a(obj.o):(.rodata+0x198):
>undefined reference to `_is9'
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/lib/libmach.a(obj.o):(.rodata+0x19c):
>undefined reference to `_read9'
>collect2: error: ld returned 1 exit status
>mk: cc -m32  ...  : exit status=exit(1)
>mk: for j in ...  : exit status=exit(1)
>mk: for j in ...  : exit status=exit(1)
>
>I guess this is because of commenting out 9obj.c from compilation. So I
>modified 9obj.c, below is the patch
>
>vasudev@rudra:~/Documents/C_programming/compilers/9-cc$ hg diff
>src/libmach/obj.c 
>diff -r 65fb8bb56c59 src/libmach/obj.c
>--- a/src/libmach/obj.c Thu Apr 23 11:11:38 2015 +0100
>+++ b/src/libmach/obj.c Fri Nov 27 22:44:29 2015 +0530
>@@ -24,14 +24,14 @@
> int_is5(char*),
>_is6(char*),
>_is8(char*),
>-   _is9(char*),
>+   /* _is9(char*), */
>_isk(char*),
>_isq(char*),
>_isv(char*),
>_read5(Biobuf*, Prog*),
>_read6(Biobuf*, Prog*),
>_read8(Biobuf*, Prog*),
>-   _read9(Biobuf*, Prog*),
>+   /* _read9(Biobuf*, Prog*), */
>_readk(Biobuf*, Prog*),
>_readq(Biobuf*, Prog*),
>_readv(Biobuf*, Prog*);
>@@ -63,7 +63,7 @@
>/*[ObjSparc64]*/{0, 0,},
>/*[ObjAmd64]*/  "amd64 .6", _is6, _read6,
>/*[ObjSpim]*/   {0, 0,},
>-   /*[ObjPower64]*/"power64 .9",   _is9, _read9,
>+   /*[ObjPower64]*//* "power64 .9",_is9, _read9,
>*/
>/*[Maxobjtype]*/0, 0
> };
>
>That took compilation further but now it breaks at point 4 in your
>issue. I hope I won't encounter more new issues :-).
>

Ah, yes, I completely forgot about that part. :/ Good luck with the rest of the 
compilation! You'll need it!

>Cheers,

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Compiling ken-cc on Linux

[Ryan Gonzalez]

On November 26, 2015 6:10:43 AM CST, Charles Forsyth 
 wrote:
>On 25 November 2015 at 17:10, Vasudev Kamath 
>wrote:
>
>> In file included from
>>
>/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/include/lib9.h:9:0,
>>  from 9obj.c:5:
>> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and
>> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
>> _DEFAULT_SOURCE"
>>
>
>Of course, that particular one is just the latest crud from the
>constantly
>mutating gcc/clang environments.
>Why "DEFAULT" if it's not in fact the default?

That's actually mostly glibc, the only library on earth that makes me want to 
bang my head on the floor.

I don't remember what GNU extension it is where glibc declares a function that 
Posix says should return no value as returning a value. So, when you use it 
like you're supposed to, you get errors.

Then there's also crap like 
https://github.com/kirbyfan64/qlibc/commit/fb550e9f35a20492bcb6a767e9e3d33e30c00c59.
 It was a PR I opened. strptime was undefined. Depending on the system, you 
need to define one of:

- _USE_XOPEN
- _XOPEN_SOURCE
- _BSD_SOURCE
and now:
- _DEFAULT_SOURCE
-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Compiling ken-cc on Linux

[Ryan Gonzalez]

On November 26, 2015 3:56:44 PM CST, Charles Forsyth 
<charles.fors...@gmail.com> wrote:
>On 26 November 2015 at 21:51, Charles Forsyth
><charles.fors...@gmail.com>
>wrote:
>
>> On 26 November 2015 at 21:49, Ryan Gonzalez <rym...@gmail.com> wrote:
>>
>>> All that is bad...but glibc is worse. The issue is that you kinda
>*have*
>>> to use it,
>>
>>
>> true, very true.
>
>
>i remember glibc being my first instance of having to buy a bigger
>drive
>just to build the thing.
>with clang+llvm, I revisited that, and also had to buy more RAM and
>CPU.

I remember the time I was trying to build LLVM+Clang on Windows in debug mode. 
Because...MinGW...I actually surpassed the file size limit when linking Clang, 
so I had to rebuild EVERYTHING. Stupid thing took about an hour each time.

Because MinGW.

>i wondered whether to have a cron entry to speak "WTF?" into /dev/audio
>every so often, to save my voice
>(cron would be good because it could switch to "blistering barnacles!"
>when
>children were present).

It would be so funny if it malfunctioned:

WTF barnacles!
blistering WTF?
-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Compiling ken-cc on Linux

[Ryan Gonzalez]

On November 26, 2015 3:31:11 PM CST, Charles Forsyth 
<charles.fors...@gmail.com> wrote:
>On 26 November 2015 at 18:15, Ryan Gonzalez <rym...@gmail.com> wrote:
>
>> the only library on earth that makes me want to bang my head on the
>floor.
>
>
>There must be others, surely. What about graphics libraries with APIs
>designed for FORTRAN (no data structures)?
>What about ostensible crypto libraries that get their random numbers
>from
>Walmart?

All that is bad...but glibc is worse. The issue is that you kinda *have* to use 
it, no matter how simple or complicated or stupid your program is. It's 
just...there. If you want to use a sane(r) libc like musl, your users need 
another dependency.

Granted, there are other bad libraries or libraries with bad APIs (OpenSSL, SDL 
[especially for playing short sounds!], PCRE, etc.). However, you really don't 
*have* to use them. You can usually use RE2 or libregexp9 over PCRE, SFML over 
SDL, and so forth. NOT WITH GLIBC!!

*rant over now*
-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Compiling ken-cc on Linux

[Ryan Gonzalez]

On November 26, 2015 5:21:54 PM CST, Charles Forsyth 
<charles.fors...@gmail.com> wrote:
>On 26 November 2015 at 23:08, Ryan Gonzalez <rym...@gmail.com> wrote:
>
>> Holy crap, that's crazy. I built it in debug mode on Linux, but I
>don't
>> think it used that much. I only have 6 GB right now!
>
>
>You have to remember that a C compiler is one of the largest, most
>complex
>software components that human beings have ever had to produce.
>The original C reference manual made it look deceptively easy, but
>really
>there's a ton of stuff going on in there, as you can see.
>How they ever got it going on a system with 64Kbytes of address space,
>I'll
>never know.

I read in LBAC that one compiler had about 80 passes. All of which stored their 
results on disk. I can't help but shudder at the thought of how long those 
things took to compile...
-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Compiling ken-cc on Linux

[Ryan Gonzalez]

On November 26, 2015 4:30:32 PM CST, David du Colombier <0in...@gmail.com> 
wrote:
>>> I remember the time I was trying to build LLVM+Clang on Windows in
>debug
>>> mode. Because...MinGW...I actually surpassed the file size limit
>when
>>> linking Clang, so I had to rebuild EVERYTHING. Stupid thing took
>about an
>>> hour each time.
>>
>>
>> Ah. Debug mode. It took me a while to suspect: I don't think you can
>build
>> debug mode at all now in 32-bit mode.
>> Even with gold instead of gnu ld it needs more memory than they can
>> represent in their arrangement of 32-bit user-mode address space.
>
>If I remember correctly, the last time I built clang in debug mode, it
>used
>more than 12 GB of memory during the linking. So yes, three times
>bigger than the 32-bit address space.

Holy crap, that's crazy. I built it in debug mode on Linux, but I don't think 
it used that much. I only have 6 GB right now!

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Undefined Behaviour in C

[Ryan Gonzalez]

Neither! It's what happens when you run sed 's/^\s*//' on your whole code
base, yielding results like (from cmd/yacc.c):


void
setup(int argc, char *argv[])
{
long c, t;
int i, j, fd, lev, ty, ytab, *p;
int vflag, dflag, stem;
char actnm[8], *stemc, *s, dirbuf[128];
Biobuf *fout;

ytab = 0;
vflag = 0;
dflag = 0;
stem = 0;
stemc = "y";
foutput = 0;
fdefine = 0;
fdebug = 0;
ARGBEGIN{
case 'v':
case 'V':
vflag++;
break;
case 'D':
yydebug = ARGF();
break;
case 'a':
yyarg = 1;
break;
case 'd':
dflag++;
break;
case 'l':
yyline = 0;
break;
case 'o':
ytab++;
ytabc = ARGF();
break;
case 's':
stem++;
stemc = ARGF();
break;
case 'S':
parser = PARSERS;
break;
default:
error("illegal option: %c", ARGC());
}ARGEND
openup(stemc, dflag, vflag, ytab, ytabc);
fout = dflag?fdefine:ftable;
if(yyarg){
Bprint(ftable, "#define\tYYARG\t1\n\n");
}
if((fd = mkstemp(ttempname)) >= 0){
tempname = ttempname;
ftemp = Bfdopen(fd, OWRITE);
}
if((fd = mkstemp(tactname)) >= 0){
actname = tactname;
faction = Bfdopen(fd, OWRITE);
}
if(ftemp == 0 || faction == 0)
error("cannot open temp file");
if(argc < 1)
error("no input file");
infile = argv[0];
if(infile[0] != '/' && getwd(dirbuf, sizeof dirbuf)!=nil){
i = strlen(infile)+1+strlen(dirbuf)+1+10;
s = malloc(i);
if(s != nil){
snprint(s, i, "%s/%s", dirbuf, infile);
cleanname(s);
infile = s;
}
}
finput = Bopen(infile, OREAD);
if(finput == 0)
error("cannot open '%s'", argv[0]);
cnamp = cnames;

defin(0, "$end");
extval = PRIVATE; /* tokens start in unicode 'private use' */
defin(0, "error");
defin(1, "$accept");
defin(0, "$unk");
mem = mem0;
i = 0;

for(t = gettok(); t != MARK && t != ENDFILE;)
switch(t) {
case ';':
t = gettok();
break;

case START:
if(gettok() != IDENTIFIER)
error("bad %%start construction");
start = chfind(1, tokname);
t = gettok();
continue;

case TYPEDEF:
if(gettok() != TYPENAME)
error("bad syntax in %%type");
ty = numbval;
for(;;) {
t = gettok();
switch(t) {
case IDENTIFIER:
if((t=chfind(1, tokname)) < NTBASE) {
j = TYPE(toklev[t]);
if(j != 0 && j != ty)
error("type redeclaration of token %s",
tokset[t].name);
else
SETTYPE(toklev[t], ty);
} else {
j = nontrst[t-NTBASE].value;
if(j != 0 && j != ty)
error("type redeclaration of nonterminal %s",
nontrst[t-NTBASE].name );
else
nontrst[t-NTBASE].value = ty;
}
case ',':
continue;
case ';':
t = gettok();
default:
break;
}
break;
}
continue;

case UNION:
/* copy the union declaration to the output */
cpyunion();
t = gettok();
continue;

case LEFT:
case BINARY:
case RIGHT:
i++;

case TERM:
/* nonzero means new prec. and assoc. */
lev = t-TERM;
ty = 0;

/* get identifiers so defined */
t = gettok();

/* there is a type defined */
if(t == TYPENAME) {
ty = numbval;
t = gettok();
}
for(;;) {
switch(t) {
case ',':
t = gettok();
continue;

case ';':
break;

case IDENTIFIER:
j = chfind(0, tokname);
if(j >= NTBASE)
error("%s defined earlier as nonterminal", tokname);
if(lev) {
if(ASSOC(toklev[j]))
error("redeclaration of precedence of %s", tokname);
SETASC(toklev[j], lev);
SETPLEV(toklev[j], i);
}
if(ty) {
if(TYPE(toklev[j]))
error("redeclaration of type of %s", tokname);
SETTYPE(toklev[j],ty);
}
t = gettok();
if(t == NUMBER) {
tokset[j].value = numbval;
if(j < ndefout && j > 3)
error("please define type number of %s earlier",
tokset[j].name);
t = gettok();
}
continue;
}
break;
}
continue;

case LCURLY:
defout(0);
cpycode();
t = gettok();
continue;

default:
error("syntax error");
}
if(t == ENDFILE)
error("unexpected EOF before %%");

/* t is MARK */
if(!yyarg)
Bprint(ftable, "extern int yyerrflag;\n");
Bprint(ftable, "#ifndef YYMAXDEPTH\n");
Bprint(ftable, "#define YYMAXDEPTH 150\n");
Bprint(ftable, "#endif\n" );
if(!ntypes) {
Bprint(ftable, "#ifndef YYSTYPE\n");
Bprint(ftable, "#define YYSTYPE int\n");
Bprint(ftable, "#endif\n");
}
if(!yyarg){
Bprint(ftable, "YYSTYPE yylval;\n");
Bprint(ftable, "YYSTYPE yyval;\n");
}else{
if(dflag)
Bprint(ftable, "#include \"%s.%s\"\n\n", stemc, FILED);
Bprint(fout, "struct Yyarg {\n");
Bprint(fout, "\tint\tyynerrs;\n");
Bprint(fout, "\tint\tyyerrflag;\n");
Bprint(fout, "\tvoid*\targ;\n");
Bprint(fout, "\tYYSTYPE\tyyval;\n");
Bprint(fout, "\tYYSTYPE\tyylval;\n");
Bprint(fout, "};\n\n");
}
prdptr[0] = mem;

/* added production */
*mem++ = NTBASE;

/* if start is 0, we will overwrite with the lhs of the first rule */
*mem++ = start;
*mem++ = 1;
*mem++ = 0;
prdptr[1] = mem;
while((t=gettok()) == LCURLY)
cpycode();
if(t != IDENTCOLON)
error("bad syntax on first rule");

if(!start)
prdptr[0][1] = chfind(1, tokname);

/* read rules */
while(t != MARK && t != ENDFILE) {
/* process a rule */
rlines[nprod] = lineno;
if(t == '|')
*mem++ = *prdptr[nprod-1];
else
if(t == IDENTCOLON) {
*mem = chfind(1, tokname);
if(*mem < NTBASE)
error("token illegal on LHS of grammar rule");
mem++;
} else
error("illegal rule: missing semicolon or | ?");
/* read rule body */
t = gettok();

more_rule:
while(t == IDENTIFIER) {
*mem = chfind(1, tokname);
if(*mem < NTBASE)
levprd[nprod] = toklev[*mem];
mem++;
t = gettok();
}
if(t == 

Re: [9fans] Compiling ken-cc on Linux

[Ryan Gonzalez]

See
https://bitbucket.org/plan9-from-bell-labs/9-cc/issues/1/problems-building-under-x64-linux
for some tips on fixing various errors you may encounter, including this
one. (I opened that issue like 8 months ago...)

On Wed, Nov 25, 2015 at 11:10 AM, Vasudev Kamath 
wrote:

>
> Hi,
>
> I'm trying to compile ken-cc from ¹. Its giving me following error
>
> cc -c -m32 -g -O
> -I/home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/include
> -I/home/vasudev/Documents/C_programming/compilers/9-cc/include -DLINUX_386
> -I../cmd/ 9obj.c
> In file included from
> /home/vasudev/Documents/C_programming/compilers/9-cc/Linux/386/include/lib9.h:9:0,
>  from 9obj.c:5:
> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
> _DEFAULT_SOURCE"
>^
> 9obj.c:8:22: fatal error: 9c/9.out.h: No such file or directory
> compilation terminated.
> mk: cc -c -m32 ...  : exit status=exit(1)
> mk: for j in ...  : exit status=exit(1)
>
> I can't find 9c under src/cmd folder. Any hints on how to get it
> compiled?.
>
> Cheers,
>
> ¹ https://bitbucket.org/plan9-from-bell-labs/9-cc/overview
>
>


-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] Undefined Behaviour in C

[Ryan Gonzalez]

I remember reading Jack Crenshaw's Let's Build a Compiler. In part 16, he 
mentioned that compiling an empty C source file on the VAX took 60 seconds and 
generated a 50K object file.

Link (just search for the text "vax"): 
http://compilers.iecc.com/crenshaw/tutor16.txt

(BTW, what exactly do you mean by "mmap of 0"?)

On November 25, 2015 8:57:11 PM CST, Prof Brucee <prof.bru...@gmail.com> wrote:
>I am still fascinated by the VAX architecture manual which designates
>as
>"unpredictable" many things with consequences  including machine crash.
>Pissed that I can't get my vaxen to crash or burst into flames.
>On 26/11/2015 1:46 PM, "Brantley Coile" <brantleyco...@me.com> wrote:
>
>> Bruce's law: undefined != stupid
>>
>> Sent from my iPad
>>
>> On Nov 25, 2015, at 9:04 PM, Prof Brucee <prof.bru...@gmail.com>
>wrote:
>>
>> gcc is indeed a very sad tome. The mmap of 0 is disgusting. I like
>kenc.
>> It just works. My behaviour this afternoon will be undefined but not
>as
>> stupid as that of some programmers.
>> On 26/11/2015 5:43 AM, "Brantley Coile" <brantleyco...@me.com> wrote:
>>
>>> Align it to column 7 and it looks like all the code I saw when I
>started.
>>>
>>> iPhone email
>>>
>>> On Nov 25, 2015, at 12:13 PM, Ryan Gonzalez <rym...@gmail.com>
>wrote:
>>>
>>> Neither! It's what happens when you run sed 's/^\s*//' on your whole
>code
>>> base, yielding results like (from cmd/yacc.c):
>>>
>>>
>>> void
>>> setup(int argc, char *argv[])
>>> {
>>> long c, t;
>>> int i, j, fd, lev, ty, ytab, *p;
>>> int vflag, dflag, stem;
>>> char actnm[8], *stemc, *s, dirbuf[128];
>>> Biobuf *fout;
>>>
>>> ytab = 0;
>>> vflag = 0;
>>> dflag = 0;
>>> stem = 0;
>>> stemc = "y";
>>> foutput = 0;
>>> fdefine = 0;
>>> fdebug = 0;
>>> ARGBEGIN{
>>> case 'v':
>>> case 'V':
>>> vflag++;
>>> break;
>>> case 'D':
>>> yydebug = ARGF();
>>> break;
>>> case 'a':
>>> yyarg = 1;
>>> break;
>>> case 'd':
>>> dflag++;
>>> break;
>>> case 'l':
>>> yyline = 0;
>>> break;
>>> case 'o':
>>> ytab++;
>>> ytabc = ARGF();
>>> break;
>>> case 's':
>>> stem++;
>>> stemc = ARGF();
>>> break;
>>> case 'S':
>>> parser = PARSERS;
>>> break;
>>> default:
>>> error("illegal option: %c", ARGC());
>>> }ARGEND
>>> openup(stemc, dflag, vflag, ytab, ytabc);
>>> fout = dflag?fdefine:ftable;
>>> if(yyarg){
>>> Bprint(ftable, "#define\tYYARG\t1\n\n");
>>> }
>>> if((fd = mkstemp(ttempname)) >= 0){
>>> tempname = ttempname;
>>> ftemp = Bfdopen(fd, OWRITE);
>>> }
>>> if((fd = mkstemp(tactname)) >= 0){
>>> actname = tactname;
>>> faction = Bfdopen(fd, OWRITE);
>>> }
>>> if(ftemp == 0 || faction == 0)
>>> error("cannot open temp file");
>>> if(argc < 1)
>>> error("no input file");
>>> infile = argv[0];
>>> if(infile[0] != '/' && getwd(dirbuf, sizeof dirbuf)!=nil){
>>> i = strlen(infile)+1+strlen(dirbuf)+1+10;
>>> s = malloc(i);
>>> if(s != nil){
>>> snprint(s, i, "%s/%s", dirbuf, infile);
>>> cleanname(s);
>>> infile = s;
>>> }
>>> }
>>> finput = Bopen(infile, OREAD);
>>> if(finput == 0)
>>> error("cannot open '%s'", argv[0]);
>>> cnamp = cnames;
>>>
>>> defin(0, "$end");
>>> extval = PRIVATE; /* tokens start in unicode 'private use' */
>>> defin(0, "error");
>>> defin(1, "$accept");
>>> defin(0, "$unk");
>>> mem = mem0;
>>> i = 0;
>>>
>>> for(t = gettok(); t != MARK && t != ENDFILE;)
>>> switch(t) {
>>> case ';':
>>> t = gettok();
>>> break;
>>>
>>> case START:
>>> if(gettok() != IDENTIFIER)
>>> error("bad %%start construction");
>>> start = chfind(1, tokname);
>>> t = gettok();
>>> continue;
>>>
>>> case TYPEDEF:
>>> if(gettok() != TYPENAME)
>>> error("bad syntax in %%type");
>>> ty = numbval;
>>> for(;;) 

Re: [9fans] Off topic: Linus rants against GCC-isms

[Ryan Gonzalez]

FYI, try googling "linus you don't need to understand programming". The link 
keeps taking me somewhere completely unrelated.

On November 4, 2015 9:41:56 PM CST, Aharon Robbins  wrote:
>Hi All.
>
>Although this group in general doesn't like Linux, I think most of you
>might enjoy his rant:
>
>http://gizmodo.com/you-dont-need-to-understand-programming-to-appreciate-t-17399
>27472
>
>Arnold

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] The 9legacy website looks bad on a mobile phone

[Ryan Gonzalez]

Looks the same on my device...

On November 3, 2015 12:12:21 AM CST, David du Colombier <0in...@gmail.com> 
wrote:
>It should be fixed now.
>
>-- 
>David du Colombier

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] off topic - a good Git reference

[Ryan Gonzalez]

It's still free. It just takes a heck of a lot of effort to port it to
other platforms after you get addicted to it.

On Thu, Oct 1, 2015 at 12:31 PM, Jeff Sickel 
wrote:

>
> > On Sep 30, 2015, at 2:59 AM, Charles Forsyth 
> wrote:
> >
> > Here's a small but representative example.
>
> That’s just an example of a C file.  The joy of Git is the rest of the
> requirements to actually use it:
>
> - bash
> - perl5
>
> And then if you want all the fancy tools & wrappers groups seem to like
> these days:
>
> - python
> - java
> - php
>
> And finally, a browser or other gui front end to make sense of it all.
>
> Free software isn’t so free after all.
>
> -jas
>
>
>


-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] joke's on us

[Ryan Gonzalez]

They're kind of right when they say "definitely"; the Zulip desktop client is 
written in C++, uses Qt for graphics, and uses CMake to build. I don't think 
any of those are available on Plan 9 (well, C++ is, but the compilers are kind 
of old...).

On September 26, 2015 9:59:44 AM CDT, Skip Tavakkolian 
 wrote:
>Plan 9 is now popular enough to make fun of:
>
>https://www.zulip.org/clients.html

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] On Linux, what is the rc init file?

[Ryan Gonzalez]

Low space on main HDD, but plenty on external.

On August 30, 2015 12:00:57 PM CDT, erik quanstrom quans...@quanstro.net 
wrote:
On Fri Aug 28 10:24:30 PDT 2015, rym...@gmail.com wrote:

 YES!! That was it! My plan9home directory didn't contain a bin
folder; that
 was somewhere else. When I symlinked it there, it worked! Thank you!
 
 

out of curiousity, why use a non-standard install?  

- erik

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

[9fans] On Linux, what is the rc init file?

[Ryan Gonzalez]

Every shell has one. You know, like .bashrc, .profile, etc. What's
plan9port rc's?

-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] On Linux, what is the rc init file?

[Ryan Gonzalez]

Thank you!

However, I think rc now hates me for some reason. :/ Watch:

ryan@DevPC-LX:~$ rc # works normally
% echo Hello, world!
Hello, world!
% ryan@DevPC-LX:~$
ryan@DevPC-LX:~$ export PLAN9=$HOME/stuff/plan9home
ryan@DevPC-LX:~$ cat $PLAN9/rcmain # rcmain is empty
ryan@DevPC-LX:~$ rc # does nothing??
ryan@DevPC-LX:~$ echo $?
0
ryan@DevPC-LX:~$

rc -v does nothing, either. If I unset $PLAN9, things work again.


On Fri, Aug 28, 2015 at 10:49 AM, s...@9front.org wrote:

 Take a look at $PLAN9/rcmain.

 sl




-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] On Linux, what is the rc init file?

[Ryan Gonzalez]

YES!! That was it! My plan9home directory didn't contain a bin folder; that
was somewhere else. When I symlinked it there, it worked! Thank you!


On Fri, Aug 28, 2015 at 11:37 AM, Skip Tavakkolian 9...@9netics.com wrote:

 make sure $PLAN9/bin is in front in your PATH.  try this:

 BIGASSBASHPROMPT$ 9 rc -i


  Thank you!
 
  However, I think rc now hates me for some reason. :/ Watch:
 
  ryan@DevPC-LX:~$ rc # works normally
  % echo Hello, world!
  Hello, world!
  % ryan@DevPC-LX:~$
  ryan@DevPC-LX:~$ export PLAN9=$HOME/stuff/plan9home
  ryan@DevPC-LX:~$ cat $PLAN9/rcmain # rcmain is empty
  ryan@DevPC-LX:~$ rc # does nothing??
  ryan@DevPC-LX:~$ echo $?
  0
  ryan@DevPC-LX:~$
 
  rc -v does nothing, either. If I unset $PLAN9, things work again.
 
 
  On Fri, Aug 28, 2015 at 10:49 AM, s...@9front.org wrote:
 
  Take a look at $PLAN9/rcmain.
 
  sl
 
 
 
 
  --
  Ryan
  [ERROR]: Your autotools build scripts are 200 lines longer than your
  program. Something’s wrong.
  http://kirbyfan64.github.io/





-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] github blob exchange

[Ryan Gonzalez]

I saw GitHub and Plan 9 together and immediately heard angels singing. :)

Question what does the --raw option do?

On August 10, 2015 5:04:54 AM CDT, Ingo Krabbe ikrabbe@gmail.com wrote:
Hi Plan9ers,

I wrote a little rc script for my personal use. I want to share it with
you, as it look quite usefull to me (why would I have wrote it
otherwise).

   https://github.com/ikrabbe/github.rc

Check it out and tell me your thoughts.

Regards,

ingo

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Harvey OS: A new OS inspired heavily by Plan 9

[Ryan Gonzalez]

On July 27, 2015 9:19:47 AM CDT, Anthony Sorace a...@9srv.net wrote:
 erik quanstrom quans...@quanstro.net wrote:
 
 when i need to run Linux programs, i run linux.

Yeah, but then you’ve got linux. Now you’ve got two
problems (hah! if only…).

 what is the benefit of running firefox on a p9 like system,
 rather than on linux?

The theory, anyway, is that you could then not have a linux
(or whatever) system. If the emulation bit could be self-
contained enough, a plan9 system with linuxemu would
have a significantly lower maintenance burden than a plan9
system plus a linux system. In theory.

I’ve never understood why the emulation effort picked
linux, though. It seems like the worst possible thing to be
emulating, and I don’t imagine the software support for the
sort of things we’re talking about (for many, it’s pretty
much just a browser) is all that different between Linux and,
say, FreeBSD. Are there a bunch of linux-only apps people
would like to have?

I always thought is was that emulating an open-source application platform is 
easier than emulating a black box like Wine does, as you can see how things are 
done and the internal APIs and stuff.


-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Harvey OS: A new OS inspired heavily by Plan 9

[Ryan Gonzalez]

On July 27, 2015 10:24:37 AM CDT, Daniel Valio not...@gmail.com wrote:
Am I the only one that is really bothered by the name?

It doesn't quite bring good things to mind.

What?? The Batman character??


On 24.07.15 21:43, Ryan Gonzalez wrote:

https://medium.com/this-is-not-a-monad-tutorial/harvey-an-operating-system-with-plan-9-s-shadow-3081414e5f0b

 I'm not affiliated with this whatsoever; I just saw it on Reddit and 
 found it interesting.

 I found this part particularly neat:

  We are working in ANSI POSIX environment to have most of well known

 tools and programs that programmers or end users expects to have in a

 modern operating system. Things that for traditional Plan 9 would be 
 very difficult to have.

 -- 
 Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity. 

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Stick

[Ryan Gonzalez]

On July 26, 2015 1:32:35 PM CDT, Sergey Zhilkin szhil...@gmail.com wrote:
To expensive for me, And, imo, device is useless
- no wired network
- no NORMAL external storage
- iNtel inside :)

As a terminal it is far more expensive then Rpi, as diskless cpu it
useless
too.

Useless :) for me

P.S.: Yes my home mac uses Intel CPU, but it is Apple ! :)

Mac? TRAITOR! :)


2015-07-26 0:37 GMT+03:00 Prof Brucee prof.bru...@gmail.com:

 AUD$229

 On Sun, Jul 26, 2015 at 7:02 AM, Sergey Zhilkin szhil...@gmail.com
 wrote:

 How much they cost ?



http://www.cnx-software.com/2014/10/15/meego-t01-hdmi-tv-stick-supports-android-windows-8-1-and-ubuntulinux/
 - the same

 I think they are too HOT :) And 64bit CPU comes with 32bit
Windows. Lol

 2015-07-25 0:31 GMT+03:00 Prof Brucee prof.bru...@gmail.com:

 Anyone with P9 experience on the Intel Compute Stick (aka
STK1A32WFC)?
 It's a lot of PC for such a small cost and form factor. I think it
was only
 released in oz last week. I have ordered one.

 brucee




 --
 С наилучшими пожеланиями
 Жилкин Сергей
 With best regards
 Zhilkin Sergey




-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Stick

[Ryan Gonzalez]

On July 26, 2015 2:48:33 PM CDT, Prof Brucee prof.bru...@gmail.com wrote:
A bit harsh and head-up-the-arse-ish. I'm willing to play with this
device.

Harsh? I put a smiley face to make it obvious it was a joke...

Enjoy your Mac.

brucee

On Mon, Jul 27, 2015 at 5:32 AM, Ryan Gonzalez rym...@gmail.com
wrote:



 On July 26, 2015 1:32:35 PM CDT, Sergey Zhilkin szhil...@gmail.com
 wrote:
 To expensive for me, And, imo, device is useless
 - no wired network
 - no NORMAL external storage
 - iNtel inside :)
 
 As a terminal it is far more expensive then Rpi, as diskless cpu it
 useless
 too.
 
 Useless :) for me
 
 P.S.: Yes my home mac uses Intel CPU, but it is Apple ! :)

 Mac? TRAITOR! :)

 
 2015-07-26 0:37 GMT+03:00 Prof Brucee prof.bru...@gmail.com:
 
  AUD$229
 
  On Sun, Jul 26, 2015 at 7:02 AM, Sergey Zhilkin
szhil...@gmail.com
  wrote:
 
  How much they cost ?
 
 
 
 

http://www.cnx-software.com/2014/10/15/meego-t01-hdmi-tv-stick-supports-android-windows-8-1-and-ubuntulinux/
  - the same
 
  I think they are too HOT :) And 64bit CPU comes with 32bit
 Windows. Lol
 
  2015-07-25 0:31 GMT+03:00 Prof Brucee prof.bru...@gmail.com:
 
  Anyone with P9 experience on the Intel Compute Stick (aka
 STK1A32WFC)?
  It's a lot of PC for such a small cost and form factor. I think
it
 was only
  released in oz last week. I have ordered one.
 
  brucee
 
 
 
 
  --
  С наилучшими пожеланиями
  Жилкин Сергей
  With best regards
  Zhilkin Sergey
 
 
 

 --
 Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.



-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Harvey OS: A new OS inspired heavily by Plan 9

[Ryan Gonzalez]

You forgot about my favorite use of gdb:

$ gdb --args a b c
gdb run
# wait for segfault
gdb bt
...
gdb quit


On July 26, 2015 12:54:34 PM CDT, hiro 23h...@gmail.com wrote:
Who claimed fast compilation was a motive?
From what I understand this is all about being able to use gdb for
debugging.

It makes sense to me, but it might still be subjective.
If you care I will explain my experience:

Some longer time ago I tried gdb for disassembling some secret binary,
but quickly gave up cause of the complex interface and reverted to
objdump instead. I wasted a lot of time and that made me hate gdb a
lot.

Now, much later I started using gdb again, cause as long as it has
access to the source analyzing coredumps is very easy. It's a better
workflow than my printf() debugging, because the Makefiles of the
project I'm working on are so complex and broken that everybody avoids
compiling (takes too long).
I have seen many complaints in Ron's commit logs about makefiles, too.
I'm fairly certain that for Harvey and Akaros they're pretty much
forced just like me into a coredump-driven development workflow.

tldr: gcc is needed so that we can use gdb so that we don't have to
compile as often so that we can fix bugs faster.

On 7/26/15, erik quanstrom quans...@quanstro.net wrote:
 just speaking for myself, I found the fact that plan 9 was a self
contained
 thing to be a must have.  i don't consider the gcc toolchain to be a
 feature.

 if fast compilation is a feature over plan 9, I'd like to see some
 numbers.

 - erik

 On Jul 25, 2015 3:15 PM, Axel Belinfante

[?cs=whv=bto=axel.belinfa...@utwente.nl]axel.belinfa...@utwente.nl
 wrote:

 I couldn’t resist looking, and found

in 
[http://www.google.com/url?q=http%3A%2F%2Fwww.osnews.com%2Fcomments%2F28699sa=Dsntz=1usg=AFQjCNGHKFWanYoFNYbSy6In7LAXtMi-tg]http://www.osnews.com/comments/28699

 Harvey is an effort to get the Plan 9 code working with gcc and
clang”.

 So, in a way it seems to be a port of Plan 9.

 More details, including the feature list below, are

at 
[http://www.google.com/url?q=http%3A%2F%2Fharvey-os.orgsa=Dsntz=1usg=AFQjCNErZ4XfGFvsgbhV-uqEiG8K2pSdYQ]http://harvey-os.org

 Features

 • AMD 64 bit
 • Modern, simplified syscall system
 • GCC toolchain means you can use gdb(!)
 • Compile in Linux or OSX using Harvey's headers and libs, no need
to
 change anything else
 • Fast compilation of the whole system
 • All Plan9 userland apps available
 • Plans to add X11 with rio-like multiplexing, tty driver, new
fileserver,
 native toolchain and more

 I’m intrigued by the “compile … using Harvey's headers and libs, no
need
 to change anything else” —
 I guess that means that it will be easy to “port” stuff to Harvey?

 The team list contains names well-known on this list...

 I must say, it looks quite interesting, worth checking out.

 Axel.

 On 25 Jul 2015, at 17:58, Ryan Gonzalez
 [?cs=whv=bto=rym...@gmail.com]rym...@gmail.com wrote:

 No clue. I'm guessing it's heavily inspired by Plan 9.

 On July 25, 2015 3:34:13 AM CDT,
 [?cs=whv=bto=st...@quintile.net]st...@quintile.net
 [?cs=whv=bto=st...@quintile.net]st...@quintile.net wrote:

 not sure what Harvey is... is it just plan9 ported to build on gcc?

 if so does gcc run under Harvey?

 does gcc run under plan9 now?

 Steve




 On 25 Jul 2015, at 01:43, Ryan Gonzalez
 [?cs=whv=bto=rym...@gmail.com]rym...@gmail.com wrote:


[https://www.google.com/url?q=https%3A%2F%2Fmedium.com%2Fthis-is-not-a-monad-tutorial%2Fharvey-an-operating-system-with-plan-9-s-shadow-3081414e5f0bsa=Dsntz=1usg=AFQjCNFKZSymwu8nNoZ6I7kp6PyVvp9A1g]https://medium.com/this-is-not-a-monad-tutorial/harvey-an-operating-system-with-plan-9-s-shadow-3081414e5f0b

 I'm not affiliated with this whatsoever; I just saw it on Reddit
and
 found it interesting.

 I found this part particularly neat:

  We are working in ANSI POSIX environment to have most of well
known
  tools and programs that programmers or end users expects to have
in a
  modern operating system. Things that for traditional Plan 9
would be
  very difficult to have.

 --
 Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.


 --
 Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.



-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Harvey OS: A new OS inspired heavily by Plan 9

[Ryan Gonzalez]

No clue. I'm guessing it's heavily inspired by Plan 9.

On July 25, 2015 3:34:13 AM CDT, st...@quintile.net st...@quintile.net 
wrote:
not sure what Harvey is... is it just plan9 ported to build on gcc?

if so does gcc run under Harvey?

does gcc run under plan9 now?

Steve




 On 25 Jul 2015, at 01:43, Ryan Gonzalez rym...@gmail.com wrote:
 

https://medium.com/this-is-not-a-monad-tutorial/harvey-an-operating-system-with-plan-9-s-shadow-3081414e5f0b
 
 I'm not affiliated with this whatsoever; I just saw it on Reddit and
found it interesting.
 
 I found this part particularly neat:
 
  We are working in ANSI POSIX environment to have most of well known
tools and programs that programmers or end users expects to have in a
modern operating system. Things that for traditional Plan 9 would be
very difficult to have.
 
 -- 
 Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.

Re: [9fans] Trying to override 'cd' command

[Ryan Gonzalez]

I think so...

So, in order to get my cd command, I enter '-' at the rc prompt? Is there some 
way for that to happen automatically?

On June 27, 2015 8:34:24 AM CDT, Neven Sajko nsa...@gmail.com wrote:
From the manual:

  -l If -l is given or the first character of argument
 zero is -, rc reads commands from
 $home/lib/profile, if it exists, before reading
 its normal input.

Does this help you?

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [9fans] thank you

[Ryan Gonzalez]

On Fri, Jun 26, 2015 at 2:25 PM, a.regenf...@gmx.de wrote:

 I just wanted to say thank you to Richard Miller (if he is reading this)
 for porting plan 9 to the raspberry pi. Having put so much work into a dead
 os *(uh oh, am i going to get bashed for this?)* is simply great. I am so
 happy having a good platform for running it and experimenting with it.
 Thank you so much.


Probably...



-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] Trying to override 'cd' command

[Ryan Gonzalez]

Finally booted up Plan 9 again. Indeed, the function works when placed in
the shell, but *not in lib/profile*.

I'm putting in $HOME/lib/profile. That's the correct location, right?


On Sat, Jun 13, 2015 at 1:46 PM, Ingo Krabbe ikrabbe@gmail.com wrote:

 try

 whatis cd

 to test if the function as active at all

 btw: I just saw your signature. Great :D

  --
  Ryan
  [ERROR]: Your autotools build scripts are 200 lines longer than your
  program. Something’s wrong.
  http://kirbyfan64.github.io/
 
  --
  Sent from my Android device with K-9 Mail. Please excuse my brevity.






-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] ftpfs shows empty /n/ftp after login

[Ryan Gonzalez]

FYI, for what it's worth, I usually use SSH to sync files between my Linux 
laptop and my Plan 9 VM.

Also, last time I tried, VirtualBox was a bit faster in emulating Plan 9 than 
QEMU, especially without KVM.


On June 25, 2015 12:25:36 PM CDT, Nils M Holm n...@t3x.org wrote:

Hello everybody!

Came back to Plan 9 recently, and I'm running into some trouble.
I'm running Plan 9 on QEMU and wanted to use ftpfs to exchange
data with my FreeBSD system.

When logging in via ftpfs, though, I get an empty /n/ftp directory.

This is how far I got:

My FreeBSD machine runs inetd and logging in to my FTP account
via localhost works fine and shows my home directory.

I'm using QEMU 2.2.1 (i386 emulation, no kqemu). This is what I do:

$ qemu -hda Plan9.qcow 

[ network card is being detected ]
[ log in as glenda ]
[ rio starts up ]

term% ip/ipconfig
term% ndb/dns -r
term% ftpfs 10.0.2.2
220 ananda.local FTP server (Version 6.00LS) ready
!Adding key: proto=pass server=10.0.2.2 service=ftp
user[glenda]: nmh
password: super-secret-password
!
331 Password required for nmh.
230 User nmh logged in.
215 UNIX Type: L8 Version: BSD-199506
257 /u/home/nmh is current directory.
%term

And then it gets weird, I think:

term% ls -l /n/ftp
[ there should be lots of files here ]
term%

The logfile on my FreeBSD machine says:

| Jun 25 19:16:16 ananda ftpd[1316]: connection from localhost
(127.0.0.1)
| Jun 25 19:17:35 ananda ftpd[1316]: FTP LOGIN FROM localhost as nmh

and nothing more.

ns | grep ftp says mount -c '#|/data1' /n/ftp

Does anyone have any idea about what's going on here or how to debug?
It's been a while and my Plan-9-fu is quite rusty.

Thanks,
Nils

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [9fans] ftpfs shows empty /n/ftp after login

[Ryan Gonzalez]

On Thu, Jun 25, 2015 at 2:57 PM, Nils M Holm n...@t3x.org wrote:


 On 2015-06-25T13:09:00-0500, Ryan Gonzalez wrote:
  FYI, for what it's worth, I usually use SSH to sync files between
  my Linux laptop and my Plan 9 VM.

 Thanks for the suggestion! Care to give me a short introduction to
 ssh on Plan 9? I normally avoid ssh like the plague, so I assume I
 know nothing about it.


I don't use FreeBSD, so this might be slightly wrong. :)

Sources:

https://www.freebsd.org/doc/handbook/openssh.html
http://plan9.bell-labs.com/wiki/plan9/connecting_to_other_OSes/index.html

You want to do this in FreeBSD:

- Edit /etc/rc.conf and check if this line is present:

sshd_enable=YES

  If it isn't, add it.

- Edit /etc/ssh/sshd_config and add the following lines:

Protocol 2,1
HostKey /etc/ssh/ssh_host_key
AllowUsers username@plan9_machine_ip_address

- Run:

ssh-keygen -t rsa1 -f /etc/ssh/ssh_host_key
chmod 644 /etc/ssh/ssh_host_key


That's the setup. Now, whenever you want to access your machine's files
from Plan 9, run this on FreeBSD:

service sshd start

And on Plan 9:

ssh username@bsd_machine_ip_address

Type 'yes' at any prompts that pop up.


  Also, last time I tried, VirtualBox was a bit faster in emulating
  Plan 9 than QEMU, especially without KVM.

 VirtualBox is much faster on my machine, but I don't manage to
 set up any network connections at all. NIC is recognized, but
 ip/ipconfig hangs and after configuring manually, not even ip/ping
 works. So I'll stick to QEMU for now.

 --
 Nils M Holm   n m h @ t 3 x . o r g   www.t3x.org




-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

[9fans] GitHub thinks plan9port hasn't been changed in 7 months!

[Ryan Gonzalez]

Kind of funny. For me, the GitHub repo says the last commit was 7 months ago, 
when it was really just last month.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [9fans] make passive aggressive gcc

[Ryan Gonzalez]

Ugh, I know. It caused Judy arrays to segfault a lot.

From my personal experience, Clang does *not* have this problem.


On June 15, 2015 3:21:56 AM CDT, Charles Forsyth charles.fors...@gmail.com 
wrote:
If you're using gcc 4.8.2 to compile ... anything, really ... but
certainly
Plan 9 or Inferno components,
and those use for loops with arrays, be sure to include the compilation
options
-fno-strict-aliasing\
-fno-aggressive-loop-optimizations\
and it will save you some time and effort.
It will save compilation time (not that you'll notice with that
sluggard)
because it won't
fuss even more with your program, and it will save effort, because you
won't have
to debug simple loops that have bounds changed, are removed completely,
or
otherwise wrecked.
You can find discussions of it elsewhere (which is how I found compiler
options to stop it).
I'd forgotten all about it until it surfaced again.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [9fans] Wildly off-topic

[Ryan Gonzalez]

It's always GCC.

On Mon, Jun 15, 2015 at 6:06 PM, Andrew Simmons kod...@gmail.com wrote:

 As the subject line says, wildly off-topic. But some-one here might know
 the answer, and it’s been bothering me.

 Such are my failings, I’ve been watching the second series of “Halt and
 Catch Fire” in order to catch up with what the kids are up to these days.
 In the second episode one of the characters opens what looks like a copy of
 KR first edition, but the cover is blue. I thought that the colour
 correction on my TV might be deceiving me, or possibly the vertical hold
 was on the fritz, but he did it again in the third episode, and the cover
 was still blue.

 So my question is, did there ever exist an edition of KR in that colour
 scheme, or is gcc to blame for the inaccuracy?




-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] Trying to override 'cd' command

[Ryan Gonzalez]

I added it to the end of lib/profile.

On June 13, 2015 3:02:56 AM CDT, Ingo Krabbe ikrabbe@gmail.com wrote:
I tried it in a fresh window, where it works for me.

 Thanks for replying! Unfortunately, that doesn't change anything.
Still
 stuck at the 'term% ' prompt.
 
 
 On Sun, Jun 7, 2015 at 6:43 PM, Ingo Krabbe ikrabbe@gmail.com
wrote:
 
 try it with

 fn cd{
 builtin cd $1
 prompt=(`{pwd}^'% ' '')
 }

 the difference is `{pwd} not '{pwd}.



  Coming from a bash world, I really like knowing what directory I'm
in at
  the prompt. I tried putting this at the end of 'lib/profile':
 
 
 
  fn cd{
  builtin cd $1
  prompt=('{pwd}^'% ' '')
  }
 
  cd $HOME
 
 
 
  However, it doesn't work! The 'cd' command seems to do what it
normally
  does. The prompt stays at 'term% '. Does nothing.
 
  --
  Ryan
  [ERROR]: Your autotools build scripts are 200 lines longer than
your
  program. Something’s wrong.
  http://kirbyfan64.github.io/



 
 
 -- 
 Ryan
 [ERROR]: Your autotools build scripts are 200 lines longer than your
 program. Something’s wrong.
 http://kirbyfan64.github.io/

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [9fans] Trying to override 'cd' command

[Ryan Gonzalez]

Thanks for replying! Unfortunately, that doesn't change anything. Still
stuck at the 'term% ' prompt.


On Sun, Jun 7, 2015 at 6:43 PM, Ingo Krabbe ikrabbe@gmail.com wrote:

 try it with

 fn cd{
 builtin cd $1
 prompt=(`{pwd}^'% ' '')
 }

 the difference is `{pwd} not '{pwd}.



  Coming from a bash world, I really like knowing what directory I'm in at
  the prompt. I tried putting this at the end of 'lib/profile':
 
 
 
  fn cd{
  builtin cd $1
  prompt=('{pwd}^'% ' '')
  }
 
  cd $HOME
 
 
 
  However, it doesn't work! The 'cd' command seems to do what it normally
  does. The prompt stays at 'term% '. Does nothing.
 
  --
  Ryan
  [ERROR]: Your autotools build scripts are 200 lines longer than your
  program. Something’s wrong.
  http://kirbyfan64.github.io/





-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

[9fans] Trying to override 'cd' command

[Ryan Gonzalez]

Coming from a bash world, I really like knowing what directory I'm in at
the prompt. I tried putting this at the end of 'lib/profile':



fn cd{
builtin cd $1
prompt=('{pwd}^'% ' '')
}

cd $HOME



However, it doesn't work! The 'cd' command seems to do what it normally
does. The prompt stays at 'term% '. Does nothing.

-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] ot: pascal rides again?

[Ryan Gonzalez]

On May 24, 2015 2:00:05 PM CDT, Bakul Shah ba...@bitblocks.com wrote:


On May 24, 2015, at 8:55 AM, erik quanstrom quans...@quanstro.net
wrote:

 Uhm I might be mistaken, but I guess [8192]byte is an array, and
[]byte are
 slices - therefore they are different types.
 
 yes, exactly.  i suppose this implies that different size arrays are
not type compatable
 (yea pascal).  also the fu := bar[:] looks a lot like the tedious
casting from c, and implies
 dynamic allocation of the slice, i'm guessing.
 
 - erik
 
Later pascal standards supported conformant array parameters. And
several extended pascal compilers provided dynamic arrays.

In Go multidimensional arrays are not well supported. Try this:

var x [5][6]int
y := x[:2][:3]
fmt.Printf(%v\n, y)

It is what it is. Get used to it if you want/have to use Go! Apart from
its concurrency features it is a pretty boring language but it is
surprisingly easy to write code in it.

Seriously. I like Nim better. And K...


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [9fans] ot: pascal rides again?

[Ryan Gonzalez]

Go array =~ C++ std::array
Go slice =~ C++ std::vector


On May 24, 2015 12:02:54 PM CDT, Aram Hăvărneanu ara...@mgk.ro wrote:
On Sun, May 24, 2015 at 5:55 PM, erik quanstrom quans...@quanstro.net
wrote:
 and implies dynamic allocation of the slice, i'm guessing.

Don't guess. Please read the links I provided, they explain all this.
Arrays in Go are not like arrays in C and Pascal, slices are more
close. Go arrays are values, so copying one is an O(n) operation.

-- 
Aram Hăvărneanu

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[9fans] Empty plan9.iso.bz2?

[Ryan Gonzalez]

Just decided to download the newest CD image and ended up downloading an
empty archive. I tried downloading via Curl and Chrome, with both giving
the same results.

-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] Empty plan9.iso.bz2?

[Ryan Gonzalez]

Nevermind. I was being stupid and trying to extract the bz2 archive with
tar...


On Sat, May 23, 2015 at 4:06 PM, Ryan Gonzalez rym...@gmail.com wrote:

 Just decided to download the newest CD image and ended up downloading an
 empty archive. I tried downloading via Curl and Chrome, with both giving
 the same results.

 --
 Ryan
 [ERROR]: Your autotools build scripts are 200 lines longer than your
 program. Something’s wrong.
 http://kirbyfan64.github.io/





-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

[9fans] I killed plan9.ini; what to do?

[Ryan Gonzalez]

I was tweaking plan9.ini for autologin and must have typed something wrong
because I got this:

[image: Inline image 1]

I want to try to fix it, but I don't know how. Do I need to reinstall Plan
9 again?

-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] Is it *legal* to use the Plan 9 regex library from MIT-licensed code?

[Ryan Gonzalez]

Ah! Looks really close to the MIT license.

Thanks!

On May 23, 2015 3:36:11 AM CDT, David du Colombier 0in...@gmail.com wrote:
The libregexp license is available here:

https://github.com/9fans/plan9port/blob/master/unix/NOTICE.regexp

It's part of the standalone Unix ports.

-- 
David du Colombier

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [9fans] ot: pascal rides again?

[Ryan Gonzalez]

I read the Go docs *once*, but I'm pretty sure you're right.

I think to make a slice out of an array, you'd do something like the_array[:].

All to say why I don't like Go. :)

On May 23, 2015 1:14:55 PM CDT, C Cirello uldericofi...@gmail.com wrote:
Uhm I might be mistaken, but I guess [8192]byte is an array, and []byte
are
slices - therefore they are different types.

- CC

2015-05-23 17:53 GMT+02:00 erik quanstrom quans...@quanstro.net:

 well, at least dennis wrote why pascal is not my favorite
programming
 language.

 from go build

 ./cat.go:36: cannot use data (type [8192]byte) as type []byte
in
 argument to cat

 what?  perhaps i'm missing something about the language, but it sure
seems
 ironic.

 - erik



-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [9fans] Is it *legal* to use the Plan 9 regex library from MIT-licensed code?

[Ryan Gonzalez]

Oh, yeah, almost forgot: the plan9port license says to see the LICENSE file
in the libregexp directory...which isn't there...


On Fri, May 22, 2015 at 6:53 PM, Ryan Gonzalez rym...@gmail.com wrote:

 Dang, I didn't want to send that yet. Thanks a lot, Gmail...

 Basically, I tend to get worried when it comes to licensing (who wants to
 get sued?) and want to make sure that this is OK.


 On Fri, May 22, 2015 at 6:52 PM, Ryan Gonzalez rym...@gmail.com wrote:



 --
 Ryan
 [ERROR]: Your autotools build scripts are 200 lines longer than your
 program. Something’s wrong.
 http://kirbyfan64.github.io/





 --
 Ryan
 [ERROR]: Your autotools build scripts are 200 lines longer than your
 program. Something’s wrong.
 http://kirbyfan64.github.io/





-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] Is it *legal* to use the Plan 9 regex library from MIT-licensed code?

[Ryan Gonzalez]

Dang, I didn't want to send that yet. Thanks a lot, Gmail...

Basically, I tend to get worried when it comes to licensing (who wants to
get sued?) and want to make sure that this is OK.


On Fri, May 22, 2015 at 6:52 PM, Ryan Gonzalez rym...@gmail.com wrote:



 --
 Ryan
 [ERROR]: Your autotools build scripts are 200 lines longer than your
 program. Something’s wrong.
 http://kirbyfan64.github.io/





-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

[9fans] Is it *legal* to use the Plan 9 regex library from MIT-licensed code?

[Ryan Gonzalez]

-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] 3d Glenda

[Ryan Gonzalez]

That's adorable!

On May 14, 2015 11:57:31 AM CDT, Kurt H Maier k...@sciops.net wrote:
Quoting Andrés Domínguez andres...@gmail.com:

 Does anyone have a 3d model of Glenda?

http://glenda.cat-v.org/gallery/stuffed-glenda.jpg

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [9fans] C.H.I.P. - world's first $9 computer

[Ryan Gonzalez]

Until that comes out, I'll be slightly skeptical.

But Plan 9 on that would be pretty cool!

On May 11, 2015 6:32:39 PM CDT, Bakul Shah ba...@bitblocks.com wrote:
https://www.kickstarter.com/projects/1598272670/chip-the-worlds-first-9-computer/

40mmx60mm
1GHz Allwinner R8 processor + 512MB memory + 4GB storage +
wifi + Bluetooth

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [9fans] using git

[Ryan Gonzalez]

Is all that even necessary?

Dulwich is a 100%-complete pure-Python implementation of the Git API, which
optional C extensions for speed. It comes with a simple Git driver remake
that implements the core necessities, a.k.a. it has fetch-pack but no push
and send-pack but no pull. It would still probably easier to extend/finish
that than writing a driver from scratch in C.


On Mon, Mar 30, 2015 at 3:20 PM, Giacomo Tesio giac...@tesio.it wrote:

 Actually, Jeff I appreciate a lot your work on mercurial. I know I could
 use the bookmarks extension to achieve a similar process with hg (never
 tried darcs and bzr seriously, sorry). but I still prefer git to mercurial,
 since it has been designed around the features that I like (when working
 alone) or need (when working in large team over years long projects).

 But this is personal taste, and I'm not a git evangelist. I just replied
 to Charles asking for the features we use in git.

 Btw, ever heard of http://libgit2.org ?
 Plain c89. No external dependencies.

 In theory, one could implement a native gitfs over that, in C, using the
 network fs available in Plan9.

 Compared to hgfs, a bit more design of the fs structure would probably be
 needed to capture the concept of branch in a hierarchical filesystem.

 How much you would estimate such development?


 Giacomo



 2015-03-30 18:16 GMT+02:00 Jeff Sickel j...@corpus-callosum.com:


  On Mar 30, 2015, at 4:55 AM, Giacomo Tesio giac...@tesio.it wrote:
 
  Ah, a small addendum: obviously we also use tags a lot to give a
 specific commit (and related history) a name.
  This is done automatically by build servers for the official tags,
 and manually by developers whenever they want in their own repository
 (often with tags like, workedhere, shittorefactortomorrow and so on).

 All of those features are available in hg, darcs, and other dscm tools.

 But to get back on topic, unless I’ve overlooked a contrib package
 somewhere, how about we begin with the requirements to get a fully working
 git installed on Plan 9.  For example,

 ## the dependencies required for git on a bare-bones FreeBSD install:
 # pkg install git
 Updating FreeBSD repository catalogue...
 FreeBSD repository is up-to-date.
 All repositories are up-to-date.
 The following 18 packages will be affected (of 0 checked):

 New packages to be INSTALLED:
 git: 2.3.4
 expat: 2.1.0_2
 p5-Authen-SASL: 2.16_1
 p5-GSSAPI: 0.28_1
 perl5: 5.18.4_11
 p5-Digest-HMAC: 1.03_1
 p5-Net-SMTP-SSL: 1.01_3
 p5-IO-Socket-SSL: 2.012
 p5-Mozilla-CA: 20141217
 p5-Net-SSLeay: 1.68
 p5-Socket: 2.018
 p5-IO-Socket-IP: 0.37
 python27: 2.7.9
 libffi: 3.2.1
 p5-Error: 0.17023
 curl: 7.41.0
 ca_root_nss: 3.18
 cvsps: 2.1_1



 I’m not sure what cvsps is for, that seems to have cropped up on the fbsd
 pkg sometime between git versions 2.3.1 and 2.3.4.  It’s been
 years^wdecades since I’ve tinkered with perl, and I’m fairly certain the
 perl 5.8 version available on Plan 9 won’t support the modules included in
 the above list.  So Plan 9 needs a modern perl to run git effectively with
 specific attention to the additional modules.  Expat is the “eXpat XML
 parser library”.  Libffi is something maintained on sources.redhat.com.
 Many of those modules depend on OpenSSL, so add that to the list.  It’s
 also possible a recent port of bash will also be required as the git
 support scripts may not work with our ape/sh or ape/psh.  We’ve got python
 2.7.8 [.9 soon] covered.

 Piece of cake, all that should fit on a coaster.

 -jas









-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] plan 9 file

[Ryan Gonzalez]

The file command just makes guesses based on the file's content. I've had
it tell me build scripts were C source files and that various other files
(most particularly Makefiles) are ASCII text.

On Wed, Mar 18, 2015 at 3:36 PM, Adrian Regenfuss a.regenf...@gmx.de
wrote:

 Hey, just found something interesting:
 When you run file on /rc/lib/rcmain, it tells me that it is «English
 text». I didn't look at the source of file yet,
 but if you cat rcmain it really doesn't look like «English text».
 Have there been similar mistakes or has it been working fine most of the
 time?
 Adrian

 P.S: Sorry for my bad english…
 P.P.S: By the way: I know how to do a screenshot in Plan 9, but how do I
 make a screen recording? Does plan 9
 deal with video files in any way?




-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] code.google.com/p/nix-os

[Ryan Gonzalez]

The Google Code page this was imported from says this:

Nix is a new multicore OS based on Plan9.

It also hasn't been developed since 2012.

The wiki didn't get moved, though.

On Mon, Mar 16, 2015 at 12:00 PM, Bence Fábián beg...@gmail.com wrote:

 Which nix-os is this?
 Also github recognized the mkfiles as javascript :)

 2015-03-16 17:03 GMT+01:00 ron minnich rminn...@gmail.com:

 is now at github.com/rminnich/nix-os

 Just for historical interest.

 ron





-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] ken cc for linux

[Ryan Gonzalez]

I prefer GitHub. Much nicer, easier to use, has a PR system (no patches!),
etc.

The website also works better on mobile devices. Google Code's source
browser doesn't work on my phone.

I wouldn't say it suddenly vanished, though. A quick search shows some were
predicting this would happen. Lots of major projects have moved to GitHub
or Bitbucket.

On Fri, Mar 13, 2015 at 8:24 AM, Charles Forsyth charles.fors...@gmail.com
wrote:


 On 13 March 2015 at 01:31, erik quanstrom quans...@quanstro.net wrote:

 was, as in google code is dead.


 It's a good example of how the cloudy future is seriously unsettled by
 services suddenly vanishing,
 even from big suppliers. Also, I rather trust the Google storage
 infrastructure, but I'm not sure about the other two.




-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] ken cc for linux

[Ryan Gonzalez]

I know. I'm referring to the ken-cc port.

On Thu, Mar 12, 2015 at 3:51 AM, Aram Hăvărneanu ara...@mgk.ro wrote:

 On Wed, Mar 11, 2015 at 10:04 PM, Ryan Gonzalez rym...@gmail.com wrote:
  As you can see, Go actually had a working 64-bit compiler.

 Plan 9 and Inferno have working 64-bit compilers. They are used for
 the many Plan 9 amd64 kernels. Go's C compilers all came from Inferno,
 including 6c.

 --
 Aram Hăvărneanu




-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] ken cc for linux

[Ryan Gonzalez]

On Thu, Mar 12, 2015 at 3:50 AM, Aram Hăvărneanu ara...@mgk.ro wrote:

 On Wed, Mar 11, 2015 at 10:04 PM, Ryan Gonzalez rym...@gmail.com 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ăvărneanu




-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] ken cc for linux

[Ryan Gonzalez]

Warning: this will get messy *fast*.

On Wed, Mar 11, 2015 at 3:30 PM, Aharon Robbins arn...@skeeve.com wrote:

 Thanks for the link to the Google code repo.

 I'm currently on x86_64 Ubuntu 12.04. Building was not so smooth, several
 files are missing for the Power 64 port.


Yup. Comment out the lines in the mkfiles. In src/cmd/mkfile, I commented
out lines 34-36.

I think you already need mk installed; you can grab it from here
http://swtch.com/plan9port/unix/mk-with-libs.tgz.



 I did as best I could to build things.  I suppose my expectations aren't
 what they should be. I was looking for the usual

 configure  make  make install

 experience, and it wasn't there. I like to compile gawk with multiple
 compilers and thought I'd try ken's, but it wasn't clear to me which
 o.out file to use, or how to install it such that it will get the
 system's include files and libraries.


I doubt the Plan 9 compilers will even get *close* to building gawk.

See, the compilers implement a variant of ANSI C with some C99-ish
extensions. For once, the preprocessor does not work with #if's. You can
only use #ifdef's.

Because of this, 99% of the C standard library headers will NOT work with
the compilers.

Another issue is that it seems that the linker does not read ELF files, so
linking with about anything is out of the question.

As for the compilers you need to invoke...

The directories in src/cmd are formatting like *n*c, *n*a, and *n*l, where
the *c ones are the compiles, *a, the assemblers, and *l, the linkers.

The executable is at src/cmd/dir/o.out. For Ubuntu 64-bit, you'll want
src/cmd/6c/o.out to compile and src/cmd/6l/o.out to link. Or, at least you
would...if the files weren't missing. Since half of them are, you'll
instead want src/cmd/8c/o.out to compile and src/cmd/8l/o.out to link.
Those are the 32-bit compilers.

I set up symlinks in ken-cc/bin using bin/8c as an alias for
src/cmd/8c/o.out. Same thing for 8l.

The command lines look something like:

8c tst.c # outputs tst.8
8l -o tst tst.8 # outputs tst

Bottom line: you may be out of luck if you want to use ken-cc as a
general-purpose C compiler. It isn't. At all.

It's fun to toy with, though.

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

As you can see, Go actually had a working 64-bit compiler.

I have yet to figure out why the hell symlinks to the compilers never get
set up in the bin directory.


 If this is easy to do, I'd appreciate hearing how. If not, then I'm not
 going to worry about it. :-)

 Much thanks,

 Arnold




-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] ken cc for linux

[Ryan Gonzalez]

That's ape with ape/pcc, which is ANSI-compliant, not a port of the
non-compliant base compilers (6c, 8c, etc.).

On Wed, Mar 11, 2015 at 4:54 PM, Quintile st...@quintile.net wrote:


 awl compiles under APE with a little work. someone, sorry I have forgotten
 who, did Stirling work a few years ago and got many Linux tools ported - to
 support 3rd party stuff. to my chagrin I never managed to get avn to work
 on top of this.

 the code was in Google code I think, his porting instructions should work
 for the latest gawk too.

 if not put the code somewhere and I will have a go.

 -Steve





 On 11 Mar 2015, at 21:04, Ryan Gonzalez rym...@gmail.com wrote:

 Warning: this will get messy *fast*.

 On Wed, Mar 11, 2015 at 3:30 PM, Aharon Robbins arn...@skeeve.com wrote:

 Thanks for the link to the Google code repo.

 I'm currently on x86_64 Ubuntu 12.04. Building was not so smooth, several
 files are missing for the Power 64 port.


 Yup. Comment out the lines in the mkfiles. In src/cmd/mkfile, I commented
 out lines 34-36.

 I think you already need mk installed; you can grab it from here
 http://swtch.com/plan9port/unix/mk-with-libs.tgz.



 I did as best I could to build things.  I suppose my expectations aren't
 what they should be. I was looking for the usual

 configure  make  make install

 experience, and it wasn't there. I like to compile gawk with multiple
 compilers and thought I'd try ken's, but it wasn't clear to me which
 o.out file to use, or how to install it such that it will get the
 system's include files and libraries.


 I doubt the Plan 9 compilers will even get *close* to building gawk.

 See, the compilers implement a variant of ANSI C with some C99-ish
 extensions. For once, the preprocessor does not work with #if's. You can
 only use #ifdef's.

 Because of this, 99% of the C standard library headers will NOT work with
 the compilers.

 Another issue is that it seems that the linker does not read ELF files, so
 linking with about anything is out of the question.

 As for the compilers you need to invoke...

 The directories in src/cmd are formatting like *n*c, *n*a, and *n*l,
 where the *c ones are the compiles, *a, the assemblers, and *l, the linkers.

 The executable is at src/cmd/dir/o.out. For Ubuntu 64-bit, you'll want
 src/cmd/6c/o.out to compile and src/cmd/6l/o.out to link. Or, at least you
 would...if the files weren't missing. Since half of them are, you'll
 instead want src/cmd/8c/o.out to compile and src/cmd/8l/o.out to link.
 Those are the 32-bit compilers.

 I set up symlinks in ken-cc/bin using bin/8c as an alias for
 src/cmd/8c/o.out. Same thing for 8l.

 The command lines look something like:

 8c tst.c # outputs tst.8
 8l -o tst tst.8 # outputs tst

 Bottom line: you may be out of luck if you want to use ken-cc as a
 general-purpose C compiler. It isn't. At all.

 It's fun to toy with, though.

 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

 As you can see, Go actually had a working 64-bit compiler.

 I have yet to figure out why the hell symlinks to the compilers never get
 set up in the bin directory.


 If this is easy to do, I'd appreciate hearing how. If not, then I'm not
 going to worry about it. :-)

 Much thanks,

 Arnold




 --
 Ryan
 [ERROR]: Your autotools build scripts are 200 lines longer than your
 program. Something’s wrong.
 http://kirbyfan64.github.io/





-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] whence kenc for linux?

[Ryan Gonzalez]

The Go version also has more features (the linker actually supports ELF
objects).

My concern is the fact that more and more of Go is slowly being rewritten
in Go, so I'm not sure how long the compilers will stick around, or at
least in their current state.

On Tue, Mar 10, 2015 at 3:48 PM, Roberto E. Vargas Caballero 
k...@shike2.com wrote:

  Where's the right place to find kenc for Linux?
 
  https://code.google.com/p/ken-cc/

 I found easier to take it from the go distribution






-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] whence kenc for linux?

[Ryan Gonzalez]

I meant reading ELF files, not writing them. Last time I tried with ken-cc,
it didn't work.

But I didn't realize Go removed the C compilers. Do you know why?

On Tue, Mar 10, 2015 at 5:30 PM, Aram Hăvărneanu ara...@mgk.ro wrote:

 The Plan 9 C compilers included with Go have been removed for some
 time. Also they worked quite differently than the Plan 9 ones because
 of liblink.

 The Plan 9 linker also supports ELF, although it lacks DWARF and a
 symbol table in the generated binaries.

 --
 Aram Hăvărneanu




-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] whence kenc for linux?

[Ryan Gonzalez]

Aw, man...

On Tue, Mar 10, 2015 at 5:45 PM, minux minux...@gmail.com wrote:


 On Mar 10, 2015 6:37 PM, Ryan Gonzalez rym...@gmail.com wrote:
 
  I meant reading ELF files, not writing them. Last time I tried with
 ken-cc, it didn't work.
 
  But I didn't realize Go removed the C compilers. Do you know why?

 Because Go runtime is now implemented in Go and assembly, not a
 combination of C, Go and assembly as it was before, so the C compilers are
 not needed anymore. The last versions to have those compilers is the 1.4
 series.




-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/

Re: [9fans] Standalone *nix port of sam

[Ryan Gonzalez]

Looks great!

However, I would advise against the CC=cc... lines in the makefiles. They
break badly when I execute the commonly-done `make CC=my_compiler`. In
particular, the Makefile in sam/sam has this:

CC=cc $(SYSFLAGS)

Which obviously breaks when I set CC to a custom compiler. Can't SYSFLAGS
be added to CFLAGS instead?

On Thu, Feb 5, 2015 at 10:22 AM, Rob King jk...@deadpixi.com wrote:

 Hello everyone,
 I don't know how much interest there'd be, but if anyone ever needs
 to run sam standalone on *nix (that is, without plan9port), there's a
 standalone version available. It's based on the original port to X11
 back in the 80s released by Lucent in 1989 or so.

 There aren't any dependencies other than Xlib/Xft, and it comes with
 scalable font support, a much improved B shell command (handles multiple
 instances of sam, and even better can be invoked on any machine involved
 in a sam -r session, even the remote one), and a few other changes.

 So yeah, it's not sam on Plan 9, but I have to use Linux on my work
 machines and can't install plan9port on them, so...there ya go. It
 should work on other *nix systems too, but I don't have any to try it
 out on. The code isn't pretty; I just hacked on it until I got it
 working the way I wanted to, but it's been stable enough for me.

 The source is at http://www.deadpixi.com/an-updated-version-of-sam

 Please let me know if you have any questions.

 Rob





-- 
Ryan
If anybody ever asks me why I prefer C++ to C, my answer will be simple:
It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
nul-terminated.
Personal reality distortion fields are immune to contradictory evidence. -
srean
Check out my website: http://kirbyfan64.github.io/

Re: [9fans] Do Plan9Port's lib9 and libbio work on Windows?

[Ryan Gonzalez]

pf9 looks interesting, although it took a bit of hunting to find it
(largely because it has the same name as a gun!).

My worry right now is that it won't work with the newest plan9port, since
it hasn't been updated since last year.

What I probably need to do is just make my own port and keep it in sync
with the GitHub repo, since the vibe I'm getting is that most of the stuff
that needs changing is stuff that I'm not going to use, and the rest of the
stuff resides in headers.

Thanks to all who answered!

On Sat, Nov 29, 2014 at 2:19 AM, Quintile st...@quintile.net wrote:

 yes

 there is pf9 for windows, which is a port of p9p.

 I have also been working on my own port for years, more orientated towards
 using a windows box as a cup server. shout if you want that.

 Steve





 On 29 Nov 2014, at 00:54, Ryan Gonzalez rym...@gmail.com wrote:

 I Google'd it, but I didn't find anything. Does it build?

 --
 Ryan
 If anybody ever asks me why I prefer C++ to C, my answer will be simple:
 It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
 nul-terminated.
 Personal reality distortion fields are immune to contradictory evidence. -
 srean
 Check out my website: http://kirbyfan64.github.io/




-- 
Ryan
If anybody ever asks me why I prefer C++ to C, my answer will be simple:
It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
nul-terminated.
Personal reality distortion fields are immune to contradictory evidence. -
srean
Check out my website: http://kirbyfan64.github.io/

Re: [9fans] github.com/9fans + plan9port on git

[Ryan Gonzalez]

Ooohhh...this is great! I'm really glad for this change.

On Sun, Nov 16, 2014 at 9:49 PM, Russ Cox r...@swtch.com wrote:

 i have moved the plan9port sources from mercurial to git. the instructions
 at http://swtch.com/plan9port/man/man1/install.html are up-to-date: you
 can still install by downloading a .tgz, or you can use git clone. it's
 entirely possible i've missed some things. let me know on plan9port-dev or
 send a code review (see 9 man codereview).

 perhaps more substantially, i created a github.com/9fans organization.
 right now it's just plan9port, and i intended to add drawterm. if anyone
 else wants to host plan9-related things there, i'm happy to add more owners.

 thanks.
 russ




-- 
Ryan
If anybody ever asks me why I prefer C++ to C, my answer will be simple:
It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
nul-terminated.
Personal reality distortion fields are immune to contradictory evidence. -
srean
Check out my website: http://kirbyfan64.github.io/

[9fans] Can the 8l linker read ELF object files?

[Ryan Gonzalez]

I have a simple C program:

#include lib9.h

void main()
{
print(abc\n);
exits(nil);
}

I built it under Linux using ken-cc (the Linux port of the Plan 9
compilers). However, this happens when I try to link it:

8l -L/home/ryan/stuff/ken-cc/Linux/386/lib -l9 -o test test.8
main: undefined: print
main: undefined: exits

Evidently, 8l isn't picking up the ELF objects in lib9.a. Can I make it
read them somehow?

-- 
Ryan
If anybody ever asks me why I prefer C++ to C, my answer will be simple:
It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
nul-terminated.
Personal reality distortion fields are immune to contradictory evidence. -
srean
Check out my website: http://kirbyfan64.github.io/

Re: [9fans] tlsClient: tls: local invalid x509/rsa certificate

[Ryan Gonzalez]

Thanks! I just tested it. It works!

On Sun, Oct 26, 2014 at 5:52 PM, David du Colombier 0in...@gmail.com
wrote:

 Just to be clearer. The patch (unified diff) attached in my
 previous email can be applied with ape/patch.

 A patch(1) (/n/sources/patch) can't be applied automatically
 without modifying patch/apply. You have to copy the individual
 files by hand to the destination indicated in the files file.

 --
 David du Colombier




-- 
Ryan
If anybody ever asks me why I prefer C++ to C, my answer will be simple:
It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
nul-terminated.
Personal reality distortion fields are immune to contradictory evidence. -
srean
Check out my website: http://kirbyfan64.github.io/

[9fans] tlsClient: tls: local invalid x509/rsa certificate

[Ryan Gonzalez]

I'm trying to download the a Python script and keep running into trouble. I
am running this:

hget https://hg.python.org/cpython/raw-file/4391ab72dd7b/Lib/types.py 
types.py

However, hget keeps complaining with `tlsClient: tls: local invalid
x509/rsa certificate`. The time and date of my Plan 9 VM are correct and
are set to sync with pool.ntp.org. I have NO clue what's wrong. Can anybody
help?

-- 
Ryan
If anybody ever asks me why I prefer C++ to C, my answer will be simple:
It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
nul-terminated.
Personal reality distortion fields are immune to contradictory evidence. -
srean
Check out my website: http://kirbyfan64.github.io/

Re: [9fans] tlsClient: tls: local invalid x509/rsa certificate

[Ryan Gonzalez]

Thanks! Quick question: how do I apply the patch? I didn't see an argument
to diff or a patch utility.

On Sun, Oct 26, 2014 at 5:30 PM, David du Colombier 0in...@gmail.com
wrote:

 The patch is now available here:

 /n/sources/patch/libsec-x509-sha256rsa

 --
 David du Colombier




-- 
Ryan
If anybody ever asks me why I prefer C++ to C, my answer will be simple:
It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
nul-terminated.
Personal reality distortion fields are immune to contradictory evidence. -
srean
Check out my website: http://kirbyfan64.github.io/