help-gss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GSS installed header in include/gss/api.h instead of gssapi.h


From: Markus Mazurczak
Subject: Re: GSS installed header in include/gss/api.h instead of gssapi.h
Date: Mon, 31 May 2010 21:40:26 +0200
User-agent: Thunderbird 2.0.0.24 (Windows/20100228)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Simon,

thanks for your answer. I think it is an good idea to implement the
compat directory and make it retrievable via pkg-config.

As a workaround i just created a file /usr/local/gssapi.h which does
nothing but including gss.h.

Regards,

Markus

Simon Josefsson schrieb:
> Markus Mazurczak <address@hidden> writes:
> 
>> configure: error: gssapi.h header file is required for GSSAPI
>>
>> libgss is available:
>>
>> ldconfig -v | grep gss
>>         libgss.so.1 -> libgss.so.1.1.0
>>
>> but there is no gssapi.h header installed. Instead the following headers
>> were installed under /usr/local/include/gss:
>>
>> - api.h
>> - ext.h
>>
>> Did i do something wrong during compiling GSS or is there something i
>> forgot?
>> I dont understand why postgresql need gssapi.h but gss just installed me
>> the above mentioned headers. Is it an gss or postgres failure?
> 
> Hi Markus.  Thanks for your interest.  The problem is that postgresql
> assumes the GSS-API header file is called 'gssapi.h', but in GNU GSS it
> is called 'gss.h' (should be available in /usr/include/gss.h for you).
> If you modify PostgreSQL to include gss.h instead of gssapi.h, hopefully
> things will work.
> 
> I don't recall anywhere in the standard that _requires_ that the header
> file is called 'gssapi.h', but I see how it could simplify building
> packages that makes this assumption (many do).
> 
> What GNU GSS could do here is to install a file
> $prefix/include/gss/compat/gssapi.h which only does '#includes <gss.h>',
> and also make 'pkg-config --cflags gss' include a
> -I$prefix/include/gss/compat directory in its output.
> 
> Thoughts?
> 
> Thanks,
> /Simon
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)

iQEcBAEBAgAGBQJMBBCqAAoJEO3Dr95SC7zh9IQIAIy1Z/DIs8mxrQR1LyHxcr7m
fK1/DzkKHKhXyzNuzvVnXNJwLybMotC6cXlaHe4APzm7OOSPv9FNsWXc/DWCLJ/c
7mGx/DznyJ5fEfth6l+aTXbB7IAvLL2aUjNcdNWCPoyGdfQE4U+qrytBlGZUHZsv
1665uPOKTub+N5uMNtmHMZXJn6t1O7q5NJBqa7HQmt7v++4ITQuRe2uQrRxk3Aat
lBNlwokB7z9FU/saJ/Ebrw8a8pE4my2No6ckWOw5V3NTNdbVNXUclneRoF7InMRw
hlsAiib57VFnTpWVxh37zZhhvTKKYi5hdU9USf03eHZur/HhGA9gBqvHmtXYa1g=
=8s9P
-----END PGP SIGNATURE-----

Attachment: 0x520BBCE1.asc
Description: application/pgp-keys


reply via email to

[Prev in Thread] Current Thread [Next in Thread]