Issue 88: "Unsupported socket" errors on Mac OS X

[stepcut]

Hello,

Is this bug still valid? Or has something magically fixed it since
June ?

This is the only blocker for a new stable release that I know of at
the moment.

- jeremy

[Anton van Straaten]

As far as I know it's still valid. The most recent discussion of this
was in the thread containing this message:

http://www.mail-archive.com/haskel...@haskell.org/msg65671.html

(I immodestly linked to my own message in that thread because it
contains a summary of the causes of the problem.)

Short of fixing the actual problem relating to Happstack's TH usage that
only seems to occur when running on the Mac, it seems to me that the
most expedient solution would be to assume that IPv6 support exists,
which would allow the offending TH code to be eliminated. This would
then trigger errors when someone tries to build Happstack on a platform
with no IPv6 support, but my guess is that this would be a less common
scenario.

Anton

[stepcut]

On Nov 9, 12:21 pm, Anton van Straaten <an...@appsolutions.com> wrote:
> Short of fixing the actual problem relating to Happstack's TH usage that
> only seems to occur when running on the Mac, it seems to me that the
> most expedient solution would be to assume that IPv6 support exists,
> which would allow the offending TH code to be eliminated.  This would
> then trigger errors when someone tries to build Happstack on a platform
> with no IPv6 support, but my guess is that this would be a less common
> scenario.

I believe the unsupported IPv6 platform is Windows.

These threads also seem relevant:

http://groups.google.com/group/happs/browse_thread/thread/a30e930e4e1dfb4a/82597ff8bc481708?lnk=gst&q=ipv6+windows#82597ff8bc481708

http://groups.google.com/group/happs/browse_thread/thread/2b74ac8151a257ed/8f5740cf85a18d19?lnk=gst&q=ipv6+windows#8f5740cf85a18d19

And this bug:

http://code.google.com/p/happstack/issues/detail?id=57&can=1&q=ipv6%20windows

- jeremy

[stepcut]

Hello,

I believe I have resolved this bug. It only occurs if you are using
the newer versions of the Network library because the module that
defines SocketAddrInet6 changed. The patch should fix it to work with
the old and new versions now.Also, I think this bug was probably not
limited to just OS X.

http://code.google.com/p/happstack/issues/detail?id=88&can=1&q=unsupported%20socket

- jeremy