On Fri, Feb 05, 2010 at 09:06:56PM +0000, Dave Korn wrote:
> On 05/02/2010 18:46, jacob navia wrote:
>
> > The build crashed in the java section by the way, there was a script that
> > supposed the object files in a .libs directory but the objects were in the
> > same directory as the source code. This happened several times, so at the
> > end I stopped since I am not interested in Java.
>
> Then this is just FYI: there should have been matching sets of .o files in
> both the main directory and the .libs subdirectory; the ones in the .libs
> subdir are/should be compiled as position-independent code. That's how it
> usually works anyway; Darwin may do things differently.
>
> You also shouldn't build in the source directory, it's not guaranteed to
> work and occasionally fails in peculiar ways.
>
> cheers,
> DaveK
Dave,
I suspect one major problem is that he is building FSF gcc 4.2.1 on
darwin10. The first FSF gcc validated on darwin10 was 4.4. Also, it wasn't
until gcc 4.5 that -no_compact_unwind was passed to the linker on darwin10.
Thus, gcc 4.4.x will be using the new compact unwinder on darwin10 which
is the origin of some of the x86_64-apple-darwin10 java testsuite failures
(now absent in FSF gcc trunk).
Jack
