World: r3wp

Cool :-)

size? struct! doesn't work yet:

#include %../ZeroMQ-binding.reds
print-integer size? message!
print-newline

*** Compilation Error: undefined symbol: message! 

*** in file: %/users/administrator/Red/Red-ZeroMQ-binding/examples/reply-server.reds 
*** at:  [message! 
    print-newline

message! is aliased in ZeroMQ-binding.reds, but it doesn't seem to 
carry over to the source file where it's included

The 0MQ binding should now be thread safe and release its allocated 
memory

Andreas: great!

Kaj: the compilation message there is wrong, the compiler wasn't 
expecting an alias name (but it should). I will fix that today.

Andreas: heelo-fbsd.bin works flawlessly on FreeBSD8.2!

Andreas: adding support for shared library is in my todo list for 
the next weeks.

Got my virtual struct! lib working ok. It is not perfect but should 
cover our needs for Red bootstrapping. Finally, we'll be able to 
get rid of /View.

Great!

Will merge it to main branch in a few minutes.

300 commits reached! And now the compiler runs on /Core!

Excellent

(Must write a cheer bot one of these days)

hehe :-)

Silly question (I'm not in the loop), why was View necessary? Feel 
free to point to a blog post or something that explains it.

because we used struct! quite heavily

which (still) is not available in /core

ok, interesting.

the binary emitters (PE, ELF) need to adhere to the respective format 
specification, which is usually supplanted with C struct definitions. 
the primary issue is that C structs have particular (platform-specific) 
memory layout rules, which REBOL's struct! mimicks.

for example a struct of an 8-bit char! and a 32-bit integer! takes 
up not 40-bits but actually 64-bits in size (due to alignment constraints, 
in this case).

so this is one of the challenges that are required to solve, when 
creating a new binary emitter?

when writing a new emitter, the "challenge" is mostly the rather 
tedious task os transliterating C structs into REBOL struct!s

Have a look at the current ELF/PE emitters, for example:

https://github.com/dockimbel/Red/blob/master/red-system/formats/ELF.r#L87

https://github.com/dockimbel/Red/blob/master/red-system/formats/PE.r#L145

For comparison, that's the spec of the ELF "Ehdr" struct:
http://sco.com/developers/gabi/latest/ch4.eheader.html

REBOL/Core 2.7.8 doesn't run on FreeBSD8.2, it requires libm.so.4 
(FreeBSD 4)...

# ln /lib/libm.so.5 /lib/libm.so.4
# rebol

/libexec/ld-elf.so.1: Shared object "libc.so.6" not found, required 
by "rebol"

Getting /Core to run on FreeBSD looks like a real challenge :-)

Aren't there "compat" libraries for FreeBSD 4 etc. backwards compatibility?

Yes, but it requires me to install a lot of stuff...The real issue 
is that /Core is built on obsolete libraries version.

I know, but all operating systems should deal with backwards compatibility, 
and the Unixes usually do it with optional packages that you need 
to install

hmm, /core 2.7.8 runs fine for me on freebsd 8.2

let's see where those ancient libm/libc versions come from :)

compat6x-amd64-6.4.604000.200810_3 :)

So the compatibilty base seems to be FreeBSD 6

I tried: pkg_add -r compat6x-amd64 from http://www.freshports.org/misc/compat6x, 
but keep getting "unable to fetch messages".

Did I miss something?

are you on an amd64 system?

Are you on AMD64?

:-)

on Vmware

I guess it emulates an Intel CPU

uname -m ?

i386

works

should be just `pkg_add -r compat6x` then

thanks!

(or -i386 :)