GCC inserts my username in command line
 

Hi!
I'm tying to compile (postgresql 8.2.0) under:
SunOS 5.8 Generic_117350-36 sun4u sparc SUNW,Sun-Blade-100
GCC 3.4.3

and got problems during the compilation, the problem seems to be that gcc (or configure) adds my username (sjostric) to the gcc command line. Like this:

gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing sjostric -I../../src/port -DFRONTEND -I../../src/include -c -o isinf.o isinf.c

which results in that I get:
gcc: sjostric: No such file or directory
(extended output below)

My configure command line is nothing unusual:
/configure --prefix=/home/sjostric/postgresql/8.2.0 --exec-prefix=/home/sjostric/postgresql/8.2.0 --without-readline

I tried a post to the postgresql mailing list but no answer, so I thought there might be one you out there that understands why GCC does this ugly thing for me! (I dont think that this is a postgresql related thing)

Thanks!

/Rickard




Output:
---- 8< ----
make[3]: Entering directory `/home/sjostric/postgresql/src/postgresql-8.2.0/src/port'
gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing sjostric -I../../src/port -DFRONTEND -I../../src/include -c -o isinf.o isinf.c
gcc: sjostric: No such file or directory
make[3]: *** [isinf.o] Error 1
make[3]: *** Deleting file `isinf.o'
make[3]: Leaving directory `/home/sjostric/postgresql/src/postgresql-8.2.0/src/port'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/sjostric/postgresql/src/postgresql-8.2.0/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/sjostric/postgresql/src/postgresql-8.2.0'
*** Error code 2
make: Fatal error: Command failed for target `all'
(56)# postgresql-8.2.0/:
---- 8< ----

Well, I don't have any idea about that, but you can always download the PostGreSQL package instead of compiling from sources :)

I don't think it is gcc. Run configure and then look at the Makefile it produces. If configure is the problem, then it is probably back to a postgresql problem since they distribute the configure script.

Most importantly, look at config.log ... and which postgresql
mailing-list did you supposedly send this to? I didn't see it,
and it's not in the archives...


Cheers,
Tink

I had a env variable PROFILE set to my usename sjostric. Re-setting this to nothing fixed the problem... :-)