Re: i386 to x86_64 Issues

[Dan Kegel <dank at kegel dot com>]

Piete Sartain wrote:
> ...
>  www.kaear.co.uk/personal/kaear/crosscompile.info

If that's a plain text file, can you give it a suffix of .txt
so browsers can deal with it?

> Binutils and GCC still need to be recompiled and packaged for me to be 
> on the way to a useful 64-bit platform, and needless to say neither of 
> the buggers will; both claiming crt1.o doesn't exist when quite 
> obviously it does.
>
> gcc --print-search-dirs doesn't include lib64, which is where *crt* 
> lives.  This indicates to me that the toolchain itself is not set up for 
> a native compile (some reference to *crt* in lib would be nice, I 
> suppose), or for whatever reason gcc & glibc don't agree on how a 
> "native" compile should work.

What version of gcc?  3.3.x had this problem with lib64; 3.4.x don't.

If you have to use 3.3.x, maybe this will help:
Cort Dougan sent in a kludge to help this; add the following
section near line 440 of crosstool.sh (I'm testing this in
the next release of crosstool now):

 test "$CANADIAN_BUILD" = "" || make $PARALLELMFLAGS all-build-libiberty || true
+#
+# This is necessary for GCC 3.3.3 on PowerPC64 and x86_64.  Possibly others
+# as well.  GCC 3.4.X works without this, though.
+# -- Cort <cort.dougan at gmail.com>
+#
+if [ ${GCC_DIR} = gcc-3.3.3 ] ; then
+    case ${TARGET} in
+	powerpc64-unknown-linux-gnu|x86_64-unknown-linux-gnu)
+	    for x in `find ${SYSROOT} -name lib -type d -empty`; do
+		echo $x
+		if [ -d `dirname $x`/lib64 ] ; then
+		    rm -rf $x
+		    ln -s `dirname $x`/lib64 $x
+		fi
+	    done
+	    ;;
+	*)
+	    ;;
+    esac
+fi
+
 make $PARALLELMFLAGS all
 make install


--
Trying to get a job as a c++ developer?  See http://kegel.com/academy/getting-hired.html

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