World: r4wp

I think someone else also had this problem, but I'm getting this 
when building this source on Linux:

undefined reference to `dtoa'

I guess that you did not do make make and make prep?

(that is necessary to include the new source code file)

No, it's not needed for Carl's source

it is needed for this

Thanks, I'll try

Hmm, we need to update the default makefile as well. Thanks for reporting, 
Kaj.

(I solved the conflict with Andreas' change by just taking his makefile)

I'll hold on then

No need to hold, make make will also resolve this.

Kaj, you should not hold, just do what I suggested

Yeah, but I don't want to complicate my build script further. I already 
have to track many branches of REBOL

make make and make prep are already strongly suggested anyway

I try to keep my build procedures as minumal as possible

then I have to wash my hands...

Pardon?

a part of the Easter story...

(no need to understand)

I understand, but I was hoping to update R3 with the minimum fuzz

Pushed an updated makefile.

If Andreas updates the makefile in one of the next commits, my build 
recipe just downloads that. Ah, thanks

However, the reliable way to do a full & clean build is `make make` 
followed by `make clean prep r3`.

All fine now. I've switched the Syllable build system to the community 
source:

http://syllable.cvs.sourceforge.net/viewvc/syllable/syllable/system/apps/utils/Builder/packages/REBOL-Core--current/

Cool.

Kaj, what is the system/version of your build?

2.101.0.4.4 just like Carl's

Hmm, why don't you "force us" to define a new (Syllable) platform?

I'm running on Syllable Server now, so the Linux version is correct

Is your build identical with the 0.4.4?

And because it's not needed. The Linux-configured source - and even 
the binary Linux library - work fine on Syllable Desktop

Do you mean a Syllable Desktop build?

Whichever you are using.

, i.e. if you really get identical builds when getting identical 
system/version

What I'm doing now is just a Linux build. A build on Syllable Desktop 
yields a different host executable: that is not compatible. The library 
would also be internatlly different when compiled on Syllable Desktop, 
but Desktop can still load a library compiled on Linux

I am especially curious whether any of your 0.4.4 is really what 
I get when building r3 on Linux?

(which is what is intended to be the true 0.4.4)

Builds are not byte for byte compatible across Linux platforms, because 
they depend on compilers, headers and startup fragments from the 
compiler and possibly the assembler

I supposed that was why there were other platforms for Linux than 
just 0.4.4?

Those are for different versions of the GNU GLibC C library. In practice, 
it's impossible to compile binaries with the GNU toolchain that are 
compatible across all C libraries

Do you really want Syllable to be ignored as a platform?

I suppose it may have some unwanted side effects.

AFAIU, 0.4.x for Syllable Server sounds appropriate (it seems to 
be "just" a Linux distribution).

I've tested it quite well. We've been running R3 Linux binaries for 
years on Syllable Desktop. Having the source it's properly built 
on Syllable, but it hasn't fixed any problems

It's fine if the Syllable Desktop configuration becomes explicit, 
but I currently don't have a reason to spend time on it

Yes, but there already are some Rebol scripts examining system/version 
to "know how to call system libraries" or some such. I guess it may 
be a good reason to define a platform?

Yes, that would be a good reason. In my patches to port Python, for 
example, I solve it by looking if the /system/index/ directory exists, 
which would identify not only Syllable Desktop, but also Syllable 
Server

As long as programs use the Linux configuration as default in a decision, 
it almost always also works on Syllable Desktop

well, then it may be just a matter of preference (if you want to 
make Syllable "visible" at least for Rebol)