pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Building PL/Perl without libperl.so fails
5+ messages / 4 participants
[nested] [flat]

* Building PL/Perl without libperl.so fails
@ 2002-12-30 14:03 Palle Girgensohn <girgen@pingpong.net>
  2003-01-02 20:27 ` Re: Building PL/Perl without libperl.so fails Tom Lane <tgl@sss.pgh.pa.us>
  2003-01-03 12:39 ` Re: Building PL/Perl without libperl.so fails Daniel Kalchev <daniel@digsys.bg>
  0 siblings, 2 replies; 5+ messages in thread

From: Palle Girgensohn @ 2002-12-30 14:03 UTC (permalink / raw)
  To: pgsql-interfaces

Hi!

With FreeBSD 5.0, there is no libperl.so installed, only libperl.a. This 
makes building PL/Perl fail:

*** Cannot build PL/Perl because libperl is not a shared library.
*** You might have to rebuild your Perl installation.  Refer to
*** the documentation for details.

I'd rather link libplperl with a static libperl.a than adding a shared 
libperl.so to the perl port. Can this be done, or will something break?

/Palle




^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Building PL/Perl without libperl.so fails
  2002-12-30 14:03 Building PL/Perl without libperl.so fails Palle Girgensohn <girgen@pingpong.net>
@ 2003-01-02 20:27 ` Tom Lane <tgl@sss.pgh.pa.us>
  2003-01-02 20:41   ` Re: Building PL/Perl without libperl.so fails Palle Girgensohn <girgen@pingpong.net>
  1 sibling, 1 reply; 5+ messages in thread

From: Tom Lane @ 2003-01-02 20:27 UTC (permalink / raw)
  To: Palle Girgensohn <girgen@pingpong.net>; +Cc: pgsql-interfaces

Palle Girgensohn <girgen@pingpong.net> writes:
> I'd rather link libplperl with a static libperl.a than adding a shared 
> libperl.so to the perl port. Can this be done, or will something break?

It will not work unless your platform is one where PIC code generation
is the default, so that the contents of libperl.a are amenable to
inclusion into a .so library.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Building PL/Perl without libperl.so fails
  2002-12-30 14:03 Building PL/Perl without libperl.so fails Palle Girgensohn <girgen@pingpong.net>
  2003-01-02 20:27 ` Re: Building PL/Perl without libperl.so fails Tom Lane <tgl@sss.pgh.pa.us>
@ 2003-01-02 20:41   ` Palle Girgensohn <girgen@pingpong.net>
  2003-01-04 10:26     ` Re: Building PL/Perl without libperl.so fails Peter Eisentraut <peter_e@gmx.net>
  0 siblings, 1 reply; 5+ messages in thread

From: Palle Girgensohn @ 2003-01-02 20:41 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-interfaces

How about FreeBSD 5.0?

FreeBSD 4.x has libperl.so, 5.0 only has libperl.a

/Palle

--On torsdag, januari 02, 2003 15.27.31 -0500 Tom Lane <tgl@sss.pgh.pa.us> 
wrote:

> Palle Girgensohn <girgen@pingpong.net> writes:
>> I'd rather link libplperl with a static libperl.a than adding a shared
>> libperl.so to the perl port. Can this be done, or will something break?
>
> It will not work unless your platform is one where PIC code generation
> is the default, so that the contents of libperl.a are amenable to
> inclusion into a .so library.
>
> 			regards, tom lane





^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Building PL/Perl without libperl.so fails
  2002-12-30 14:03 Building PL/Perl without libperl.so fails Palle Girgensohn <girgen@pingpong.net>
  2003-01-02 20:27 ` Re: Building PL/Perl without libperl.so fails Tom Lane <tgl@sss.pgh.pa.us>
  2003-01-02 20:41   ` Re: Building PL/Perl without libperl.so fails Palle Girgensohn <girgen@pingpong.net>
@ 2003-01-04 10:26     ` Peter Eisentraut <peter_e@gmx.net>
  0 siblings, 0 replies; 5+ messages in thread

From: Peter Eisentraut @ 2003-01-04 10:26 UTC (permalink / raw)
  To: Palle Girgensohn <girgen@pingpong.net>; +Cc: pgsql-interfaces

Palle Girgensohn writes:

> FreeBSD 4.x has libperl.so, 5.0 only has libperl.a

Then whatever change was made in 5.0 needs to be reverted.  You also need
a libperl.so if you want to use mod_perl, which probably also has a
considerable market.

-- 
Peter Eisentraut   peter_e@gmx.net




^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Building PL/Perl without libperl.so fails
  2002-12-30 14:03 Building PL/Perl without libperl.so fails Palle Girgensohn <girgen@pingpong.net>
@ 2003-01-03 12:39 ` Daniel Kalchev <daniel@digsys.bg>
  1 sibling, 0 replies; 5+ messages in thread

From: Daniel Kalchev @ 2003-01-03 12:39 UTC (permalink / raw)
  To: Palle Girgensohn <girgen@pingpong.net>; +Cc: pgsql-interfaces

Palle,

While this should be doable (by patching configure/Makefiles), why would you 
not want to have libperl.so?

On many systems, the .a files are considered 'development', while the .so 
files are considered 'runtime'. Or is the libperl.a on FreeBSD 5.0 different?

Daniel

>>>Palle Girgensohn said:
 > Hi!
 > 
 > With FreeBSD 5.0, there is no libperl.so installed, only libperl.a. This 
 > makes building PL/Perl fail:
 > 
 > *** Cannot build PL/Perl because libperl is not a shared library.
 > *** You might have to rebuild your Perl installation.  Refer to
 > *** the documentation for details.
 > 
 > I'd rather link libplperl with a static libperl.a than adding a shared 
 > libperl.so to the perl port. Can this be done, or will something break?
 > 
 > /Palle
 > 
 > 
 > ---------------------------(end of broadcast)---------------------------
 > TIP 6: Have you searched our list archives?
 > 
 > http://archives.postgresql.org





^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2003-01-04 10:26 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2002-12-30 14:03 Building PL/Perl without libperl.so fails Palle Girgensohn <girgen@pingpong.net>
2003-01-02 20:27 ` Tom Lane <tgl@sss.pgh.pa.us>
2003-01-02 20:41   ` Palle Girgensohn <girgen@pingpong.net>
2003-01-04 10:26     ` Peter Eisentraut <peter_e@gmx.net>
2003-01-03 12:39 ` Daniel Kalchev <daniel@digsys.bg>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox