On Tue, 9 May 2006, Ed Hill wrote:
What you've done above is a start but you left out a critical step.
What you really need to use is a program name prefix and/or suffix
***PLUS*** a different --prefix=${SOME_PATH} so that ${SOME_PATH} does
not equal /usr.
I understand this, but I didn't know how to solve it.
For testing purposes, I typically use something like:
./gcc-4.1.0/configure --prefix=/opt/gcc-4.1.0 \
--enable-languages=c,c++,f95 --program-suffix=-4.1.0
and you will want a similar syntax for binutils, etc...
assuming I'm producing the native compiler from the cross
compiler here and the native compiler (and its libraries)
winds up in /opt/gcc-x.x.x on the linux machine, then when I
tar| untar the native compiler onto the target machine in
/usr, will the native compiler be looking for its own files
(and libraries) in /opt/gcc-x.x.x or in /usr?
Thanks Joe
--
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!
--
TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
