Thread: plperl error when making 8.2dev CVS
Hi, i was trying to compile CVS using --with-plperl (perl installed is 5.6.1) and i get this error when make go inside plperl: make[3]: *** No rule to make target `SPI.xs', needed by `SPI.c'. Stop. make[2]: *** [all] Error 1 make[1]: *** [all] Error 2 make: *** [all] Error 2 -- regards, Jaime Casanova (DBA: DataBase Aniquilator ;)
Jaime Casanova wrote: > Hi, > > i was trying to compile CVS using --with-plperl (perl installed is > 5.6.1) and i get this error when make go inside plperl: > > make[3]: *** No rule to make target `SPI.xs', needed by `SPI.c'. Stop. Did you delete that file? It's part of the sources. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
On 11/8/05, Alvaro Herrera <alvherre@commandprompt.com> wrote: > Jaime Casanova wrote: > > Hi, > > > > i was trying to compile CVS using --with-plperl (perl installed is > > 5.6.1) and i get this error when make go inside plperl: > > fixing a bad typo in the message i try --with-perl (no --with-plperl like said above)... Just in case, someone tell me that's the error... the above was an error of typo in the message... > > make[3]: *** No rule to make target `SPI.xs', needed by `SPI.c'. Stop. > > Did you delete that file? It's part of the sources. > > -- > Alvaro Herrera http://www.CommandPrompt.com/ > The PostgreSQL Company - Command Prompt, Inc. > No... i didn't... and the file *is* in the plperl dir -- Atentamente, Jaime Casanova (DBA: DataBase Aniquilator ;)
On 11/8/05, Alvaro Herrera <alvherre@commandprompt.com> wrote: > Jaime Casanova wrote: > > On 11/8/05, Alvaro Herrera <alvherre@commandprompt.com> wrote: > > > Jaime Casanova wrote: > > > > make[3]: *** No rule to make target `SPI.xs', needed by `SPI.c'. Stop. > > > > > > Did you delete that file? It's part of the sources. > > > > No... i didn't... and the file *is* in the plperl dir > > Weird. So if you cd src/pl/plperl and ls, the file is there, yet it > tries to "make" it? That's weird. Did you try a make distclean after > changing your configure arguments? I've never seen this problem. > > -- > Alvaro Herrera http://www.CommandPrompt.com/ > PostgreSQL Replication, Consulting, Custom Development, 24x7 support > i think i did... but it was 1:30 am maybe i dream it, i will try 'make distclean' and configure again at night... -- regards, Jaime Casanova (DBA: DataBase Aniquilator ;)
Jaime Casanova wrote: > On 11/8/05, Alvaro Herrera <alvherre@commandprompt.com> wrote: > > Jaime Casanova wrote: > > > make[3]: *** No rule to make target `SPI.xs', needed by `SPI.c'. Stop. > > > > Did you delete that file? It's part of the sources. > > No... i didn't... and the file *is* in the plperl dir Weird. So if you cd src/pl/plperl and ls, the file is there, yet it tries to "make" it? That's weird. Did you try a make distclean after changing your configure arguments? I've never seen this problem. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
On 11/8/05, Alvaro Herrera <alvherre@commandprompt.com> wrote: > Jaime Casanova wrote: > > On 11/8/05, Alvaro Herrera <alvherre@commandprompt.com> wrote: > > > Jaime Casanova wrote: > > > > make[3]: *** No rule to make target `SPI.xs', needed by `SPI.c'. > Stop. > > > > > > Did you delete that file? It's part of the sources. > > > > No... i didn't... and the file *is* in the plperl dir > > Weird. So if you cd src/pl/plperl and ls, the file is there, yet it > tries to "make" it? That's weird. Did you try a make distclean after > changing your configure arguments? I've never seen this problem. > ok, i execute 'make distclean' and then get the same error when making after configuring with --with-perl -- Atentamente, Jaime Casanova (DBA: DataBase Aniquilator ;)
Jaime Casanova wrote: > On 11/8/05, Alvaro Herrera <alvherre@commandprompt.com> wrote: > > Jaime Casanova wrote: > > > On 11/8/05, Alvaro Herrera <alvherre@commandprompt.com> wrote: > > > > Jaime Casanova wrote: > > > > > make[3]: *** No rule to make target `SPI.xs', needed by `SPI.c'. > > Stop. > > > > > > > > Did you delete that file? It's part of the sources. > > > > > > No... i didn't... and the file *is* in the plperl dir > > > > Weird. So if you cd src/pl/plperl and ls, the file is there, yet it > > tries to "make" it? That's weird. Did you try a make distclean after > > changing your configure arguments? I've never seen this problem. > > ok, i execute 'make distclean' and then get the same error when making > after configuring with --with-perl Is this a clean source tree? Try cvs update -C (beware it'll destroy all your local changes) -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Jaime Casanova wrote:
>> ok, i execute 'make distclean' and then get the same error when making
>> after configuring with --with-perl
> Is this a clean source tree? Try cvs update -C (beware it'll destroy
> all your local changes)
I'm wondering about a clock skew problem (if machine's clock is in the
past then SPI.xs might appear newer than derived files). If not that,
it sounds like it would have to be a bug in gmake.
regards, tom lane
On 11/9/05, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Alvaro Herrera <alvherre@commandprompt.com> writes: > > Jaime Casanova wrote: > >> ok, i execute 'make distclean' and then get the same error when making > >> after configuring with --with-perl > > > Is this a clean source tree? Try cvs update -C (beware it'll destroy > > all your local changes) > > I'm wondering about a clock skew problem (if machine's clock is in the > past then SPI.xs might appear newer than derived files). If not that, > it sounds like it would have to be a bug in gmake. > > regards, tom lane > mmm... sorry for the noise... i download the CVS from my windows box (because i can't get my internal modem to work with linux :) for some reason i don't know sometimes when moving from windows to a linux dir shared with smb (in the same machine)... it converts file names from uppercase to lowercase so the file in linux was named spi.xs not SPI.xs... i realize that this was the problem just when replacing the entire source tree with same i downloaded in windows... this time the names got right and everything is fine... -- regards, Jaime Casanova (DBA: DataBase Aniquilator ;)