Re: compile problem on a vax
От | Tom Lane |
---|---|
Тема | Re: compile problem on a vax |
Дата | |
Msg-id | 22691.979784060@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | compile problem on a vax ("bart sikkes" <b.sikkes@student.utwente.nl>) |
Ответы |
Re: compile problem on a vax
Re: compile problem on a vax |
Список | pgsql-ports |
"bart sikkes" <b.sikkes@student.utwente.nl> writes: > I have been trying to compile postgresql-7.0.3 on a uVax II running NetBSD > 1.5, after some problems i am almost there, now i only get these errors > during the final compile: >> gcc -I../include -I../backend -O2 -pipe -Wall -Wmissing-prototypes -Wmissin > g-declarations -o postgres access/SUBSYS.o bootstrap/SUBSYS.o >> catalog/SUBSYS.o commands/SUBSYS.o executor/SUBSYS.o lib/SUBSYS.o > libpq/SUBSYS.o main/SUBSYS.o parser/SUBSYS.o nodes/SUBSYS.o >> optimizer/SUBSYS.o port/SUBSYS.o postmaster/SUBSYS.o regex/SUBSYS.o > rewrite/SUBSYS.o storage/SUBSYS.o tcop/SUBSYS.o >utils/SUBSYS.o > ../utils/version.o -lcrypt -lcompat -lm -lutil -ltermcap -lcurses >> access/SUBSYS.o: Undefined symbol `r0' referenced >> storage/SUBSYS.o: Undefined symbol `r0' referenced >> collect2: ld returned 1 exit status I'll bet that the assembler is taking the 'r0' references in the TAS() snippet to be a global-variable name, rather than register name as intended. Possibly $0 or %0 or some such locution is needed. The VAX port has evidently not been used in a long time. I had noticed that it was inconsistent with all the other ports in defining slock_t in s_lock.h rather than in the OS-specific header files; that's clearly wrong now. Feel free to submit a patch once you get it worked out. regards, tom lane
В списке pgsql-ports по дате отправления: