About tcurbishley

tcurbishley · ‎Dec 31, 2020

Thanks very much. That's exactly what I needed to know!

tcurbishley · ‎Dec 30, 2020

Does anyone have experience building the toolkit on a Cray? I'm trying to build the FNP toolkit on a Cray XC-30 running CLE 6.0 and it's not working. I'm using the SUSE reference Linux LSB x86-64 platform. (x64_lsb) version 11.16. The default Cray compilers return this right away: cc -c -fno-pie -g -I../machind -I. -DFD_LIMIT_CHECK -DFLEX_INET6 -g -O2 -m64 -D__BITS64 -pipe -D_POSIX_C_SOURCE=199506L -D_GNU_SOURCE -DOS_LINUX -pthread -DECMC_DISABLE_FAKE_TPM=1 -DLM_INTERNAL -DFLEXLM_KITBUILD -DFLEX_STATIC -DLINUX -DNO_ACTIVATION_SUPPORT lmcode.c No supported cpu target is set, CRAY_CPU_TARGET=x86-64 will be used. Load a valid targeting module or set CRAY_CPU_TARGET CC-2115 craycc: ERROR in command line "-pipe" is an invalid command-line option. CC-2115 craycc: ERROR in command line "-pthread" is an invalid command-line option. makefile:146: recipe for target 'lm_new.o' failed make: *** [lm_new.o] Error 1 Do I have the wrong platform or do I need to tweak the makefile? Any clues would be greatly appreciated!

tcurbishley · ‎Apr 28, 2020

I have ancient application that was built with Visual Studio 6.0 and CVF 6.0 under Windows XP and I would like to add Flexnet Publisher licensing to it. Crazy, I know, but I have reasons for wanting to do so. My goal is to implement a simple non-server file-based license capability on this old piece of software. The i86_n3 toolkit for 11.16.6.0, built successfully under Windows 10, of course, but I wasn't able to build it under XP/VS6. I was able to copy the built toolkit from Win 10 to Win XP. Using VS6, I created a project for the lmflex.c program. The source compiles correctly, but at link time, many of the system .lib files (e.g. dhcpcsvc.lib) can't be found, even though in many cases the corresponding DLLs are present. I suspect that if I obtained a suitably ancient version of the toolkit, I might have more success, but the version archive only goes back to 11.10 and doesn't include 32-bit Windows support. Has anyone else tried this? Does anyone have any advice as to how I might proceed? Many thanks in advance to any clues provided.

tcurbishley · ‎May 11, 2018

The answer is to build your vendor daemon on an older system. The maintainers of glibc go to great pains to ensure backward compatibility. It works very well going forward, that is, running an executable built with an older version of glibc runs on a system that features a newer version of glibc. Going in the other direction doesn't always work; an executable build with a newer version of glibc will not necessarily run on a system that features an older version of glibc. The dividing line appears to be glibc 2.14. If your older/newer systems are all earlier than 2.14, everything runs. Likewise if the older/newer systems are later than 2.14. It's when you build your executable on a "new" system (glibc > 2.14) and try to run it on an "older" system (glibc < 2.14) that there is trouble. The ray of hope is that executables built on an "older" system seem to run well on "new" systems. My solution was to create an "old" system in a virtual machine to build our daemons. In my case I created a VM in VirtualBox and installed CentOS 6.5, which has glibc 2.12. Add some compilers and install the FNP toolkit, and you're ready to build portable daemons. Hope this helps someone!

tcurbishley · ‎Jan 23, 2017

