Interesting. I don't think any of us have tried compiling open-vm-tools on QNX, though I recall hearing of others using them on that platform. Could you please provide the output from make that shows the error, as well as the contents of config.log?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
# ./configure --without-x
[...]
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/qnx632/host/qnx6/x86/usr/bin/ntox86-ld
checking if the linker (/usr/qnx632/host/qnx6/x86/usr/bin/ntox86-ld) is GNU ld... yes
checking whether the g++ linker (/usr/qnx632/host/qnx6/x86/usr/bin/ntox86-ld) supports shared libraries... no
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/qnx632/host/qnx6/x86/usr/bin/ntox86-ld) supports shared libraries... no
checking dynamic linker characteristics... nto-qnx6.3.2 ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for pkg-config... no
checking for X... disabled
checking for crypt in -lcrypt... no
configure: error: libcrypt not found. Please install the libc/libcrypt devel package(s).
#
File Added: config.log
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We need libcrypt because of the call to crypt(3) within lib/auth/authPosix.c. There's some code there to use pam instead of libcrypt, so you can try running with that (add USE_PAM to CPPFLAGS in configure.ac and regenerate configure using autoreconf). It appears we've never enabled that code path for the Tools before, so there may be other issues.
Alternatively, if you don't care about VIX SDK guest operations, you could comment out the inclusion of crypt.h from authPosix.c and heavily modify Auth_AuthenticateUser so that it always returns NULL, or always calls setpwent(), Posix_Getpwnam(user), and endpwent().
Elliot, if you're reading this, does this mean we've never actually enabled pam support for guestd, and thus either 1) should, or 2) can remove the pam.d files that we distribute?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks! I did as you've suggested but I got the following error message when running autoreconf:
Can't locate object method "path" via package "Autom4te::Request" at /opt/bin/atom4te line 81.
Any clues?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2008-06-02
Logged In: YES
user_id=18318
Originator: NO
josuejr - it's hard to give QNX-specific advice on fixing errors like that, but perhaps you could get in touch with Rick Duff, who I believe has worked on porting open-vm-tools to QNX. See http://community.qnx.com/sf/projects/vmware
Adar - yea, if we never define USE_PAM then I guess we're shipping the pam.d file in vain. However, PAM gives more flexibility to sysadmins, so it would really be nice to fix this. I'll put it on the todo list.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2008-07-11
Logged In: YES
user_id=18318
Originator: NO
Josue - have you had any luck getting things to build? Did you get in contact with the QNX project for open-vm-tools?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1867590
Originator: NO
Interesting. I don't think any of us have tried compiling open-vm-tools on QNX, though I recall hearing of others using them on that platform. Could you please provide the output from make that shows the error, as well as the contents of config.log?
Logged In: YES
user_id=2094227
Originator: YES
This is the console output.
# ./configure --without-x
[...]
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/qnx632/host/qnx6/x86/usr/bin/ntox86-ld
checking if the linker (/usr/qnx632/host/qnx6/x86/usr/bin/ntox86-ld) is GNU ld... yes
checking whether the g++ linker (/usr/qnx632/host/qnx6/x86/usr/bin/ntox86-ld) supports shared libraries... no
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/qnx632/host/qnx6/x86/usr/bin/ntox86-ld) supports shared libraries... no
checking dynamic linker characteristics... nto-qnx6.3.2 ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for pkg-config... no
checking for X... disabled
checking for crypt in -lcrypt... no
configure: error: libcrypt not found. Please install the libc/libcrypt devel package(s).
#
File Added: config.log
"./configure --without-x" log on QNX 6.3.2
Logged In: YES
user_id=1867590
Originator: NO
We need libcrypt because of the call to crypt(3) within lib/auth/authPosix.c. There's some code there to use pam instead of libcrypt, so you can try running with that (add USE_PAM to CPPFLAGS in configure.ac and regenerate configure using autoreconf). It appears we've never enabled that code path for the Tools before, so there may be other issues.
Alternatively, if you don't care about VIX SDK guest operations, you could comment out the inclusion of crypt.h from authPosix.c and heavily modify Auth_AuthenticateUser so that it always returns NULL, or always calls setpwent(), Posix_Getpwnam(user), and endpwent().
Elliot, if you're reading this, does this mean we've never actually enabled pam support for guestd, and thus either 1) should, or 2) can remove the pam.d files that we distribute?
Logged In: YES
user_id=2094227
Originator: YES
Thanks! I did as you've suggested but I got the following error message when running autoreconf:
Can't locate object method "path" via package "Autom4te::Request" at /opt/bin/atom4te line 81.
Any clues?
Logged In: YES
user_id=18318
Originator: NO
josuejr - it's hard to give QNX-specific advice on fixing errors like that, but perhaps you could get in touch with Rick Duff, who I believe has worked on porting open-vm-tools to QNX. See http://community.qnx.com/sf/projects/vmware
Adar - yea, if we never define USE_PAM then I guess we're shipping the pam.d file in vain. However, PAM gives more flexibility to sysadmins, so it would really be nice to fix this. I'll put it on the todo list.
Logged In: YES
user_id=18318
Originator: NO
Josue - have you had any luck getting things to build? Did you get in contact with the QNX project for open-vm-tools?