Well it's not that simple, the X11 version uses freetype2 and fontconfig to
read/render TrueType fonts..
The OS X is probably doing something similar with Apple's APIs
On Fri, Dec 13, 2013 at 7:26 PM, Friedrich Psiorz wrote:
> I would really like to have fontsrv in native Plan 9. It's nice to b
= data
@@ -466,7 +467,7 @@
done := make(chan *Req)
req := clnt.ReqAlloc()
req.Done = done
-tc := req.Tc
+tc := &req.Tc
tc.Id = vt.Tsync
err = clnt.Rpcnb(req)
if err != nil {
On Sat, Jul 6, 2013 at 1:52 PM, Pavel Zholkover wrote:
> Hi all,
>
> Does anyone use
Hi all,
Does anyone use the http://http://code.google.com/p/govt package for
client side venti ?
I had to apply the attached patch to be able to read a vac score.
Thanks,
- Pavel
govt_client_fixes.diff
Description: Binary data
Hi all!
I did a small port of the p9p libthread to CPython 2.7.3 and up using the
greenlet module.
https://bitbucket.org/paulzhol/libtask9
You might find it useful if like me, you failed to convince your peers to
switch to Go :)
-paulzhol
CGO will generate C code stubs that require gcc to compile.
The gcc generated executable (_cgo_.o in the example bellow) is then
parsed for it's dwarf debug info
(I think) to get import the names and dso's of imported symbols.
Later, when you build an executable using the cgo'd package; 6l will
gen
I've looked at
http://code.swtch.com/plan9port/src/9574d432c889/src/cmd/9pfuse/main.c#cl-580
and O_NOFOLLOW == 040 handling was added in
http://code.swtch.com/plan9port/changeset/43f43652132d
So maybe you can recompile a more recent version ?
On Thu, Mar 22, 2012 at 8:30 PM, Pavel Zhol
I've also encountered this on my synology DS411 linux based kirkwood
NAS. If I remember correctly I saw a comment by Russ regarding
weird/unhandled flags being passed to the open syscall.
My workaround was just to compile a 9p kernel module and mount the
vacfs export with it.
On Thu, Mar 22, 2012
Is the builder going to be based on the native build or will it be
cross-compiled ?
Thanks!
On Thu, Dec 1, 2011 at 8:18 PM, Anthony Martin wrote:
# In other news, I'm working on setting up an
# an automated builder so we can include Plan 9
# in the Go Dashboard.
> setting up cross-compilation with gcc, and even using it once set up,
> has historically been surprisingly complicated; has that changed?
>
I'm not sure about gcc, but the go toolchain can produce quite well working
Plan 9 binaries.
Taru also has the go toolchain running native in itself after
The following executables are installed into $GOROOT/bin as Plan 9
a.out binaries when you run make -k install inside src/pkg:
cgo, ebnflint, gofix, gofmt, gotest, gotype, govet, goyacc, hgpatch.
They should be directed somewhere else by setting GOBIN, there is no
need to include them in your PATH,
=plan9 GOBIN=$GOROOT/bin/plan9 make -k install
Pavel
On Sat, Apr 9, 2011 at 10:04 PM, Skip Tavakkolian
wrote:
> Great info! thanks.
> -Skip
>
> On Sat, Apr 9, 2011 at 11:53 AM, Pavel Zholkover wrote:
>> The mainline go will not compile syscall after the last post-weekly tag
The mainline go will not compile syscall after the last post-weekly tag due
to the mmap support.
Russ wrote he'll look into it next week.
I try to maintain the bitbucket patch que with CLs still being reviewed
(Anthony's time changes for example) so people can test them as a whole.
There is no ne
Try make -k install like in the wiki instructions. This should continue
building packages even if some fail to compile.
On Apr 9, 2011 8:53 PM, "Sergey Kish" wrote:
> Hello,
>
> I'm unable to make go plan9 crosscompiler.
> Can you help me?
>
> # I use patched repo
> hg qclone https://bitbucket.or
On Tue, Apr 5, 2011 at 7:33 AM, Lucio De Re wrote:
> No, and no "yuck", either: Go executables are different animals and
> they are allowed to be identified as such. Until they are not, when
> they are allowed to become the same animal.
> snip...
>
> And maybe it's just me being uninformed, but I
On Mon, Apr 4, 2011 at 8:27 PM, Lucio De Re wrote:
> PS: Would anybody like to summarise for us plebs whether there is any
> convergence looming between Go and Plan 9 on the x64 front? It seems
> sad to miss a chance to add a peer-reviewed and thoroughly tested 64-bit
> toolchain to Plan 9.
the
Thanks for the detailed explanation, I've added your patch to if that
is alright with you https://bitbucket.org/paulzhol/golang-plan9-
runtime-patches/
Pavel
On Mon, Apr 4, 2011 at 1:30 AM, Anthony Martin wrote:
> Pavel Zholkover once said:
>> I'm not sure I understand the r
I'm not sure I understand the reason 9vx will fail to reserve 768mb
with brk() while my Plan 9 install on kvm+qemu with 128mb or ram works
fine, as long as it is not written to.
The -s is no longer needed, 8l generates a.out symbols correctly.
Pavel
On Mon, Apr 4, 2011 at 12:16 AM, Anthony Marti
What about the old gcc3 port? Is it enough for bootstrapping the compilers?
On Apr 3, 2011 7:28 PM, "Skip Tavakkolian"
wrote:
On Apr 3, 2011 12:18 PM, "erik quanstrom" wrote:
> okay, i volunteer. just to make sure, we're talking
> about a plan 9 port, not a cross compile?
>
> just let me know what i need to get set up. i can
> easily do 386 and arm at this point.
>
> - erik
>
I think Rob meant it would be a cross compi
On Sun, Apr 3, 2011 at 2:52 AM, David Leimbach wrote:
> So wait... We can get the toolchain built on plan 9. Or we can target plan 9
> via cross compiler? Either way is pretty awesome! Nice work!
We are cross-compiling unless someone syncs
http://code.google.com/p/go-plan9/ with mainline.
Pav
I've set up a Mercurial patch queue with some instructions on building
at https://bitbucket.org/paulzhol/golang-plan9-runtime-patches/
with Andrey and Taru's patches. I'll try to keep it updated :)
Pavel
Hi all!
Rob just committed my syscall and os Plan 9 patches into mainline.
The produced binaries do not run properly on 9vx since the last gc changes
so its native or kvm+qemu etc.
Please test :)
Pavel
On Sat, Jan 15, 2011 at 11:30 AM, wrote:
> In a nutshell, I actually took a very recent release of Go and tried
> to build a Plan 9 version:
>
> cd $GOROOT/src
> GOOS=plan9 ./make.bash
>
> I was not surprised that it did not build correctly on my Ubuntu
> workstation. Fixing it did
On Sat, Jan 15, 2011 at 4:00 AM, Anthony Martin wrote:
> Pavel Zholkover once said:
>> I have no idea what is causing it to die, I've tried adding a bunch of
>> INT $3 to see how far in the flow I can get, but all I get this:
>>
>> 9vx panic: unknown trap/intr:
On Sat, Jan 15, 2011 at 11:01 AM, wrote:
> I'm a bit cinfusing...
>
> There is a flag (GPOS=plan9) to ebnable plan9 os in the standard Go
> dsitribution.
> How the patches you posted here now and before are related to that flag.
> I suppose the original plan9 flag is for plan9port.
> Am I correc
> main9.s sets _tos on entry. why not just use _tos as
> the c glue code does?
>
> - erik
>
>
I'm already setting _tos on entry:
http://code.google.com/p/go/source/browse/src/pkg/runtime/plan9/386/rt0.s
TEXT _rt0_386_plan9(SB),7, $0
MOVLAX, _tos(SB)
// move arguments
I did the runtime port a few month ago, now waiting for
http://codereview.appspot.com/3816043/ to get reviewed and
committed... there are still a bunch of things missing like linking
with symbols, os.ForkExec and environment variables at early runtime.
time package is also not ready, so I can't ru
I'm typing from my phone so I don't have go sources in front of me,
but 0xdfffefc0 looks like the address I used for per thread G and M
structs - just bellow struct Tos.
Andrey and I also tried running on a 32-bit 9vx with the same effect.
Is 9vx using a different memory layout than Plan 9?
On T
On Tue, Dec 28, 2010 at 9:24 AM, Skip Tavakkolian
wrote:
> sorry for the noise; the -s was mentioned in your original post and i
> missed it. now hell-o example works. i'll try out a few more things.
>
> i checked out a complete release (fresh copy) earlier today before
> applying the patch; it h
println("Hello, 世界")
> }
> cpue% ./8.hell-o
> 8.hell-o 19698: suicide: sys: trap: general protection violation pc=0x7047
>
> -Skip
>
> On Sun, Dec 26, 2010 at 7:54 AM, Pavel Zholkover wrote:
>> Hi all!
>>
>> I've pushed syscall and os p
Hi all!
I've pushed syscall and os package support for Plan 9 on x86 at
http://codereview.appspot.com/3816043/ (pending a review).
I had to make changes to the core go files, so keep your fingers
crossed I didn't break anything along the way and get committed.
If you have access to a real Plan 9
Hi,
I did a Go runtime port for x86, it is in already in the main hg repository.
Right now it is cross-compile from Linux for example (GOOS=plan9 8l -s
when linking. notice the -s, it is required).
There were a few changes made to the upstream so the following patch
is needed until the fix is comm
32 matches
Mail list logo
