On Fri, 2005-10-14 at 17:59 +0200, Peter Alberer wrote: > > Where do I find how my gcc was configured? > You can get the compile options for gcc with "gcc -v". Ah. okay, here is what I have: =========================================================================== [williams@sns-hp-eval1 3.2.3]$ gcc -v Reading specs from /usr/lib/gcc-lib/x86_64-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man -- infodir=/usr/share/info --enable-shared --enable-threads=posix -- disable-checking --with-system-zlib --enable-__cxa_atexit --host=x86_64- redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-47) ============================================================================ There are some compiler flags that I need to know about as well. For example is some the makefiles that I use for 32-bit builds on a plain old x86 machine, I have things like: * ARCH_DEP_CPPFLAGS += -D_X86 Then I guess I will have to throw the -m64 flag for both C++ and C builds? > > > > My main questions: > > > - Why is the file "/lib/tls/libc.so.6" used here and not the same file > > in > > > /lib64? > > > - Where does gcc find the info which version of the libs (32/64-bit) to > > use? > > > - do others have experience with systems running redhat as4 where gcc > > seems > > > to behave funny? > > > > Same question for me. > > As far as the "/lib/tls/libc.so.6" question is concerned, this seems to be > because I compiled my own gcc with 32bit. But the others question are still > interesting for me. > > As far as my original problem is concerned: > In the meantime i managed to get postgresql running on my machine. The > problem was in some calls to socket-functions where a parameter that should > have the type "socket_len" was defined as "size_t". which seems to work on > 32 bit and for some people in 64 bit, but not for me... > > By, peter > >
