|
Boost : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-12-18 06:25:07
Oliver.Kowalke_at_[hidden] wrote:
>
> From: Martin Bonner
>
>> From: Oliver.Kowalke_at_[hidden]
>> > With autoconfig the build process can check if strerror_r
>> is avaliable
>> > and provide strerror as fall back.
>>
>> Autoconfig can check if strerror_r is available ON THE BUILD MACHINE.
>> It CANNOT tell whether it will be available on the target machines.
>
> It is you fault if you distribute a software to an platform for which it
> wasn't build.
> If build and target machine have the same os version and release then
> the system calls should be the same.
And why do you think that build and target machine should have the same os
version and release? It's quite reasonable to build things on operating
system X version N and have it run on operating system Y version M.
Compiler running on Linux and producing binaries for Windows is a common
beast.
It's quite possible to have compiler run on Solaris N and target Solaris
N-1.
However, that requires *specially configured* compiler. Among other things
will be need access to the header files and libraries of the target OS.
- Volodya
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk