Build krb5 on cygwin

[Weijun Wang]

This is my first time trying to build MIT krb5 on cygwin. I have gcc installed and "bash configure" fails with

configure: error: Shared libraries are not yet supported on this platform.

Adding --disable-shared --enable-static but see the same error.

I tried using MSVC 2013 but it shows "cl --version" not supported.

Thanks
Max




_______________________________________________
krbdev mailing list ***@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev

[Greg Hudson]

Post by Weijun Wang
This is my first time trying to build MIT krb5 on cygwin. I have gcc installed and "bash configure" fails with
configure: error: Shared libraries are not yet supported on this platform.
Adding --disable-shared --enable-static but see the same error.

Cygwin isn't a supported platform for MIT krb5, and I think it would
take a fair amount of work, or at least expertise, to get a cygwin build
working. We don't really support a static library build; I added the
partial support for --disable-shared --enable-static back when gcov
didn't work with shared libraries, and haven't maintained it.

Post by Weijun Wang
I tried using MSVC 2013 but it shows "cl --version" not supported.

I'm not sure where this is coming from. Our Windows build currently
requires MSVC 2010. Getting it to work with later versions might not
require too many changes.
_______________________________________________
krbdev mailing list ***@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev

[Weijun Wang]

Post by Greg Hudson

Post by Weijun Wang
This is my first time trying to build MIT krb5 on cygwin. I have gcc installed and "bash configure" fails with
configure: error: Shared libraries are not yet supported on this platform.
Adding --disable-shared --enable-static but see the same error.

Cygwin isn't a supported platform for MIT krb5, and I think it would
take a fair amount of work, or at least expertise, to get a cygwin build
working. We don't really support a static library build; I added the
partial support for --disable-shared --enable-static back when gcov
didn't work with shared libraries, and haven't maintained it.

I see. Cygwin does include krb5 libraries. I assume it's from MIT krb5 and maybe I can ask them how they compiled it.

Post by Greg Hudson

Post by Weijun Wang
I tried using MSVC 2013 but it shows "cl --version" not supported.

I'm not sure where this is coming from. Our Windows build currently
requires MSVC 2010. Getting it to work with later versions might not
require too many changes.

OK, I'll try again.

BTW, is there a configure option to force using MSVC? Now that I have gcc installed and it always choose gcc. I tried setting CC=/path/to/cl.exe but see

checking for gcc... /.../VC/bin/amd64/cl.exe
checking whether the C compiler works... no

Thanks
Max


_______________________________________________
krbdev mailing list ***@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev

[Benjamin Kaduk]

Post by Weijun Wang
BTW, is there a configure option to force using MSVC? Now that I have gcc installed and it always choose gcc. I tried setting CC=/path/to/cl.exe but see
checking for gcc... /.../VC/bin/amd64/cl.exe
checking whether the C compiler works... no

The build instructions in src/windows/README do not involve running
configure at all.

-Ben
_______________________________________________
krbdev mailing list ***@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev

[Benjamin Kaduk]

Post by Benjamin Kaduk

Post by Weijun Wang
BTW, is there a configure option to force using MSVC? Now that I have gcc installed and it always choose gcc. I tried setting CC=/path/to/cl.exe but see
checking for gcc... /.../VC/bin/amd64/cl.exe
checking whether the C compiler works... no

The build instructions in src/windows/README do not involve running
configure at all.

Though I suppose I should note that IIRC, the output of cl.exe is
not binary compatible with cygwin binaries, in terms of compiling a
library with cl.exe and linking into a cygwin binary. So if the
need is specifically to build updated cygwin binaries using newer
krb5 functionality, this is probably not the right path to go down.

-Ben
_______________________________________________
krbdev mailing list ***@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev