World: r3wp

Kaj, thanks for the contribution. I have planned to wrap some of 
the memory manipulation functions too as soon as I finish the work 
on aliasing and type casting.

Hats off to Kaj!
 - from Miejeru on the Red Google Group

Thanks :-)

Red can load library functions with different calling conventions, 
but which convention does the emitter generate for its own functions? 
Cdecl?

Internal functions: stdcall

Wouldn't it be better for compatibility to use cdecl?

I am not sure about the argument order, though...it might be opposite 
of stdcall

I doubt it, because so far I have been able to interchange them. 
The differences must be very small

For porting the cURL binding, I will need callbacks. I'm sure cURL 
on most systems expects them to be cdecl

cdecl for internal functions is only required for callbacks from 
external app, so I planned to add it for internal functions that 
are exported.

OK, when is that plannned?

In a not-too-distant future :-) I don't have precise ETA for that 
as it is not required for Red building. I will add that feature when 
working on the DLL building mode, so probably one of the next weekends 
(maybe on June, 4-5 if there's no other urgent tasks).

Great, thanks

I wanted also to add PIC code generation, so I am not sure which 
one I'll do first. What do you think?

By DLL building mode, do you mean having Red generate shared libraries?

Precisely.

Brilliant

PIC support will be required for that.

I thought about implementing PIC support first and testing it using 
Syllable's executables.

For DLL, you need PIC. I can use callbacks before that, so I'd say 
the order is cdecl, PIC, DLL

That would be nice, too, but it's quite possible that executables 
can already run on Syllable if they can be generated at the right 
start address

Ok, I have no personal priorities for these tasks, so I'll take yours.

Ah, right, that was the last show-stopper.

BTW, I tried installing Syllable on VMWare 7 and it failed to recognize 
the disk controller (I tried every possible disk modes and Syllable 
boot mode). I might have not picked the right image to install...I'm 
retrying right now with this one: http://downloads.syllable.org/Linux/i686/systems/Server/0.1/SyllableServer-0.1.i686.VM.7z

Oh, that's old. We only got a VMware image contributed for Server 
0.1, so it's much better to run the installation for Server 0.4

hm, kaj, could you try setting
base-address:  -2147483648
and see if that generates binaries which work?

But that's Syllable Server, my Linux, so it won't provide any testing 
abilities for Red beyond another Linux

Also, View doesn't run on it. You'd need my unreleased graphical 
version with X11 to run the Red compiler

For testing PIC mode, you'd need Syllable Desktop, for example the 
live CD you got at ReBorCon :-)

Andreas, I'll give it a try

Shouldn't I use one of the VMware v0.6.6 images rather than the install 
CD?

Or should I wait for your graphical version with X11?

You'r mixing up Desktop and Server. 0.6.6 is Desktop, X11 is Server, 
which is Linux

If you want to run Desktop, 0.6.6 indeed has a ready VMware image. 
On the other hand, the live CD you have has some enhancements. Such 
as R3 and the cURL binding :-)

Ah! :-) But can it run R2/View?

Desktop can only run ORCA, Boron and now R3. That's why I've never 
been able to use REBOL in the past decade

Server has R2/Core, Boron and ORCA onboard

Ok, so I need to compile Red/System scripts elsewhere and copy them 
in Syllable.

I'm using View on our inhouse Syllable Workstation, which I could 
give you a download for

copy them => copy the built binaries

Yes, I cross-compile everything on Syllable Workstation

Let me try Desktop first on VMware

Wow, base-address	-2147483648 compiles

Well done Andreas! :-)

now do the binaries run :) ?

I'll have to reboot

If you can upload the binary somewhare I can test it from my running 
Desktop image.

readelf -a looks reasonable

I've compiled the 0MQ binding, and that isn't ported to Desktop yet

what's the dynamic linker called on syllable desktop? would/should 
/lib/ld-linux.so.2 work?