Skip to Content.
Sympa Menu

freetds - Re: [freetds] Getting it to all work on HPUX

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: christos AT zoulas.com (Christos Zoulas)
  • To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] Getting it to all work on HPUX
  • Date: Mon, 9 Feb 2009 09:04:38 -0500

On Feb 9, 11:34am, freddy77 AT gmail.com (Frediano Ziglio) wrote:
-- Subject: Re: [freetds] Getting it to all work on HPUX

| 2009/2/7 Christos Zoulas <christos AT zoulas.com>:
| > On Feb 6, 9:45pm, jklowden AT freetds.org ("James K. Lowden") wrote:
| > -- Subject: Re: [freetds] Getting it to all work on HPUX
| >
| > | Frediano Ziglio wrote:
| > | > > I think we should use an autoconf test to detect the presence of
| > | > > socklen_t instead of resorting to such ugliness .
| > | > >
| > | >
| > | > We already test for socklen_t. The problem is that HP-UX use
| > | > socklen_t* for last getsockopt argument in some cases and int in some
| > | > others (giving different defines).
| > |
| > | It reminds me of the gethostbyname_r fiasco. Solvable with autoconf,
but
| > | not pretty. Perhaps another project has already written the approprite
| > | m4?
| >
| > Look in the tcsh's configure.in. Thank you HP *again*!
| >
| > christos
|
| I don't see nothing about getsockopt in tcsh's configure.in, only
| about socklen_t (which we already test in our configure script). The
| problem is not socklen_t but the use of it in getsockopt !!
| Yes, my workaround is ugly...

And it will not work for big-endian _LP64 machines where socklen_t is 32bits.
I don't know if any such beasts exist. Let me try to find a getsockopt test.

christos




Archive powered by MHonArc 2.6.24.

Top of Page