Bruce Dubbs wrote:
> Try this as the lfs user:
> 
> tar -xf glibc-2.16.0.tar.xz
> cd glibc-2.16.0
> 
> sed -i 's/ -lgcc_s//' Makeconfig
> sed -i 's|<rpc/types.h>|"rpc/types.h"|' sunrpc/rpc_clntout.c
> 
> mkdir -v ../glibc-build
> cd ../glibc-build
> 
> echo BUILD_CC=${LFS_TGT}-gcc > configparms

Uh, isn't that backwards?  :-)

BUILD_CC is the CC to use to build programs that will be executed on the
cross-compilation *source* architecture, not the destination. ${LFS_TGT}
is the destination arch.  The glibc sources are trying to build this
program for the source.

This actually also means that host includes (and libs) are *absolutely*
required to be here.  This output doesn't get linked into the cross
glibc, so this is *not* actually a contamination from the host system.
(Only the output of rpcgen, after it gets built and run, is used.)

This does mean, however, that the host does really need the rpc/types.h
header file installed, so on systems that don't have it, glibc won't
build...


Attachment: signature.asc
Description: OpenPGP digital signature

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to