On Fri, Aug 15, 2014 at 02:35:24AM +0200, Aurelien Jarno wrote: > I have not been able to reproduce the issue, neither with 0.4.1-6 nor > with version 0.4.1+git-20140423.c559da7c-1 I have just uploaded. Are you > sure it is not related to your cross-compiler?
I think it is related to Ubuntu's build environment. But I believe it is
a bug to build without the -ffreestanding flag in this case, will cause
no harm to do so, and not doing so does cause cross-compiling issues.
Otherwise you're making the implicit assumption that the build system is
the target system, when the nature of the package means that there is no
need to do so.
The definition from my manpage:
-ffreestanding
Assert that compilation targets a freestanding environment.
This implies -fno-builtin. A freestanding environment is one
in which the standard library may not exist, and program
startup may not necessarily be at "main". The most obvious
example is an OS kernel. This is equivalent to -fno-hosted.
It seems to me that the correct thing to do is to use this flag in this
case, even if it happens to not cause a build failure in your particular
build environment.
Note: I have not checked applicability for your latest upload
(0.4.1+git-20140423.c559da7c-1). I assume for now that the code in this
area hasn't changed.
signature.asc
Description: Digital signature