How do you compile your vendor daemon for maximum portability to older (Linux) systems? We recently upgraded our Linux development system to openSUSE LEAF 42.1. In the process, we movied from glibc2.14 to glibc 2.19. Previous to the upgrade, we could build a vendor daemon on our system and it would work on pretty much any Linux flavor and version we tried. Since the upgrade, our customers often see the following message when they start up lmadmin: "/lib/libc.so.6: version `GLIBC_2.14' not found (required by fnpdaemon)" As I understand (from posts like this: http://lightofdawn.org/wiki/wiki.cgi/-wiki/NewAppsOnOldGlibc), glibc is very backward compatible in that old apps will run under new glibc versions, but it's a little more complicated for new apps running under older versions of glibc. The daemon produced by our older glibc 2.14 system ran everywhere, while the same daemon built with glibc 2.19 needs glibc 2.14 or newer. I would like to be able to build a vendor daemon on our development system that runs on the maximum possible number of target systems. Perhaps that means linking against an older glibc. Perhaps there are other tricks. How do you build your vendor daemon?

tcurbishley · ‎May 19, 2014

Hi Steven, I'm in the same boat as you with regard to support for lmadin installation - it's hard to find any documentation. I'm sorry you never got a reply to this question. I'll share my answer in case it helps anyone else. The lmadmin installer is a 32-bit application, even though lmadmin itself may be a 64-bit application. Your 64-bit Linux platform may not include 32-bit support by default. If you get the "bad ELF interpreter" message, try installing the 32-bit compatibility library: glibc-i686 On OpenSuSE, one command that worked for me was yum -y install glibc.i686 Or just use YaST. My experience with RedHat is limited, so I can't offer specific commands. Hope this helps (someone)! Tom

tcurbishley · ‎Dec 10, 2012

The fix is to set the environment variable LD_LIBRARY_PATH to your platform directory. See KB Q112640: INFO: Error: lc_flexinit failed: 131072 and Q200786: Setting up Trusted Storage on Linux and Unix csh: setenv LD_LIBRARY_PATH /my/platform/dir sh, bash: export LD_LIBRARY_PATH=/my/platform/dir

tcurbishley · ‎Dec 07, 2012

I deleted my FlexNet Publisher installation and started from scratch, so all I have now are the files from the distribution. lmflex produces the error "lc_flexinit failed: 2" even for the unserved case. My DEMO_LICENSE_FILE variable is set to the platform directory, and lmdiag sees it okay. To be clear, I am *not* running the license server right now. Below is the output from lmdiag. Has anyone seen this before? FNP_11.11.0.0/x64_lsb> ./lmflex lc_flexinit failed: 2 FNP_11.11.0.0/x64_lsb> ./lmdiag lmdiag - Copyright (c) 1989-2012 Flexera Software LLC. All Rights Reserved. FLEXnet diagnostics on Fri 12/7/2012 11:32 ----------------------------------------------------- License file: /opt/flexera/FNP_11.11.0.0/x64_lsb/counted.lic ----------------------------------------------------- ----------------------------------------------------- License file: /opt/flexera/FNP_11.11.0.0/x64_lsb/expired.lic ----------------------------------------------------- "f4" v1.000, vendor: demo uncounted nodelocked license locked to NOTHING (hostid=ANY) starts: 1-jan-199 0, expires: 01-jan-2001 This license cannot be checked out because: Feature has expired. Feature: f4 Expire date: 01-jan-2001 License path: /opt/flexera/FNP_11.11.0.0/x64_lsb/counted.lic:/opt/flexera/FNP_1 1.11.0.0/x64_lsb/expired.lic:/opt/flexera/FNP_11.11.0.0/x64_lsb/uncounted.lic: FLEXnet Licensing error:-10,32 For further information, refer to the FLEXnet Licensing documentation, available at "www.flexerasoftware.com". ----------------------------------------------------- ----------------------------------------------------- License file: /opt/flexera/FNP_11.11.0.0/x64_lsb/uncounted.lic ----------------------------------------------------- "f2" v1.000, vendor: demo uncounted nodelocked license locked to NOTHING (hostid=ANY) starts: 1-jan-199 0, no expiration date This is the correct node for this node-locked license ----------------------------------------------------- FNP_11.11.0.0/x64_lsb> lmdiag lmdiag: Command not found. FNP_11.11.0.0/x64_lsb> ./lmdiag lmdiag - Copyright (c) 1989-2012 Flexera Software LLC. All Rights Reserved. FLEXnet diagnostics on Fri 12/7/2012 11:32 ----------------------------------------------------- License file: /opt/flexera/FNP_11.11.0.0/x64_lsb/counted.lic ----------------------------------------------------- ----------------------------------------------------- License file: /opt/flexera/FNP_11.11.0.0/x64_lsb/expired.lic ----------------------------------------------------- "f4" v1.000, vendor: demo uncounted nodelocked license locked to NOTHING (hostid=ANY) starts: 1-jan-1990, expires: 01-jan-2001 This license cannot be checked out because: Feature has expired. Feature: f4 Expire date: 01-jan-2001 License path: /opt/flexera/FNP_11.11.0.0/x64_lsb/counted.lic:/opt/flexera/FNP_11.11.0.0/x64_lsb/expired.lic:/opt/flexera/FNP_11.11.0.0/x64_lsb/uncounted.lic: FLEXnet Licensing error:-10,32 For further information, refer to the FLEXnet Licensing documentation, available at "www.flexerasoftware.com". ----------------------------------------------------- ----------------------------------------------------- License file: /opt/flexera/FNP_11.11.0.0/x64_lsb/uncounted.lic ----------------------------------------------------- "f2" v1.000, vendor: demo uncounted nodelocked license locked to NOTHING (hostid=ANY) starts: 1-jan-1990, no expiration date This is the correct node for this node-locked license ----------------------------------------------------- FNP_11.11.0.0/x64_lsb> ls *.lic counted.lic expired.lic uncounted.lic

tcurbishley · ‎Dec 06, 2012

I have installed FlexNet Publisher under openSUSE 11.2 and am running through the demos as per "Getting Started with File-based Licensing". I can start the license server administrator and connect to the web interface just fine. Yet when i try to run lmflex, it fails with: lc_flexinit failed: 2 I've hunted around the web and around this forum, but I haven't located a similar problem. I did find out that err 2 means "Unable to load activation library". What might be wrong?

Online Status	Offline
Date Last Visited	‎Dec 31, 2020 01:23 PM

Re: Building the FNP toolkit on a Cray XC-30

Building the FNP toolkit on a Cray XC-30

Flex-enabling a Windows XP application

Re: Building a vendor daemon for maximum portabili...

Building a vendor daemon for maximum portability: ...

Re: lmadmin install - where to get help

Solved

Additional info

lc_flexinit failed: 2