On Thu, 11 Dec 2003, Dave Page wrote:
> > "Dave Page" <[EMAIL PROTECTED]> writes:
> > > gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes
> > > -Wmissing-declarations prod -I../../src/include -D_GNU_SOURCE
> > > -I/usr/include -c -o path.o path.c
> > > gcc: cannot specify -o with -c or -S
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> How is "prod" getting into that command line? I suspect it's coming
>> from an environment variable like PROFILE or CFLAGS ...
> Is there a case for making Makefile/shell variables and defines we use
> have less generic names?
Havi
Tom Lane wrote:
"Dave Page" <[EMAIL PROTECTED]> writes:
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes
-Wmissing-declarations prod -I../../src/include -D_GNU_SOURCE
-I/usr/include -c -o path.o path.c
gcc: cannot specify -o with -c or -S and multiple compilations
How is "prod" get
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 11 December 2003 15:31
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] 7.4 build problem on Linux Vserver
>
> "Dave Page" <[EMAIL PROTECTED]> writes
"Dave Page" <[EMAIL PROTECTED]> writes:
> gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes
> -Wmissing-declarations prod -I../../src/include -D_GNU_SOURCE
> -I/usr/include -c -o path.o path.c
> gcc: cannot specify -o with -c or -S and multiple compilations
How is "prod" getting into that c
