Buildng for Windows #7
Comments
|
If you have the gem installed, then you don't need to rebuild. You could just do "ruby -Iext test/*.rb" I think. If you want to run the rake task, you'll have to pass the options that you passed on the command line to build rkerberos in the first place. So, something like "rake test -- --with-rkerberos-dir=C:/path/to/kerberos". |
|
Hi, Thanks for the reply. I'll take a look on Tuesday when I'm next back at I haven't yet been able to get the gem to install... as it's failing at Cheers Phil Daniel Berger wrote on 02/04/15 19:56:
|
|
Ah, it didn't successfully install. Ok, then try "gem install rkerberos -- --with-rkerberos-dir=C:/path/to/kerberos". |
|
Any luck? |
|
Sadly not... at least not yet. I haven't been able to upload the logs to somewhere I can share with you
I think the problem is that some parts of the kerberos codebase may not Daniel Berger wrote on 08/04/15 16:05:
|
|
The only includes in rkerberos are these: None of those are unix-specific, so I'm guessing it's something else. Anyway, we'll take a look at the logs once you post them and see what we can do to help. |
|
Oh, nm, you mean within kerberos itself. Hm, could be, I don't think I ever tried to build it on Windows. |
|
Just curious, did you build from source or use one of the kerberos installers? Because I noticed that the installer doesn't include the admin headers for some reason. |
|
I built from source, so have all the libraries and header files available. The problem is a header imported from kadm5/admin.h. which isn't available on Windows :( Daniel Berger wrote on 08/04/15 19:36:
|
|
Hmm, could be a bug in kerberos. What happens if you explicitly include winsock2.h in rpc.h before that line? Edit: Or maybe substitute netinet/in.h with winsock2.h, can't remember now. |
Hi,
I'm trying to get rkerberos to build on Windows 7, so far without any luck.
I have the krb5-1.13.1 from MIT built and installed.
When I try to run either "gem install rkerberos", or rake test in the gems directory, I get:
--- 8< ---
z:\exe\Ruby21-x64\lib\ruby\gems\2.1.0\gems\rkerberos-0.1.3>rake test
Failed to remove tmp/x64-mingw32/stage: No such file or directory @ unlink_inter
nal - tmp/x64-mingw32/stage
Failed to remove tmp/x64-mingw32/rkerberos/2.1.5/mkmf.log: No such file or direc
tory @ unlink_internal - tmp/x64-mingw32/rkerberos/2.1.5/mkmf.log
mkdir -p tmp/x64-mingw32/rkerberos/2.1.5
cd tmp/x64-mingw32/rkerberos/2.1.5
z:/exe/Ruby21-x64/bin/ruby.exe -I. ../../../../ext/rkerberos/extconf.rb
checking for krb5.h... no
checking for main() in -lkrb5... no
warning: com_err not found, usually a dependency for kadm5clnt
checking for kadm5/admin.h... no
*** ../../../../ext/rkerberos/extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.
Provided configuration options:
': kadm5clnt library not found--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=../../../../ext/rkerberos
--curdir
--ruby=z:/exe/Ruby21-x64/bin/ruby
--with-rkerberos-dir
--without-rkerberos-dir
--with-rkerberos-include
--without-rkerberos-include=${rkerberos-dir}/include
--with-rkerberos-lib
--without-rkerberos-lib=${rkerberos-dir}/lib
--with-krb5lib
--without-krb5lib
--with-com_err-config
--without-com_err-config
--with-pkg-config
--without-pkg-config
../../../../ext/rkerberos/extconf.rb:15:in `
(RuntimeError)
rake aborted!
Command failed with status (1): [z:/exe/Ruby21-x64/bin/ruby.exe -I. ../../....]
Tasks: TOP => test => test:all => compile => compile:x64-mingw32 => compile:rker
beros:x64-mingw32 => copy:rkerberos:x64-mingw32:2.1.5 => tmp/x64-mingw32/rkerber
os/2.1.5/rkerberos.so => tmp/x64-mingw32/rkerberos/2.1.5/Makefile
(See full trace by running task with --trace)
--- >8 ---
Any sugestions?
I'm not very familiar with ruby, so apologies if I'm missing anything really obvious.
Regards
Phil
The text was updated successfully, but these errors were encountered: