The Apache Harmony PPMC is proud to announce David Tanzer as our
newest Apache Harmony committer, and look forward to seeing him
continue his work on component interfaces (starting with his
contribution in sandbox/tanzer_component), as well as other areas of
his interest.
His work shows
This contribution was accepted by the Apache Harmony community with
unanimous support, and all documentation is complete. This
contribution and it's contribution information has been placed in the
contrib archive (where it shall remain untouched) :
https://svn.apache.org/repos/asf/incuba
> "Enrico" == Enrico Migliore <[EMAIL PROTECTED]> writes:
Enrico> Since we got GNU libc code, my suggestion is, for each
Enrico> architecture, compile _ALL_ the C code with the same set of C
Enrico> flags, including the libc.
Enrico> In this way, the libc and the VM will be a monolithic
Enric
Why would people want to recompile libc?
geir
On Oct 7, 2005, at 12:16 PM, Dan Lydick wrote:
It seems that not all versions of 'libc' are compiled
with the same flags. Furthermore, the edition that I
am using (GCC 3.3.3 on Solaris 9) apparently does not
use all the same flags all the way a
Why would people want to recompile libc?
geir
On Oct 7, 2005, at 12:16 PM, Dan Lydick wrote:
It seems that not all versions of 'libc' are compiled
with the same flags. Furthermore, the edition that I
am using (GCC 3.3.3 on Solaris 9) apparently does not
use all the same flags all the way aro
It seems that not all versions of 'libc' are compiled
with the same flags. Furthermore, the edition that I
am using (GCC 3.3.3 on Solaris 9) apparently does not
use all the same flags all the way around. I am
suspicious of this because I was able to compile
everything but code that used fprintf(
I'm working with Dan's bootVM to get to run on Windows, and have been
thinking about the use of -fpack-struct vs #pragm pack() vs just not
packing and writing code that is a little slower, and a little more
verbose, but seemingly more robust and maintainable due to less
information about
