Ishwar Rattan | 2 Sep 2009 18:47

Inferno under 64-bit Linux?


Any one able to compile it? If so, how?
It stopped on the in-line assembly code in fpclt.h.

-ishwar

Charles Forsyth | 4 Sep 2009 00:10

Re: Inferno under 64-bit Linux?

it will only work in 32-bit mode, so use -m32 (which i thought was now the default).
with a few changes it gets surprisingly far in full 64-bit mode, but that's
misleading because there are some fundamental things that are incompatible.
From: Ishwar Rattan <ishwar@...>
Subject: [inferno-list] Inferno under 64-bit Linux?
Date: 2009-09-02 16:47:13 GMT

Any one able to compile it? If so, how?
It stopped on the in-line assembly code in fpclt.h.

-ishwar
Salva Peiró | 8 Sep 2009 10:59
Picon

Re: emu-g ipk's for various ARM NAS'es

On Mon, Mar 30, 2009 at 8:02 PM, Brian Zhou<b88zhou@...> wrote:
> * Right now, only emu-g is built. On these headless NAS devices, X11
> isn't used much. Even X11 is present, I'm not sure that's the way to
> go for GUI. Probably an approach of virtual frame buffer makes more
> sense (GSoC idea?). I'm still a newbie on inferno and plan9, maybe
> there's already an easy way?
>
> Cheers,
>
> -Brian Zhou
> bzhou@...
>

I've got the same problem here and found one possible solution:

I was wanting to cpu to a sheevaplug and then use the draw device
under /n/client/dev/draw coming from a laptop to have a "graphical"
interface to the sheevaplug (see the scripts cpug/rcmdg in [1])

But i've noticed that with the CONF=emu-g used to build the emu-g
binary it's not possible, as when loading a graphical program it fails
as wmlib can't load the graphic's builtin modules: '$Draw', '$Tk', etc

I've adapted emu-g (see patch), so it provides the required
draw modules draw, tk, freetype, so wmlib can work as expected.

Notice that the same trick/ will also work on native,
although it has some quirks which i haven't tracked so it's experimental.

HTH
(Continue reading)

C H Forsyth | 8 Sep 2009 14:30
Favicon

Re: emu-g ipk's for various ARM NAS'es

you probably don't need freetype. leaving it it will save some space.

Axel Belinfante | 9 Sep 2009 15:13
Picon
Picon
Picon

styx-on-a-brick for lego nxt?

just curious if anyone worked on something like that.

seeing that support for remote control over bluetooth
seems already built-in into the NXT  I'm curious
about opinions on how useful a styx-on-a-brick
approach would be there...

I guess that if one would like to have 9p access to
remote control the NXT, one might just as well write
an fs that maps file operations onto the bluetooth commands,
and run that fs on the (remote controlling) host.

Axel.

Adrian Thiele | 15 Sep 2009 07:35
Picon

XShm.h, I found it.

I added these and it built just fine.
 libxext-dev libxpm-dev x11proto-xext-dev

Adrian Thiele | 15 Sep 2009 07:23
Picon

XShm.h?

I'm trying to build inferno on Debian and I seem to be missing this header file,
anybody have an idea which package may contain it?

    cc -c -m32 -DROOT="/home/at/Desktop/inferno" -DEMU -I. -I../port -I/home/at/Desktop/inferno/Linux/386/include -I/home/at/Desktop/inferno/include -I/home/at/Desktop/inferno/libinterp -g -O -I/home/at/Desktop/inferno/Linux/386/include -I/home/at/Desktop/inferno/include -I/usr/X11R6/include -DLINUX_386 -I. ../port/win-x11a.c
../port/win-x11a.c:40:33: error: X11/extensions/XShm.h: No such file or directory

I ran a find for it, and I can't locate it on my system.

Ishwar Rattan | 15 Sep 2009 18:55

heap allocation?


Is there a way to do this in Inferno?

-ishwar

roger peppe | 15 Sep 2009 19:24
Picon
Gravatar

Re: heap allocation?

almost all allocation is heap allocation in inferno.
e.g.

x := array[1024] of byte;

allocates x on the heap.

but perhaps that's not what you mean?

2009/9/15 Ishwar Rattan <ishwar@...>:
>
> Is there a way to do this in Inferno?
>
> -ishwar
>
>

Ishwar Rattan | 15 Sep 2009 22:17

Re: heap allocation?

I am computing Fibonacci numbers the hard way :-)
After 1000000th number, I get out of memory
message. Maybe I have hit the max resource allocation
limit..

-ishwar

On Tue, 15 Sep 2009, roger peppe wrote:

> almost all allocation is heap allocation in inferno.
> e.g.
>
> x := array[1024] of byte;
>
> allocates x on the heap.
>
> but perhaps that's not what you mean?
>
>
> 2009/9/15 Ishwar Rattan <ishwar@...>:
>>
>> Is there a way to do this in Inferno?
>>
>> -ishwar
>>
>>
>


Gmane