add CUSTOM_MSPACK_LIBS="/usr/local/include/mspack.h" to ebuild src configure when libmspack gets into portage.
assign to vmware@gentoo.com
(In reply to kundarsa from comment #1) > assign to vmware@gentoo.com oops, please assign to vmware@gentoo.org
(In reply to kundarsa from comment #0) > add CUSTOM_MSPACK_LIBS="/usr/local/include/mspack.h" to ebuild src configure > when libmspack gets into portage. If libmspack is installing headers into /usr/local/include, then the mspack ebuild needs to be adjusted.
did a merge off ebuild and got >>> Merging dev-libs/libmspack-0.5 to / --- /usr/ --- /usr/include/ >>> /usr/include/mspack.h --- /usr/lib64/ >>> /usr/lib64/libmspack.so -> libmspack.so.0.1.0 >>> /usr/lib64/libmspack.so.0 -> libmspack.so.0.1.0 >>> /usr/lib64/libmspack.so.0.1.0 the /usr/local must have been from my manual configure make install... open-vm-tools src configure would be changed to CUSTOM_MSPACK_LIBS="/usr/include/mspack.h" sorry about that. will wipe and reinstall my AT test box its getting dirty :P
will put in an ebuild patch for this later. vgauth and deploypkg look like they will both be enabled and building.
Current version is app-emulation/open-vm-tools-10.1.15:0 . @ kundarsa : Against which version of open-vm-tools was this Bug ? Is this Bug still valid ? NEEDINFO @ Mike : Otherwise, I would suggest to close this BUG as OBSOLETE. Thanks.
(kundarsa in comment #5) : 2015-05-07 > will put in an ebuild patch for this later. PING
no longer using this software, i suggest close until another user can confirm this is an issue.