Lack of 64bit support breaks -run

[Russ Lewis]

I took a closer look at the RPM.  Apparently, gcc32 is a GCC 3.2 
compiler, *NOT* a gcc 32 bit compiler.  At least, that is true on Fedora 
Core 5.

So, it's back to square one.

John Demme wrote:
> compile it without -run (and with CC=gcc32), and compare the gcc comands
> between the two runs.
> 
> ~John Demme
> 
> Russ Lewis wrote:
> 
> 
>>I found that I could get gcc32 by installing the package "compat-gcc-32"
>>(on Fedora Core 5), but it still didn't work for me:
>>
>>[russ at russ project]$ CC=gcc32 dmd -run ~/bin/global_uniq.d < parser.h
>>/usr/bin/ld: skipping incompatible
>>/usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/../../../libphobos.a when
>>searching for -lphobos
>>/usr/bin/ld: skipping incompatible /usr/lib/libphobos.a when searching
>>for -lphobos
>>/usr/bin/ld: cannot find -lphobos
>>collect2: ld returned 1 exit status
>>--- errorlevel 1
>>[russ at russ project]$
>>
>>
>>John Demme wrote:
>>
>>>Looks like that doesn't work b/c DMD takes the CC env variable and runs
>>>it
>>>as a command, so you have to use gcc32 as Thomas suggested.  Does gcc32
>>>exist on all systems?
>>>
>>>~John Demme
>>>
>>>Russ Lewis wrote:
>>>
>>>
>>>
>>>>Doesn't seem to work.  I get this:
>>>>
>>>>CC="gcc -m32" dmd -run ~/bin/global_uniq.d < parser.h
>>>>gcc -m32: No such file or directory
>>>>--- errorlevel 255
>>>>[russ at russ project]$
>>>>
>>>>Thomas Kuehne wrote:
>>>>
>>>>
>>>>>-----BEGIN PGP SIGNED MESSAGE-----
>>>>>Hash: SHA1
>>>>>
>>>>>Russ Lewis schrieb am 2006-05-22:
>>>>>
>>>>>
>>>>>
>>>>>>Since dmd can't link properly on AMD64 linux, I can't use -run.
>>>>>>
>>>>>>It has occurred to me that one (simple) solution to this would be to
>>>>>>add an argument to dmd which it would pass to gcc, so that I could pass
>>>>>>-m32.  I tried using -L, but that passes the argument
>>>>>>-Xlinker -m32
>>>>>>to gcc rather than what I'm attempting to pass, which is simply
>>>>>>-m32
>>>>>
>>>>>
>>>>>work around:
>>>>>
>>>>>CC="gcc -m32" dmd -run source.d
>>>>>
>>>>>Thomas
>>>>>
>>>>>
>>>>>-----BEGIN PGP SIGNATURE-----
>>>>>
>>>>>iD8DBQFEciwD3w+/yD4P9tIRAiBzAKCjsiYfysCdSB5nIJ6U4v4k/E0q2gCfTCeM
>>>>>EyxfeV58iN9vRoKdKPlAp1Y=
>>>>>=m3PI
>>>>>-----END PGP SIGNATURE-----
>>>
>>>
>