Controlling a Daemon in a Compiled Program

I'm having one heck of a time trying to find a good way to incorporate daemons into my compiled program. I have an 8 port serial card and I would like to use "Serial.vit" as my template and then rename them "Serial (COM1).vi" however the Name Property Node doesn't work with a compiled program (like it does with VIs). The best way I could find is to change the Front Panel Title to "Serial (COM1).vi" but keep the VI name as Serial (Clone 1).vi and retrieve the reference using this:
Using a VI, you can just change the VI Name Property and use:
Does anyone have any suggestions on a _good_ way to achieve this? 

Hello,
What is your ultimate goal in terms of functionality here?
-Zach
Certified LabVIEW Developer

Similar Messages

  • LV 8 problem with New Report.vi in compiled program

    I'm a novice LV programmer trying to finish my first project.  The project is the automation of an air flow stand using field point for acquisition/control.  Have the code written and everything seems to work fine until I compile.  Specifically, I get an error when I attempt to open an Excel template (XLT) using the New Report.vi included in the report generation add on.  When the compiled executable run I get a message with the header "Error 7 occured at Open VI reference in New Report vi>report2.vi>auto air flow testing.vi .   And then in the body of the message is says:
    Possible reason(s):
    LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux.
    NI-488:  Non-existent board.
    VI Path: C:\builds\auto air flow\My Application\auto air flow 1a.exe\Excel_Open.vi
    Built Application or Shared Library (DLL): Make sure all dynamically loaded VIs were properly included in the build specification for the application or shared libr
    The input to the New Report.vi template connector is C:\Air Flow Data Files\templates\psc.xlt.  Again this works in design so I believe the formatting is correct and the file does exist.
    Why would this work in design environment but not the compiled program?  I recompiled several times and even tried reinstalling the report generation tool kit. Any help or pointers would be greatly appreciated. I will be happy to supply more info if necessary.   thanks. 

    Okay, I found the solution by doing a search here on 'Error 7".  My thanks to those who have posted the solution in the past.  Regards

  • [SOLVED] configure: error: cannot run C compiled programs

    I'm trying to build lib32-libxkbcommon 0.5.0-1 from AUR with makepkg. I already tried installing pacman (setting the default makepkg.conf) and multilib-devel with no luck.
    makepkg messages:
    ==> Making package: lib32-libxkbcommon 0.5.0-1 (Mon May 11 00:17:05 EEST 2015)
    ==> Checking runtime dependencies...
    ==> Checking buildtime dependencies...
    ==> Retrieving sources...
    -> Found libxkbcommon-0.5.0.tar.xz
    ==> Validating source files with sha256sums...
    libxkbcommon-0.5.0.tar.xz ... Passed
    ==> Extracting sources...
    -> Extracting libxkbcommon-0.5.0.tar.xz with bsdtar
    bsdtar: Failed to set default locale
    ==> Starting prepare()...
    ==> Removing existing $pkgdir/ directory...
    ==> Starting build()...
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking whether to enable maintainer-specific portions of Makefiles... yes
    checking for style of include used by make... GNU
    checking for gcc... gcc -m32
    checking whether the C compiler works... yes
    checking for C compiler default output file name... a.out
    checking for suffix of executables...
    checking whether we are cross compiling... configure: error: in `/mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0':
    configure: error: cannot run C compiled programs.
    If you meant to cross compile, use `--host'.
    See `config.log' for more details
    ==> ERROR: A failure occurred in build().
    Aborting...
    makepkg.conf:
    # /etc/makepkg.conf
    # SOURCE ACQUISITION
    #-- The download utilities that makepkg should use to acquire sources
    # Format: 'protocol::agent'
    DLAGENTS=('ftp::/usr/bin/curl -fC - --ftp-pasv --retry 3 --retry-delay 3 -o %o %u'
    'http::/usr/bin/curl -fLC - --retry 3 --retry-delay 3 -o %o %u'
    'https::/usr/bin/curl -fLC - --retry 3 --retry-delay 3 -o %o %u'
    'rsync::/usr/bin/rsync --no-motd -z %u %o'
    'scp::/usr/bin/scp -C %u %o')
    # Other common tools:
    # /usr/bin/snarf
    # /usr/bin/lftpget -c
    # /usr/bin/wget
    #-- The package required by makepkg to download VCS sources
    # Format: 'protocol::package'
    VCSCLIENTS=('bzr::bzr'
    'git::git'
    'hg::mercurial'
    'svn::subversion')
    # ARCHITECTURE, COMPILE FLAGS
    CARCH="x86_64"
    CHOST="x86_64-unknown-linux-gnu"
    #-- Compiler and Linker Flags
    # -march (or -mcpu) builds exclusively for an architecture
    # -mtune optimizes for an architecture, but builds for whole processor family
    CPPFLAGS="-D_FORTIFY_SOURCE=2"
    CFLAGS="-march=core2 -m64 -mfpmath=sse -O2 -fomit-frame-pointer -pipe -fstack-protector --param=ssp-buffer-size=4"
    CXXFLAGS="${CFLAGS}"
    LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro"
    #-- Make Flags: change this for DistCC/SMP systems
    MAKEFLAGS="-j5"
    #-- Debugging flags
    DEBUG_CFLAGS="-g -fvar-tracking-assignments"
    DEBUG_CXXFLAGS="-g -fvar-tracking-assignments"
    # BUILD ENVIRONMENT
    # Defaults: BUILDENV=(!distcc color !ccache check !sign)
    # A negated environment option will do the opposite of the comments below.
    #-- distcc: Use the Distributed C/C++/ObjC compiler
    #-- color: Colorize output messages
    #-- ccache: Use ccache to cache compilation
    #-- check: Run the check() function if present in the PKGBUILD
    #-- sign: Generate PGP signature file
    BUILDENV=(!distcc color !ccache check !sign)
    #-- If using DistCC, your MAKEFLAGS will also need modification. In addition,
    #-- specify a space-delimited list of hosts running in the DistCC cluster.
    #DISTCC_HOSTS=""
    #-- Specify a directory for package building.
    #BUILDDIR=/tmp/makepkg
    # GLOBAL PACKAGE OPTIONS
    # These are default values for the options=() settings
    # Default: OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !upx !debug)
    # A negated option will do the opposite of the comments below.
    #-- strip: Strip symbols from binaries/libraries
    #-- docs: Save doc directories specified by DOC_DIRS
    #-- libtool: Leave libtool (.la) files in packages
    #-- staticlibs: Leave static library (.a) files in packages
    #-- emptydirs: Leave empty directories in packages
    #-- zipman: Compress manual (man and info) pages in MAN_DIRS with gzip
    #-- purge: Remove files specified by PURGE_TARGETS
    #-- upx: Compress binary executable files using UPX
    #-- debug: Add debugging flags as specified in DEBUG_* variables
    OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !upx !debug)
    #-- File integrity checks to use. Valid: md5, sha1, sha256, sha384, sha512
    INTEGRITY_CHECK=(md5)
    #-- Options to be used when stripping binaries. See `man strip' for details.
    STRIP_BINARIES="--strip-all"
    #-- Options to be used when stripping shared libraries. See `man strip' for details.
    STRIP_SHARED="--strip-unneeded"
    #-- Options to be used when stripping static libraries. See `man strip' for details.
    STRIP_STATIC="--strip-debug"
    #-- Manual (man and info) directories to compress (if zipman is specified)
    MAN_DIRS=({usr{,/local}{,/share},opt/*}/{man,info})
    #-- Doc directories to remove (if !docs is specified)
    DOC_DIRS=(usr/{,local/}{,share/}{doc,gtk-doc} opt/*/{doc,gtk-doc})
    #-- Files to be removed from all packages (if purge is specified)
    PURGE_TARGETS=(usr/{,share}/info/dir .packlist *.pod)
    # PACKAGE OUTPUT
    # Default: put built package and cached source in build directory
    #-- Destination: specify a fixed directory where all packages will be placed
    #PKGDEST=/home/packages
    #-- Source cache: specify a fixed directory where source files will be cached
    #SRCDEST=/home/sources
    #-- Source packages: specify a fixed directory where all src packages will be placed
    #SRCPKGDEST=/home/srcpackages
    #-- Log files: specify a fixed directory where all log files will be placed
    #LOGDEST=/home/makepkglogs
    #-- Packager: name/email of the person or organization building packages
    #PACKAGER="John Doe <[email protected]>"
    #-- Specify a key to use for package signing
    #GPGKEY=""
    # COMPRESSION DEFAULTS
    COMPRESSGZ=(gzip -c -f -n)
    COMPRESSBZ2=(bzip2 -c -f)
    COMPRESSXZ=(xz -c -z -)
    COMPRESSLRZ=(lrzip -q)
    COMPRESSLZO=(lzop -q)
    COMPRESSZ=(compress -c -f)
    # EXTENSION DEFAULTS
    # WARNING: Do NOT modify these variables unless you know what you are
    # doing.
    PKGEXT='.pkg.tar.xz'
    SRCEXT='.src.tar.gz'
    # vim: set ft=sh ts=2 sw=2 et:
    config.log:
    This file contains any messages produced by compilers while
    running configure, to aid debugging if configure makes a mistake.
    It was created by libxkbcommon configure 0.5.0, which was
    generated by GNU Autoconf 2.69. Invocation command line was
    $ ./configure --prefix=/usr --libdir=/usr/lib32 --disable-docs --disable-static
    ## Platform. ##
    hostname = Arch
    uname -m = x86_64
    uname -r = 4.0.1-1-ARCH
    uname -s = Linux
    uname -v = #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015
    /usr/bin/uname -p = unknown
    /bin/uname -X = unknown
    /bin/arch = unknown
    /usr/bin/arch -k = unknown
    /usr/convex/getsysinfo = unknown
    /usr/bin/hostinfo = unknown
    /bin/machine = unknown
    /usr/bin/oslevel = unknown
    /bin/universe = unknown
    PATH: /usr/local/sbin
    PATH: /usr/local/bin
    PATH: /usr/bin
    PATH: /usr/lib/jvm/default/bin
    PATH: /usr/bin/site_perl
    PATH: /usr/bin/vendor_perl
    PATH: /usr/bin/core_perl
    ## Core tests. ##
    configure:2424: checking for a BSD-compatible install
    configure:2492: result: /usr/bin/install -c
    configure:2503: checking whether build environment is sane
    configure:2558: result: yes
    configure:2709: checking for a thread-safe mkdir -p
    configure:2748: result: /usr/bin/mkdir -p
    configure:2755: checking for gawk
    configure:2771: found /usr/bin/gawk
    configure:2782: result: gawk
    configure:2793: checking whether make sets $(MAKE)
    configure:2815: result: yes
    configure:2844: checking whether make supports nested variables
    configure:2861: result: yes
    configure:2987: checking whether to enable maintainer-specific portions of Makefiles
    configure:2996: result: yes
    configure:3023: checking for style of include used by make
    configure:3051: result: GNU
    configure:3122: checking for gcc
    configure:3149: result: gcc -m32
    configure:3378: checking for C compiler version
    configure:3387: gcc -m32 --version >&5
    gcc (GCC) 5.1.0
    Copyright (C) 2015 Free Software Foundation, Inc.
    This is free software; see the source for copying conditions. There is NO
    warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
    configure:3398: $? = 0
    configure:3387: gcc -m32 -v >&5
    Using built-in specs.
    COLLECT_GCC=gcc
    COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/5.1.0/lto-wrapper
    Target: x86_64-unknown-linux-gnu
    Configured with: /build/gcc-multilib/src/gcc-5-20150505/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib --disable-werror --enable-checking=release --with-default-libstdcxx-abi=c++98
    Thread model: posix
    gcc version 5.1.0 (GCC)
    configure:3398: $? = 0
    configure:3387: gcc -m32 -V >&5
    gcc: error: unrecognized command line option '-V'
    gcc: fatal error: no input files
    compilation terminated.
    configure:3398: $? = 1
    configure:3387: gcc -m32 -qversion >&5
    gcc: error: unrecognized command line option '-qversion'
    gcc: fatal error: no input files
    compilation terminated.
    configure:3398: $? = 1
    configure:3418: checking whether the C compiler works
    configure:3440: gcc -m32 -march=core2 -m64 -mfpmath=sse -O2 -fomit-frame-pointer -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro conftest.c >&5
    configure:3444: $? = 0
    configure:3492: result: yes
    configure:3495: checking for C compiler default output file name
    configure:3497: result: a.out
    configure:3503: checking for suffix of executables
    configure:3510: gcc -m32 -o conftest -march=core2 -m64 -mfpmath=sse -O2 -fomit-frame-pointer -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro conftest.c >&5
    configure:3514: $? = 0
    configure:3536: result:
    configure:3558: checking whether we are cross compiling
    configure:3566: gcc -m32 -o conftest -march=core2 -m64 -mfpmath=sse -O2 -fomit-frame-pointer -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro conftest.c >&5
    In file included from /usr/include/stdio.h:27:0,
    from conftest.c:11:
    /usr/include/features.h:365:25: fatal error: sys/cdefs.h: No such file or directory
    compilation terminated.
    configure:3570: $? = 1
    configure:3577: ./conftest
    ./configure: line 3579: ./conftest: No such file or directory
    configure:3581: $? = 127
    configure:3588: error: in `/mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0':
    configure:3590: error: cannot run C compiled programs.
    If you meant to cross compile, use `--host'.
    See `config.log' for more details
    ## Cache variables. ##
    ac_cv_env_CC_set=set
    ac_cv_env_CC_value='gcc -m32'
    ac_cv_env_CFLAGS_set=set
    ac_cv_env_CFLAGS_value='-march=core2 -m64 -mfpmath=sse -O2 -fomit-frame-pointer -pipe -fstack-protector --param=ssp-buffer-size=4'
    ac_cv_env_CPPFLAGS_set=set
    ac_cv_env_CPPFLAGS_value=-D_FORTIFY_SOURCE=2
    ac_cv_env_CPP_set=
    ac_cv_env_CPP_value=
    ac_cv_env_DOT_set=
    ac_cv_env_DOT_value=
    ac_cv_env_DOXYGEN_set=
    ac_cv_env_DOXYGEN_value=
    ac_cv_env_LDFLAGS_set=set
    ac_cv_env_LDFLAGS_value=-Wl,-O1,--sort-common,--as-needed,-z,relro
    ac_cv_env_LIBS_set=
    ac_cv_env_LIBS_value=
    ac_cv_env_PKG_CONFIG_LIBDIR_set=
    ac_cv_env_PKG_CONFIG_LIBDIR_value=
    ac_cv_env_PKG_CONFIG_PATH_set=set
    ac_cv_env_PKG_CONFIG_PATH_value=/usr/lib32/pkgconfig
    ac_cv_env_PKG_CONFIG_set=
    ac_cv_env_PKG_CONFIG_value=
    ac_cv_env_XCB_XKB_CFLAGS_set=
    ac_cv_env_XCB_XKB_CFLAGS_value=
    ac_cv_env_XCB_XKB_LIBS_set=
    ac_cv_env_XCB_XKB_LIBS_value=
    ac_cv_env_XORG_MALLOC_DEBUG_ENV_set=
    ac_cv_env_XORG_MALLOC_DEBUG_ENV_value=
    ac_cv_env_YACC_set=
    ac_cv_env_YACC_value=
    ac_cv_env_YFLAGS_set=
    ac_cv_env_YFLAGS_value=
    ac_cv_env_build_alias_set=
    ac_cv_env_build_alias_value=
    ac_cv_env_host_alias_set=
    ac_cv_env_host_alias_value=
    ac_cv_env_target_alias_set=
    ac_cv_env_target_alias_value=
    ac_cv_path_install='/usr/bin/install -c'
    ac_cv_path_mkdir=/usr/bin/mkdir
    ac_cv_prog_AWK=gawk
    ac_cv_prog_ac_ct_CC='gcc -m32'
    ac_cv_prog_make_make_set=yes
    am_cv_make_support_nested_variables=yes
    ## Output variables. ##
    ACLOCAL='${SHELL} /mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0/build-aux/missing aclocal-1.14'
    ADMIN_MAN_DIR=''
    ADMIN_MAN_SUFFIX=''
    AMDEPBACKSLASH='\'
    AMDEP_FALSE='#'
    AMDEP_TRUE=''
    AMTAR='$${TAR-tar}'
    AM_BACKSLASH='\'
    AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)'
    AM_DEFAULT_VERBOSITY='1'
    AM_V='$(V)'
    APP_MAN_DIR=''
    APP_MAN_SUFFIX=''
    AR=''
    AUTOCONF='${SHELL} /mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0/build-aux/missing autoconf'
    AUTOHEADER='${SHELL} /mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0/build-aux/missing autoheader'
    AUTOMAKE='${SHELL} /mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0/build-aux/missing automake-1.14'
    AWK='gawk'
    BASE_CFLAGS=''
    BUILD_LINUX_TESTS_FALSE=''
    BUILD_LINUX_TESTS_TRUE=''
    CC='gcc -m32'
    CCDEPMODE=''
    CFLAGS='-march=core2 -m64 -mfpmath=sse -O2 -fomit-frame-pointer -pipe -fstack-protector --param=ssp-buffer-size=4'
    CHANGELOG_CMD=''
    CPP=''
    CPPFLAGS='-D_FORTIFY_SOURCE=2'
    CWARNFLAGS=''
    CYGPATH_W='echo'
    DEFS=''
    DEPDIR='.deps'
    DLLTOOL=''
    DOT=''
    DOXYGEN=''
    DRIVER_MAN_DIR=''
    DRIVER_MAN_SUFFIX=''
    DSYMUTIL=''
    DUMPBIN=''
    ECHO_C=''
    ECHO_N='-n'
    ECHO_T=''
    EGREP=''
    ENABLE_DOCS_FALSE=''
    ENABLE_DOCS_TRUE=''
    ENABLE_X11_FALSE=''
    ENABLE_X11_TRUE=''
    EXEEXT=''
    FGREP=''
    FILE_MAN_DIR=''
    FILE_MAN_SUFFIX=''
    GREP=''
    HAVE_DOT=''
    HAVE_DOT_FALSE=''
    HAVE_DOT_TRUE=''
    HAVE_DOXYGEN_FALSE=''
    HAVE_DOXYGEN_TRUE=''
    HAVE_NO_UNDEFINED_FALSE=''
    HAVE_NO_UNDEFINED_TRUE=''
    INSTALL_CMD=''
    INSTALL_DATA='${INSTALL} -m 644'
    INSTALL_PROGRAM='${INSTALL}'
    INSTALL_SCRIPT='${INSTALL}'
    INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
    LD=''
    LDFLAGS='-Wl,-O1,--sort-common,--as-needed,-z,relro'
    LIBOBJS=''
    LIBS=''
    LIBTOOL=''
    LIB_MAN_DIR=''
    LIB_MAN_SUFFIX=''
    LIPO=''
    LN_S=''
    LTLIBOBJS=''
    MAINT=''
    MAINTAINER_MODE_FALSE='#'
    MAINTAINER_MODE_TRUE=''
    MAKEINFO='${SHELL} /mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0/build-aux/missing makeinfo'
    MANIFEST_TOOL=''
    MAN_SUBSTS=''
    MISC_MAN_DIR=''
    MISC_MAN_SUFFIX=''
    MKDIR_P='/usr/bin/mkdir -p'
    NM=''
    NMEDIT=''
    OBJDUMP=''
    OBJEXT=''
    OTOOL64=''
    OTOOL=''
    PACKAGE='libxkbcommon'
    PACKAGE_BUGREPORT='https://bugs.freedesktop.org/enter_bug.cgi?product=libxkbcommon'
    PACKAGE_NAME='libxkbcommon'
    PACKAGE_STRING='libxkbcommon 0.5.0'
    PACKAGE_TARNAME='libxkbcommon'
    PACKAGE_URL='http://xkbcommon.org'
    PACKAGE_VERSION='0.5.0'
    PATH_SEPARATOR=':'
    PKG_CONFIG=''
    PKG_CONFIG_LIBDIR=''
    PKG_CONFIG_PATH='/usr/lib32/pkgconfig'
    RANLIB=''
    RT_LIBS=''
    SED=''
    SET_MAKE=''
    SHELL='/bin/sh'
    STRICT_CFLAGS=''
    STRIP=''
    VERSION='0.5.0'
    XCB_XKB_CFLAGS=''
    XCB_XKB_LIBS=''
    XKBCONFIGROOT=''
    XLOCALEDIR=''
    XORG_MALLOC_DEBUG_ENV=''
    XORG_MAN_PAGE=''
    YACC=''
    YACC_INST=''
    YFLAGS=''
    ac_ct_AR=''
    ac_ct_CC='gcc -m32'
    ac_ct_DUMPBIN=''
    am__EXEEXT_FALSE=''
    am__EXEEXT_TRUE=''
    am__fastdepCC_FALSE=''
    am__fastdepCC_TRUE=''
    am__include='include'
    am__isrc=''
    am__leading_dot='.'
    am__nodep='_no'
    am__quote=''
    am__tar='$${TAR-tar} chof - "$$tardir"'
    am__untar='$${TAR-tar} xf -'
    bindir='${exec_prefix}/bin'
    build=''
    build_alias=''
    build_cpu=''
    build_os=''
    build_vendor=''
    datadir='${datarootdir}'
    datarootdir='${prefix}/share'
    docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
    dvidir='${docdir}'
    exec_prefix='NONE'
    host=''
    host_alias=''
    host_cpu=''
    host_os=''
    host_vendor=''
    htmldir='${docdir}'
    includedir='${prefix}/include'
    infodir='${datarootdir}/info'
    install_sh='${SHELL} /mnt/tmp/yaourt-tmp-tsester/aur-lib32-libxkbcommon/src/libxkbcommon-0.5.0/build-aux/install-sh'
    libdir='/usr/lib32'
    libexecdir='${exec_prefix}/libexec'
    localedir='${datarootdir}/locale'
    localstatedir='${prefix}/var'
    mandir='${datarootdir}/man'
    mkdir_p='$(MKDIR_P)'
    oldincludedir='/usr/include'
    pdfdir='${docdir}'
    prefix='/usr'
    program_transform_name='s,x,x,'
    psdir='${docdir}'
    sbindir='${exec_prefix}/sbin'
    sharedstatedir='${prefix}/com'
    sysconfdir='${prefix}/etc'
    target_alias=''
    ## confdefs.h. ##
    /* confdefs.h */
    #define PACKAGE_NAME "libxkbcommon"
    #define PACKAGE_TARNAME "libxkbcommon"
    #define PACKAGE_VERSION "0.5.0"
    #define PACKAGE_STRING "libxkbcommon 0.5.0"
    #define PACKAGE_BUGREPORT "[url]https://bugs.freedesktop.org/enter_bug.cgi?product=libxkbcommon[/url]"
    #define PACKAGE_URL "[url]http://xkbcommon.org[/url]"
    #define PACKAGE "libxkbcommon"
    #define VERSION "0.5.0"
    configure: exit 1
    other info:
    core/pacman 4.2.1-1
    multilib/gcc-multilib 4.9.2-4 (multilib-devel) [installed]
        The GNU Compiler Collection - C and C++ frontends for multilib
    multilib/lib32-fakeroot 1.20.2-1 (multilib-devel) [installed]
        Tool for simulating superuser privileges (32-bit)
    multilib/lib32-libltdl 2.4.5-1 (multilib-devel) [installed]
        A generic library support script (32-bit)
    Last edited by tsester (2015-05-10 22:10:28)

    tsester wrote:P.S.: I recently transfered the linux system between failing disks
    In that case you should probably check that no other packages are missing files with
    pacman -Qkk 2>&1 | grep "No such file or directory"
    Any packages that report that they're missing files, you should reinstall.

  • Storing integers in a compiled program

    I would am wriitng a program and I would like to generate a unique number for each time a users uses the compiled program, is it possible to store previously incremented numbers i.e. the last person who used this program got a print out number of 5. The next person to use this program would then get the number 6 etc etc? At the moment I have only been made familiar to coding in Java in a sort of runtime environment only.
    An example of my thinking could be like so:
    private int mynumber=1;
    I woould then like to be able to set a new number most probably by creating a set method like so:
    public int setMyNumber(int mynumber){
    mynewnumber = mynumber+1;
    return mynewnumber;
    ...... then in my main method I would like to return this new number. Please note this may not actually work but just giving you an idea of my thinking.
    : )

    Kayaman wrote:
    cyber_frog wrote:
    Hi EJP,
    Not sure what you mean by a preference? Do you have any info?See the Preferences class.Additional > [url http://download.oracle.com/javase/6/docs/api/]API Doco
    Additional > [url http://download.oracle.com/javase/1.4.2/docs/guide/lang/preferences.html]Tutorial 

  • How do I rid the User Account Control - "Do you want the following program to make changes to this computer?" - FireFox Helper pop-up that shows after every log in?

    The following pop-up is displayed after every log-in, even after it is clicked yes after previous log-ins. Several students log-in the computers daily. How do I rid THIS?:
    User Account Control
    "Do you want the following program to make changes to this computer?
    Program Name: FireFox Helper
    Verified Publisher: Mozilla Corporation
    File Origin: Hard Drive on this Computer

    In Windows 7, Microsoft updated UAC in several ways. By default, UAC does not prompt when certain programs included with Windows make changes requiring elevated permissions. Other programs still trigger a UAC prompt. The strictness of UAC can be changed to either always prompt, or to never do so.
    [http://windows.microsoft.com/eN-US/windows-vista/What-is-User-Account-Control What is User Account Control?]
    [http://windows.microsoft.com/en-US/windows-vista/Turn-User-Account-Control-on-or-off Turn User Account Control on or off]
    It is the same on win7.
    [http://en.wikipedia.org/wiki/User_Account_Control User Account Control]
    thank you
    Please mark "Solved" the answer that really solve the problem, to help others with a similar problem.

  • Do I have control over "USE flags" when compile from source

    I have  used Gentoo and like it's system specific customizations, but am looking for something a slight bit easier to maintain.  I noticed that Arch also compiles as part of the installation.  Do I have control over the system wide compile setting in order to customize the builds similar to what is done is Gentoo?  Or, is the pacman process a "one size fits all" installer without customizations, for such things as architecture, with or without certain extensions...
    Thanks for your info.  This looks like the distro for me, but am researching first.

    It's a one-size-fits-all approach for the official binary repos and many weird and wonderful things can be found in the AUR or unofficial user repos. You can also use ABS to alter the configuration yourself, but you would have to edit PKGBUILDs for every package you want to change (e.g. add '--enable-foo') as Arch doesn't use the USE flags.
    Official Arch packages support only i686 and generic 64-bit architectures, but e.g. linux -ck kernel https://bbs.archlinux.org/viewtopic.php?id=111715 is provided optimized for many specific processors.

  • Configure: error: cannot run C compiled programs.

    Hi,
    I am new to Solaris. I have installed Solaris 10 and compiled packages without any error.
    I have tried to compile Wireshark 1.7.1 and it was exist indicating '/usr/include/sys/feature_tests.h no such file or directory'.
    So I have download feature_tests.h file and uploaded it to the relevant location and run ./configure again.
    Now I am not able to compile any package and it indicate error
    'configure: error: cannot run C compiled programs.
    If you meant to cross compile, use `--host'.
    See `config.log' for more details'
    I have attached portion of the config.log
    configure:3739: checking whether the C compiler works
    configure:3761: gcc conftest.c >&5
    configure:3765: $? = 0
    configure:3813: result: yes
    configure:3816: checking for C compiler default output file name
    configure:3818: result: a.out
    configure:3824: checking for suffix of executables
    configure:3831: gcc -o conftest conftest.c >&5
    configure:3835: $? = 0
    configure:3857: result:
    configure:3879: checking whether we are cross compiling
    configure:3887: gcc -o conftest conftest.c >&5
    In file included from conftest.c:11:
    /usr/include/stdio.h:21:31: sys/feature_tests.h: No such file or directory
    In file included from /usr/include/stdio.h:66,
    from conftest.c:11:
    /usr/include/iso/stdio_iso.h:90: error: syntax error before "fpos_t"
    /usr/include/iso/stdio_iso.h:208: error: syntax error before "fpos_t"
    /usr/include/iso/stdio_iso.h:210: error: syntax error before '*' token
    In file included from /usr/include/stdio.h:135,
    from conftest.c:11:
    /usr/include/iso/stdio_c99.h:54: error: conflicting types for '_RESTRICT_KYWD'
    /usr/include/iso/stdio_c99.h:54: error: previous definition of '_RESTRICT_KYWD' was here
    /usr/include/iso/stdio_c99.h:56: error: redefinition of parameter '_RESTRICT_KYWD'
    /usr/include/iso/stdio_c99.h:56: error: previous definition of '_RESTRICT_KYWD' was here
    /usr/include/iso/stdio_c99.h:68: error: conflicting types for '_RESTRICT_KYWD'
    /usr/include/iso/stdio_c99.h:68: error: previous definition of '_RESTRICT_KYWD' was here
    /usr/include/iso/stdio_c99.h:70: error: conflicting types for '_RESTRICT_KYWD'
    /usr/include/iso/stdio_c99.h:70: error: previous definition of '_RESTRICT_KYWD' was here
    configure:3891: $? = 1
    configure:3898: ./conftest
    ./configure: line 3900: ./conftest: No such file or directory
    configure:3902: $? = 127
    configure:3909: error: in `/wireshark-1.6.7':
    configure:3911: error: cannot run C compiled programs.
    If you meant to cross compile, use `--host'.
    See `config.log' for more details

    934802 wrote:
    Hi,
    I am new to Solaris. I have installed Solaris 10 and compiled packages without any error.
    I have tried to compile Wireshark 1.7.1 and it was exist indicating '/usr/include/sys/feature_tests.h no such file or directory'.
    So I have download feature_tests.h file and uploaded it to the relevant location and run ./configure again.
    Now I am not able to compile any package and it indicate error Where did you get this file?

  • Execution of one CLASS file ( a compiled program)

    this is a ambiguse problem for me !!!!
    i working with jsdk1.4.1 .
    i can compile programs but can't perform them with "java" !!
    this is error of it :
    (( Exception in thread "main" java.lang.NoclassDefFoundError : file name ))
    anyone can lead & help me !!!
    Thank you for your responses .
    F.Heidary

    Set your classpath.

  • Compiling programs in different directories (packages)

    I'm studying Java from the book, Java: A Beginner's Guide Fourth Edition. I've come across a hurdle regarding compiling programs where classes are called from other files (packages). I can compile without error a file that doesn't include 'main()' which resides in it's own directory, "BookPack". I can't compile the second file which contains the 'main()' function. This file residing in another directory by the same name as it's package, "BookPackB". The error reported is "..... package BookPack.Book(..." does not exist.
    For completeness here are the two files (page 308 from the book).
    // Book recoded for public access.
    package BookPack;
    public class Book {
      private String title;
      private String author;
      private int pubDate;
      // Now public.
      public Book(String t, String a, int d) {
        title = t;
        author = a;
        pubDate = d;
      // Now, public.
      public void show() {
        System.out.println(title);
        System.out.println(author);
        System.out.println(pubDate);
        System.out.println();
    }and
    // This class is in package BookPackB
    package BookPackB;
    // Use the Book Class from BookPack.
    class UseBook {
      public static void main(String args[]) {
        BookPack.Book books[] = new BookPack.Book[5];
        books[0] = new BookPack.Book("Java: A Beginner's Guide", "Schildt", 2007);
        books[1] = new BookPack.Book("Java: The Complete Reference", "Schildt", 2007);
        books[2] = new BookPack.Book("The Art of Java", "Schildt and Holmes", 2003);
        books[3] = new BookPack.Book("Red Storm Rising", "Clancy", 1986);
        books[4] = new BookPack.Book("On the Road", "Kerouac", 1955);
        for(int i=0; i<books.length; i++) books.show();
    I would appreciate some simple guidance in the steps to compile the above files.
    Cheers,
    Steve.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    superjacent wrote:
    My base direcory is "Module-08" and I have two sub-directories, "BookPack" and "BookPackA".
    The first file with the class Book resides in the BookPack directory and the other file containing 'main()' resides in the BookPackA directory.Which ones? The .java files? or the .class files?
    There are two possible ways to compile such structures: Have the .class files be next to the .java files (that's the easier one) or have a parallel directory structure for the .class files that mirrors the source structure (that's the nicer one but a tiny bit harder to set up).
    I'll describe the first one here.
    Your goal is for your directories + content to be like this:
    Module-08/BookPack/Book.java
    Module-08/BookPack/Book.class
    Module-08/BookPackB/UseBook.java
    Module-08/BookPackB/UseBook.class
    1.) Go to Module-08
    2.) compile Book.java using this command:
    javac -cp . BookPack/Book.java3.) compile UseBook.java using this command:
    javac -cp . BookPackB/UseBook.javaThe "-cp ." means "Use the current directory as the Classpath".
    Note that your package names should be lower-case, that's a convention and it would be better to follow it.

  • How to make the LV front panel controls the current value through the program is set as the default value when the next time you open?

    How to make the LV front panel controls the current value through the programis set as the default value when the next time you open?
    1110340051 

    Try this: Re: How to make a VI remember the latest control value?
    Jim
    You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice

  • Problem with a compiled program

    Hello,
    I have a problem with a compiled program on labview 6i.
    This program used a serial port (COM1 or COM2).
    During the launching of the ".exe ", a fatal error occurs.
    Here this error:
    => APPLICATION caused an invalid page fault in
    => module LVRT.DLL at 0167:30164426.
    Can somebody help me?
    Regards
    Cedric

    Cedric,
    This problem was fixed in the LabVIEW 6.0.2 update. You can download this update (along with the updated runtime engine) from our website.
    Good luck with your application, and have a pleasant day.
    Sincerely,
    Darren N.
    NI Applications Engineer
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Compiling programs using jdk1.6.0

    when i compiled program using "system.out.print.in " , it shows an error
    that package system does not exist .

    if you want to print something use
    System.out.printor if you want to make it print on seperate lines
    System.out.println

  • Can I run gcc compiled programs in the terminal?

    I compiled a simple C program in the terminal using gcc 4.0 from the Xcode 2.2 distribution. I used gcc a.c at the command line and the compiler produced a.out. When I type a.out at the command line, I get the message
    tcsh: a.out: Command not found.
    Am I missing a step in the comilation phase? Is it possible to run gcc compiled programs in the terminal? I get the same results in the bash shell and when using X11.
    eMac G4   Mac OS X (10.4.6)  

    ./a.out is correct. Your current directory in not in your $PATH. You could add "." to the PATH, but that is considered a security compromise, because an unexpected command could be introduced either maliciously or inadvertently. (I have seen this happen.)

  • My compiled program crashes after first run (LabVIEW 2009)

    I have a compiled program created with LabVIEW 2009 that on the first run after the computer is re-booted will work fine but after shutting down the program it will not run properly. 
    The program uses a compiled launcher to dynamically activate a set of VI's containing Queue Driven State Machines (QDSM).  On subsequent program starts the launcher module comes up fine and its progress bar shows that it is launching each of the VI's.  Once the launcher is complete it removes itself from memory leaving the dynamically launched VI's running.  The subsequent launches which fail the main user interface VI pops up barely long enough for the observer to see (if at all) then shuts down.  The program is then gone from memory as far as I can tell.  There are no processes in memory or anything.
    Additionally, the when I try to run the installed version of the exe on a computer that has the 2009 development environment installed I get this behavior consistently with a successful run even once.
    In both cases my program does not throw any errors (which are logged) nor does the runtime engine generate any that I can see.  Also, when I run my program in the development environment the program does not behave this way.  It has no problems at all.
    I have used this style of architecture before in LV8.6 with out any problems.  Can anyone suggest some possible solutions or even some debugging tips?  I have never had a problem that I could not duplicate in the development environment so I am unsure how begin attacking my issue.
    Thanks for any help.
    Jason
    Wire Warrior
    Behold the power of LabVIEW as my army of Roomba minions streaks across the floor!
    Solved!
    Go to Solution.

    I have solved the problem I think (at least as far as testing to this point has revealed).   After I added in the ability to log the states passed to the QDSM's, I was able to determine that the program was "crashing" after I dynamically closed the front panel of the launcher.  My program was designed to close the front panel of the launcher then pop-up the front panel of the main UI.   My EXE is built on to contain the launcher with my other QDSM files being maintained externally in specific directories.  What appeared to be happening is that when the launcher closed its front panel and before the UI opened up the run-time engine would decide since there were no windows open it would close itself down.  This is my supposition about what may be happening any way.  I modified my code to changed the launcher window to hidden and delay for 1/2 a second to give the main UI a chance to start fully running.  This fixed the problem, or at least worked around it.  If someone out there can explain to me exactly what is happening I sure would appreciate it.
    Thanks for all the help those of you who responded.  Your advice was very beneficial and certainly led me to a resolution faster.
    Jason
    Wire Warrior
    Behold the power of LabVIEW as my army of Roomba minions streaks across the floor!

  • Control & Simulation Loop failed to compile

    Dear Forum Members,
    I have a problem with a Control & Simulation Loop program (attached) that just doesn't compile & run.  I believe that the problem is associated with the 'Feedback Node' at the bottom of this Control & Simulation Frame since if this is taken out the program will run ok.
    Can anyone please advise me if this 'Feedback Node' is incorrectly used or in violation of anything.  I have tried various ways to overcome the problem i.e. initialising it at the start but nothing works.  The error message that I received just says "VI failed to compile".
    Appreciate any help with this.

    Hello bunnykins, 
    The Feedback node really isn't a supported function in control design and simulation. The behavior you're reporting, and the work around are both documented in the know issues of the module here: 
    201449
    Return
    A Feedback Node on a Simulation Diagram causes the VI to fail to compile
    The Feedback Node does not make sense semantically within a Simulation Diagram, due to the fact that most ODE Solvers will execute the diagram multiple times per iteration and may need to reject steps and try again, filling the Feedback Node with bad data.
    Workaround: Use the Memory block from the Simulation Utility palette. If a delay of greater than 1 is desired you can chain multiple memory blocks in sequence.
    Reported Version: 8.5
    Resolved Version: N/A
    Added: 07/31/2010
    Applications Engineer
    National Instruments
    CLD Certified

Maybe you are looking for