Re: static libperl?
| От | Jim C. Nasby |
|---|---|
| Тема | Re: static libperl? |
| Дата | |
| Msg-id | 20050824223352.GD96732@pervasive.com обсуждение исходный текст |
| Ответ на | Re: static libperl? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
On Wed, Aug 24, 2005 at 04:24:10PM -0400, Tom Lane wrote: > Andrew Dunstan <andrew@dunslane.net> writes: > > Earlier today I noticed these lines in this buildfarm log > > http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=platypus&dt=2005-08-16%2002:05:00 > > > /usr/bin/ld: /usr/local/lib/perl5/5.6.1/mach/CORE/libperl.a(perl.o): relocation R_X86_64_32S can not be used when makinga shared object; recompile with -fPIC > > /usr/local/lib/perl5/5.6.1/mach/CORE/libperl.a: could not read symbols: Bad value > > I've fixed Makefile.freebsd to assert allow_nonpic_in_shlib only on > i386; that should solve the above problem (by keeping platypus from > trying to build plperl :-(). It may be there are some other > architectures we can safely set allow_nonpic_in_shlib for, but I don't > know exactly which. Note that platypus is still configured to build plperl... ISTM that if it's unable to do so we should throw some kind of error, prefferably at configure time. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com 512-569-9461
В списке pgsql-hackers по дате отправления: