Re: fixing Makefile.shlib for solaris/gcc with -m64 flag - Mailing list pgsql-hackers

From Jignesh K. Shah
Subject Re: fixing Makefile.shlib for solaris/gcc with -m64 flag
Date
Msg-id 45AE60E6.2090307@sun.com
Whole thread Raw
In response to Re: fixing Makefile.shlib for solaris/gcc with -m64 flag  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I tried that but it didn't work.

Also on Solaris it typically uses the ld in /usr/ccs/bin/ld which uses "-64" as its flag for 64 bit 
and if you put LDFLAGS out there it will fail as unrecognized unless gcc parses -64 to -m64.

Putting -m64 in CC will do the workaround but then I guess that's what CFLAGS is for..

Regards,
Jignesh


Tom Lane wrote:
> "Jignesh K. Shah" <J.K.Shah@Sun.COM> writes:
>> simple if I use -m64 for 64 bit then all end binaries are generated 64-bit and the shared libraries 
>> are generated 32-bit and the compilation fails (ONLY ON SOLARIS) since that particular line is only 
>> for the condition Solaris AND gcc.
> 
>> If I use the COMPILER which is CC + CFLAGS it passes -m64 properly to it and generates shared 
>> libraries 64-bit and the compile continues..
> 
> Hmm ... I see we're doing it that way already for some other platforms,
> but I can't help thinking it's a kluge.  Wouldn't the correct answer be
> that -m64 needs to be in LDFLAGS?
> 
>             regards, tom lane


pgsql-hackers by date:

Previous
From: Kim
Date:
Subject: Re: [PERFORM] unusual performance for vac following 8.2
Next
From: Stefan Kaltenbrunner
Date:
Subject: Re: [COMMITTERS] pgsql: Implement width_bucket() for the