| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: static libperl? |
| Date: | 2005-08-24 20:24:10 |
| Message-ID: | 8718.1124915050@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)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 making a 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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-08-24 20:34:12 | Re: TODO questions |
| Previous Message | Tom Lane | 2005-08-24 20:13:43 | Re: TODO questions |