World: r4wp

Yes, they are.

cool

Full set of our changes, except for the dropping of NM.

great, so yes, go for the official repo ;)

Rebol System error 1405...

Ah, that sounds like the Win7 crash.

WinXp

During make make already, I guess?

Try running make make directly:
./r3-make ../src/tools/make-make.r 0.3.1

That should give you the Win32 makefile, with a workaround for the 
crash in place.

to launch an exe, it must and wth .exe in WinXp (from console)

Ok, launched the make make

Error:

./r3-make -qs >NUL: ../src/tools/make-headers.r
.
 non è riconosciuto come comando interno o esterno,
 un programma eseguibile o un file batch.
mingw32-make: *** [prep] Error 1

make make OS... is ok
make prep gives that error

Is like that says: 
.
 is not a command

problem is in CD=./

it doesn't work on windows

it should probably: "CD=cd"
it returns the current path on Windows.

CD = %CD%  
works

so I arrive at the next bug...

C:\DOCUME~1\max\DOCUME~1\GitHub\r3\maker3-make
 is not recognized

is the path correct? maker3-make is an executable? if so it should 
be maker3-make.exe.

It doesn't exist any maker3-make

anywhere

If you can build successfully R3 in Widnows with MinGW, please post 
the procedure on GitHub wiki

Probably it is a missed file on your fork. I didn't build R3 on Windows 
yet. Cyphre can send that file I think.

You can send me the binary directly... :-)

I don't have that binary. I think it's used by Cyphre and it's missed 
on the svn.

I posted an old binary several days ago. Let me build a fresh one.

MaxV, are you running the above from a MinGW shell?

Or just from a plain cmd.exe?

plain cmd.exe

Not sure if that ought to work.

All paths in the makefile use / as path separators.

So better try running from a MinGW shell.

OK, I understood.

(Otherwise, if you absolutely don't want to use a MinGW shell, try 
using CD=.\ or CD=%CD%\ -- the trailing backslash is important.)

I didn't know the MinGW shell, I used it and it worls!
>> system/version
== 2.101.0.3.1

(works)

We could use a separate group to talk about building and porting 
R3. This group is getting a bit polluted.

I have a couple significant changes to make to TRANSCODE. Can all 
interested parties please review http://issue.cc/r3/1915and http://issue.cc/r3/1916
and comment what you think? AFIAK I have used TRANSCODE more than 
anyone else, but we're at the point where more opinions are needed. 
It's low-level, so most people won't be affected by this. They're 
not syntax changes, they're changes in its external behavior.

Brian -- !REBOL3 Building and Porting group created

Where is the GitHub Wiki?

It disappeared!

The http://www.rebol.com/r3/docs/index.htmlwiki is not good, you 
can't register or edit.... :-(

MaxV: I think you can edit. I would definitely not replace it with 
the Github one, at least not for docs, which are quite extensive. 
IIRC, you had to be registered on R3 Chat, and then when you got 
some level of access, you could edit docs. There is more to the R3 
Chat, than might be seen from the mostly ugly surface ...

Sorry, but I don't think so. 

A good wiki is a wiki where is easy to register and edit. The one 
on the Rebol.com is not a good wiki.

People will register and use GitHub, so a wiki must be on GitHub. 

If youlike, you may have an "offical" wiki in Rebol, but a living 
wiki is the GitHub.

I can copy all rebol wiki on GitHub, you you want; but please reactivate 
the GitHub wiki!

Don't do the same errors of Rebol 2, where there was a wall between 
people and reboltech.

MaxV: I will gladly let it to Carl to sort out. He was reshaping 
a wiki for nearly 3 months, and there are something like 75K pages 
of content. It is also kind of autogenerated/automated. So - do you 
want to do many things manually?

I'll do it in 24 hours, you have my word!

As Carl said, it's not tto difficult, if you know how to do it.