Bug 28272

Summary:

Update port: net/libsocket++

Product:

Ports & Packages

Reporter:

Heiko Schaefer <hschaefer>

Component:

Individual Port(s)

Assignee:

Ade Lovett <ade>

Status:

Closed FIXED

Severity:

Affects Only Me

Priority:

Normal

Version:

Latest

Hardware:

Any

OS:

Any

Attachments:

Description	Flags
file.shar	none
patch-af	none
libsocket-port-diff	none

Description Heiko Schaefer 2001-06-19 11:40:01 UTC

there is a newer version of libsocket++ (1.11) than the one in net/libsocket++ (1.10). Lauri Nurmi has done a cleanup of 1.11 and provides his version at http://www.kauhajoki.fi/~lanurmi/socket++/. The library now supports exception handling, but the interface has subtly changed since the 1.10 version.
additionally i fixed a freebsd-specific problem with bind() that's present in the port for 1.10 already.
(open problem: for an unknown to me reason the shared version of the library that gets built is not ok...).

attached is the port i am using - hoped it might be useful for other people as well :)
(if the attached .shar is damaged by the webform, i will gladly email it to whomever wants to look into this...)

Comment 1 dwcjr 2001-06-20 04:49:44 UTC

The usual routine is to provide a diff against the existing version 
instead of a shar.  can you make this diff?

-- 
David W. Chapman Jr.

Comment 2 Heiko Schaefer 2001-06-20 08:59:44 UTC

Hi David,

> The usual routine is to provide a diff against the existing version
> instead of a shar.  can you make this diff?

wow, thanks for the quick reply :)

i'm not entirely sure that i got the attached diff right, but it seems to
be ok... additionally i introduced one more patch-file.

again, like i already stated in the problem report, this newer version of
libsocket++ (1.11) has a subtly incompatible interface... so if i was
assuming that lots of people use the current port of libsocket++-1.10,
then i would suggest to leave the old port and add my new one parallel to
it (it is more than likely that stuff which compiled against 1.10 is
broken against 1.11). but i really assume that noone uses the libsocket++
port anyway (at least no other port seems to depend on it), therefore it's
probably not worth having two ports for it. i've got no idea what the
usual way to deal with this would be ... just trying to make you aware of
the situation as i see it :)

cheers,

Heiko

Comment 3 dwcjr freebsd_committer

2001-06-27 04:46:25 UTC

State Changed
From-To: open->analyzed

Looks like it needs a repo copy, any suggestions of the new name?

Comment 4 dwcjr 2001-06-27 04:47:49 UTC

(open problem: for an unknown to me reason the shared version of the library that gets built is not ok...).

What does this mean?

Comment 5 Heiko Schaefer 2001-06-27 11:46:55 UTC

Hi David,

> (open problem: for an unknown to me reason the shared version of the
> library that gets built is not ok...).
>
> What does this mean?

the Makefile that comes with the distfile of libsocket++ only builds a
static (.a) version of the library. the old port for it provides a file
files/Makefile.lib that manages to build a shared version of the lib,
which also works. i just left this Makefile.lib in my version of the port,
but it doesn't seem to work. the shared library that comes out of the
mechanism seems to be corrupt - and i don't know why, nor do i know what
to look for to fix it.

probably one easy thing would be just to leave that out - not to build
any shared library at all. but then again i was hoping the mistake might
be a simple one that would be obvious to someone who knows more about the
whole ports mechnism....

Heiko

Comment 6 Ade Lovett freebsd_committer

2002-04-13 04:35:50 UTC

State Changed
From-To: analyzed->closed

Timeout (9 months) in analyzed.

Comment 7 Ade Lovett freebsd_committer

2002-04-13 04:35:50 UTC

Responsible Changed
From-To: freebsd-ports->	 ade

My fault[tm]