search

veekays / iphonedevonlinux

Automatically exported from code.google.com/p/iphonedevonlinux
0 stars 0 forks source link

Detecting gcc 32bits awareness on 64bits platforms #10

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Currently, cctool-iphone only build on 32bits platforms.
It would be nice if toolchain.sh could detect 32bits support in GCC or die
otherwise.

What steps will reproduce the problem?
1. install gcc on a 64bits architecture (e.g. Ubuntu amd64)
2. make sure no support for 32bits is available
3. ./toolchain.sh build

What is the expected output? What do you see instead?
The user expects the toolchain to build. Instead, he can read:

checking for C compiler default output file name... 
configure: error: C compiler cannot create executables
See `config.log' for more details.
make: *** No rule to make target `clean'.  Stop.
Building cctools-iphone...
Build progress logged to: toolchain/bld/cctools-iphone/make.log
Build & install failed. Check make.log and install.log

What version of the product are you using? On what operating system?
toolchain.sh r73, Ubuntu Intrepid Ibex x86_64

Please provide any additional information below.
The following patch aims at detecting 32bits support in GCC when
toolchain.sh is ran on 64bits platforms.

Original issue reported on code.google.com by damien.c...@gmail.com on 16 Feb 2009 at 9:27

Attachments:

GoogleCodeExporter commented 8 years ago 
Thanks for the patch damien. Unfortunately (or perhaps fortunately in my case) 
I've
had a busy period with some paid work so I haven't been able to focus on the
toolchain builder as much. I'll this and your other patch introduced tonight 
hopefully.

Original comment by m4d...@gmail.com on 21 Feb 2009 at 9:25

GoogleCodeExporter commented 8 years ago 
what do i do with the patch?

Original comment by ackdrumm...@aol.com on 17 Aug 2009 at 7:42

GoogleCodeExporter commented 8 years ago 
You simply have to use the binary "patch" to merge this patch to the regular 
toolchain.sh

First, give it a try:
patch --dry-run toolchain.sh < /home/dciabrin/Desktop/toolchain-m32check.patch

if the patch applies succesfully, you can proceed for real:
patch toolchain.sh < /home/dciabrin/Desktop/toolchain-m32check.patch

But please note that it won't fix compilation issue, it only tells you earlier
whether your gcc is able to compile the toolchain or not (i.e. if it support 
32bit
compilation)

Original comment by damien.c...@gmail.com on 17 Aug 2009 at 7:38