Re: FW: Problems building newlib under Cygwin

[Carl Miller <chaz at energoncube dot net>]

> I am using a modified script I found (and plagiarized shamelessly) that
> first compiles binutils (this works) and then compiles gcc-core (this works,
> too), then newlib is compiled and appears to finish and puke on installing
> in the following manner:

I don't see any error message at the end of the make.

[..chop..]
> make[1]: Leaving directory
> `/home/bruceb/Work/build-newlib/powerpc-eabi/newlib'
> if [ -f /usr/src/newlib-1.10.0/texinfo/gen-info-dir ] ; then \
>   /usr/src/newlib-1.10.0/texinfo/gen-info-dir
> /home/bruceb/Work/Cross-Powerpc-eabi/info
> /usr/src/newlib-1.10.0/texinfo/dir.info-template > dir.info.new ; \
>   mv -f dir.info.new dir.info ; \
> else true ; \
> fi
> s=`cd /usr/src/newlib-1.10.0; pwd`; export s; \
> if [ -f dir.info ] ; then \
>   /bin/sh $s/install-sh -c -m 644 dir.info
> /home/bruceb/Work/Cross-Powerpc-eabi/info/dir.info ; \
> else true ; fi
> Building libc failed

It would appear to me that there's a mismatch in the filename or directory
under which the make install installed the target libc, and where the build
script is looking for it in this check:

> # Configure, build and install newlib
> cd /home/bruceb/Work/build-newlib
> /usr/src/newlib-1.10.0/configure --target=$target --prefix=$prefix -v \
> 2>&1 | tee configure.log 
> make all install info install-info 2>&1 | tee make.log
>
> # test to see if this step passed
> if [ ! -f ${PREFIX}/${TARGET}/lib/libc.a ]; then
>     echo Building libc failed && exit 1
> fi

See where the newlib makefile installs to.  Maybe the libc is somewhere else,
or called something else, and that's just a bogus test that you see failing.

If that doesn't turn up anything, try sifting through that last make.log
looking for error messages that for some reason didn't cause make to exit.
If you find something suspicious, track down from there (or post it to the
list if you still need help).


                         ------Carl

(Ah, a local!  I work in Carlsbad, too!)

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com