That all looks ok. I don't see anything weird there.
Michael Abshoff suggested perhaps the compiler on this machine
requires, or objects to -m64.
What happens if you compile and run the following program (test.c say):
#include <stdio.h>
int main(void)
{
printf("hello\n");
return 0;
}
Try compiling it with:
gcc -m64 test.c -o test
and with
gcc test.c -o test
Do both work?
./test
Bill.
2009/4/16 Jeff Gilchrist <[email protected]>:
>
> On Thu, Apr 16, 2009 at 8:18 AM, Bill Hart <[email protected]>
> wrote:
>
>> What is the result of
>> gcc -v
>
> Using built-in specs.
> Target: x86_64-redhat-linux
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --enable-checking=release --with-system-zlib --enable-__cxa_atexit
> --disable-libunwind-exceptions --enable-libgcj-multifile
> --enable-languages=c,c++,objc,obj-c++,java,fortran,ada
> --enable-java-awt=gtk --disable-dssi --enable-plugin
> --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
> --with-cpu=generic --host=x86_64-redhat-linux
> Thread model: posix
> gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)
>
> Jeff.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
