|
From: <sv...@va...> - 2005-05-17 16:13:19
|
Author: tom
Date: 2005-05-17 17:13:15 +0100 (Tue, 17 May 2005)
New Revision: 3761
Modified:
trunk/configure.in
Log:
Pass an explicit "-m32" or "-m64" in the C flags on x86/amd64 systems
so that we get the right compiler when --host is used to ask for an x86
build on amd64 or vice versa.
Modified: trunk/configure.in
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/configure.in 2005-05-17 16:11:40 UTC (rev 3760)
+++ trunk/configure.in 2005-05-17 16:13:15 UTC (rev 3761)
@@ -96,9 +96,9 @@
AC_MSG_RESULT([ok (${host_cpu})])
VG_ARCH=3D"x86"
KICKSTART_BASE=3D"0xb0000000"
- ARCH_CORE_AM_CFLAGS=3D"@PREFERRED_STACK_BOUNDARY@ -DELFSZ=3D32"
- ARCH_TOOL_AM_CFLAGS=3D"@PREFERRED_STACK_BOUNDARY@"
- ARCH_CORE_AM_CCASFLAGS=3D""
+ ARCH_CORE_AM_CFLAGS=3D"-m32 @PREFERRED_STACK_BOUNDARY@ -DELFSZ=3D=
32"
+ ARCH_TOOL_AM_CFLAGS=3D"-m32 @PREFERRED_STACK_BOUNDARY@"
+ ARCH_CORE_AM_CCASFLAGS=3D"-m32"
;;
=20
x86_64)=20
@@ -108,15 +108,15 @@
# quantities; therefore going above 0x7fffffff doesn't work... t=
his is
# a problem.
KICKSTART_BASE=3D"0x70000000"
- ARCH_CORE_AM_CFLAGS=3D"-fomit-frame-pointer @PREFERRED_STACK_BOU=
NDARY@ -DELFSZ=3D64"=20
+ ARCH_CORE_AM_CFLAGS=3D"-m64 -fomit-frame-pointer @PREFERRED_STAC=
K_BOUNDARY@ -DELFSZ=3D64"=20
# XXX: need to use -fpic, otherwise when linking tools I get thi=
s error
# message:
# relocation R_X86_64_32 can not be used when making a shared =
object;
# recompile with -fPIC
#
# I don't understand... --njn
- ARCH_TOOL_AM_CFLAGS=3D"-fomit-frame-pointer @PREFERRED_STACK_BOU=
NDARY@ -fpic"
- ARCH_CORE_AM_CCASFLAGS=3D""
+ ARCH_TOOL_AM_CFLAGS=3D"-m64 -fomit-frame-pointer @PREFERRED_STAC=
K_BOUNDARY@ -fpic"
+ ARCH_CORE_AM_CCASFLAGS=3D"-m64"
;;
=20
arm*)=20
|