Re: [patches] Cross-building instructions

[Khem Raj <kraj@xxxxxxxxxx>]

Jim Blandy said the following on 2/21/2007 4:58 PM:
> Khem Raj <kraj@xxxxxxxxxx> writes:
>   
> > I ran through the steps. But I get an error when building
> > eglibc-headers
> >     
>
> Hmm.
>
> First, Joseph had some comments that lead me to substantially revise
> the instructions from the ones you quoted in the message I'm replying
> to.  Also, I committed some fixes yesterday.  So, are you using the
> latest EGLIBC sources, and the EGLIBC.cross-building file in there?
>   
yes I am uptodate with SVN.
> Second, what were your configure and make install-headers commands,
> exactly?
>   

> When I do the 'make install-headers ...', I see
> $obj/eglibc-headers/gnu/lib-names.h being created:
>
> ...
> gawk -f scripts/lib-names.awk /home/jimb/cross-build/ppc/obj/eglibc-headers/soversions.i > /home/jimb/cross-build/ppc/obj/eglibc-headers/gnu/lib-names.T
> /bin/sh scripts/move-if-change /home/jimb/cross-build/ppc/obj/eglibc-headers/gnu/lib-names.T /home/jimb/cross-build/ppc/obj/eglibc-headers/gnu/lib-names.h
> touch /home/jimb/cross-build/ppc/obj/eglibc-headers/gnu/lib-names.stmp
> ...
>
> Does this step not occur for you?
>   
Hmmm no I didn't see gawk being called. But I saw the following.

autoconf: Undefined macros:
***BUG in Autoconf--please report*** AC_FD_MSG

The autoconf on my host is configured to use 2.13 by default

Its too old for glibc. I updated to 2.60 now it works as expected. So 
now I am past that point.
>   
> > Secondly, I think we should also add some words about ports its not
> > mentioned that it should be inside 'libc' directory
> > because on SVN tree its parallel to libc.
> >     
>
> The instructions are supposed to be independent of how or whether you
> add ports to your tree.  Is there something in the directions that
> assumes that ports is in the tree?
>   
For e.g. doing an arm build you need ports add-on. So the instructions 
does not specify anything about ports directory where to put it etc. for 
ppc ports is not needed so even if ports in not there is will work.
but may be we could add some words on how to configure ports along with 
libc. I saw that the configure already has --enable-add-ons so creating 
a symlink inside libc directory to ports would be sufficient


--
Khem Raj <kraj@xxxxxxxxxx>
MontaVista Software Inc.