Author ngie
Recipients goertzen, hugo_koopmans, jdalambert, jepler, mattcomms, ngie, nico0438, nico38, robsa, solarx, vapier, xudong888
Date 2009-02-24.22:05:46
SpamBayes Score 1.52471e-06
Marked as misclassified No
Message-id <1235513153.7.0.121035171346.issue1006238@psf.upfronthosting.co.za>
In-reply-to
Content
I can definitely chime in on this issue.

A (proper) testcase would be to do something like the following:

# Example item -- this isn't what you'll be using...
CROSS_COMPILE_PREFIX=binos_c3.4.3-p1.mips64-octeon-linux-

AS="${CROSS_COMPILE}as" \
CC="${CROSS_COMPILE}gcc" \
CC="${CROSS_COMPILE}c++" \
LD="${CROSS_COMPILE}ld" \
NM="${CROSS_COMPILE}nm" \
./configure --prefix=/usr/local \
BUILD_PYTHON=/path/to/native/python \
DESTDIR=/where/i/want/to/install/python \
--build=`"${CROSS_COMPILE}gcc" -dumpmachine` \
--host=`arch`

NOTES:
- arch(1) is a GNU specific utility, so it won't work outside of Linux!
- I'll leave it as an exercise to the reader to specify the correct
CFLAGS, CPPFLAGS, LDFLAGS, and LDLIBS.

Some testcases during the compile that fail if cross-compiling are (with
2.6.1):
- chflags
- lchflags
- printf with %zd format support.

Thanks!
History
Date User Action Args
2009-02-24 22:05:53ngiesetrecipients: + ngie, jepler, goertzen, jdalambert, vapier, solarx, robsa, xudong888, nico38, nico0438, hugo_koopmans, mattcomms
2009-02-24 22:05:53ngiesetmessageid: <1235513153.7.0.121035171346.issue1006238@psf.upfronthosting.co.za>
2009-02-24 22:05:47ngielinkissue1006238 messages
2009-02-24 22:05:46ngiecreate