InvokeReferenceNode and compile problem

Hi!
I have created a LV5.1.1 application that uses the
InvokeReferenceNode to call a few sub-VIs (the
reason I am doing it that way is that I can then
access that VIs property node from the calling VI
and change things like title bar etc).
Now I would like to compile my app using
ApplicationBuilder, but how do I get access to the
VIs in the compiled version? I noticed that there is
a "dynamic VIs" setting in application builder but
even if I add the VIs I can't seem to load them.
I tried
* supplying the full *source* path
* supplying the VI name only
Neither works. Instead I get an error 4001 (not
documented). I assume the issue is that in the
former case the VI is somewhere else (surprise)
and in the latter case it
is not in memory ...
anyone got this working?
Rudolf

Hi Rudolf,
The path to VI's in a built application is defferent than in the development environment.
First, include the dymanically called VI as a "Dynamic" in the app buildler.
If the VI you want to invoke is in the same folder as the VI calling it, you can take the path of the calling VI, Strip it once, at that will give you the path to the folder where the dynamic VI is.
In the built app, you have to strip the path twice.
There are a number of ways of determining which method to use, when.
If the app is running in the dev environ., the file extension will be ".VI".
In the built it will be ".exe".
There are other methods you could use, this is just one.
I hope this helps,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Similar Messages

  • Makepkg.conf and compilation problem

    Hi!
    In my makepkg.conf I have:
    CARCH="x86_64"
    CHOST="x86_64-unknown-linux-gnu"
    #-- Exclusive: will only run on -march=x86-64
    # -march (or -mcpu) builds exclusively for an architecture
    # -mtune optimizes for an architecture, but builds for whole processor family
    CFLAGS="-march=amdfam10 -O2 -pipe" #Arch wiki says this
    CXXFLAGS="${CFLAGS}"
    #-- Make Flags: change this for DistCC/SMP systems
    MAKEFLAGS="-j5"
    and when I try to makepkg for smting (for example arora) I get:
    g++ -c -m64 -pipe -march=x86-64 -mtune=generic -O2...
    My gcc is 4.3.3. AMD Phenom II x4 910 processor.
    Why is this two -march are different?

    It's the only one package. And it fails to build every time on different files with the same error. And if I just enter ./src/arora-build and run qmake && make it does compile ok.
    The error example:
    .obj/moc_settings.o: file not recognized: File truncated                                         
    collect2: ld returned 1 exit status
    P.S. PKGBUILD is community/arora-git
    Last edited by vit (2009-05-06 18:02:36)

  • Compiling and running problems

    Dear Friends:
    I believe I encountered a very difficult situation when I try to run Fortran
    files in Sun Sparc Solaris 8.0.
    I would like to describe it, hopefully someone can give me some suggestions.
    The the files I try to run is fortran 77 files developed originally for VAX
    machine, later on there are Linux and Unix adaptions (but not for Sun
    Solaris). The source code is open source from the link:
    http://www.webmo.net/support/mopac_linux.html. I have compiled and run
    successfully in Redhat 9.0 (means same results as the samples). The linux
    dependency is gcc (or egcs) glibc (or libc) f2c.
    Also it is compatible with SGI IRIX unix system with the dependency MIPSpro Fortran 77 and MIPSpro C as the link http://www.webmo.net/support/mopac_sgi.html. I havenot tried it yet.
    In sun solaris, I have tried g77, but even cannot compiled. With Apogee's
    F77 (www.apogee.com), it can be compiled, but cannot run completely (terminate in the middle
    process, i.e. without the complete output as the samples).
    Could anyone take a time do a analysis and provide me any suggestions?
    thanks a lot,
    Justin

    Justin,
    I downloaded the mopac tarball and compiled it on Sun Solaris using the Sun Studio 10 compiler. The code compiles successfully with only a small change to the included Makefile.
    Change the original unix target as follows:
    unix:
         f77 -w -O -static *.f -o $(EXE)
    becomes
    unix:
         f90 -f77 -w -O *.f -o $(EXE)
    I noticed during the compilation that there were a number of BLAS and LAPACK routines that are being compiled into the application. The Sun Studio compilers include a high performance BLAS/LAPACK library called the Sun Performance Library which provides highly tuned versions of the BLAS/LAPACK routines called by this application. I would be more than happy to help you modify the source and makefile so that you can use these tuned routines and realize increased performance in this application.
    I ran several of the data sets in the examples directory and they appeared to complete successfully. Since none of them run for more than a second or so, it's hard to say whether or not the tuned Performance Library will have a large impact on the performance or not.
    If you are interested, please contact me : [email protected]

  • Re: [iPlanet-JATO] sp3 jsp compiler problem

    Weiguo,
    First, Matt is correct, the regular expression tool is perfect for general text
    substitution situations, and as a completely independent tool its use is not
    restricted to migration situations (or file types for that matter).
    Second, I sympathize with the unfortunate trouble you are experiencing due to
    Jasper's (perhaps more strict) compilation, but in what way did the iMT
    automated translation contribute to these inconsistencies that you cited?
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    The iMT does not generate any OnClick or onClick clauses per se. In a
    translation situation, the only way "OnClick" would have been introduced was if
    it had been part of the pre-existing project's "extraHTML" (which was written
    by the original customer and just passed through unchanged by the iMT) or if it
    was added manually by the post-migration developer.
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be
    similar to the OnClick situation described above?
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    Again, the content tag would never have been generated by the iMT. There was no
    equivalent in the NetDynamics world, so any content tags in your code must have
    been introduced by your developers manually. Its a shame that jasper is so
    particular, but the iMT could not help you out here even if we wanted to. The
    constants that are used by the iMT are defined in
    com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can see, the
    only situation of a closing tag with any space in it is
    public static final String CLOSE_EMPTY_ELEMENT = " />";
    But that should not cause the type of problem you are referring to.
    Mike
    ----- Original Message -----
    From: Matthew Stevens
    Sent: Thursday, September 06, 2001 10:16 AM
    Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
    Weiguo,
    Others will chime in for sure...I would highly recommend the Regex Tool from
    the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
    posted to the group (even recently) on directions and advantages of creating
    your own RULES (rules file) in XML for arbitary batch processing of source.
    matt
    -----Original Message-----
    From: weiguo.wang@b...
    [mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174144234026000079108238073194105057099246073154180137239239223019162">weiguo.wang@b...</a>]
    Sent: Thursday, September 06, 2001 12:25 PM
    Subject: [iPlanet-JATO] sp3 jsp compiler problem
    Matt/Mike/Todd,
    We are trying to migrate to sp3 right now, but have had a lot of
    issues with the new jasper compiler.
    The following workaround has been employed to solve the issues:
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    As I see it, we have two options to go about solving this problem:
    1. Write a script which will iterate through all the jsp files and
    call jspc on them. Fix the errors manually when jspc fails. Jspc will
    flag the line number where an error occurs.
    2. Write a utility which scans the jsp files and fix the errors when
    they are encountered. We should define what's an error and how to
    correct it. It's best if we combine this with solution 1 since we
    might miss an error condition.
    Actually, there might be another option, which is seeking help from
    you guys since you have better understanding of JATO and iAS. Can you
    do anything to help us?
    We would be happy to hear your thoughts.
    At last, I would like to suggest modifying the moko tool so that
    these rules are enforced and the generated JSPs work with the new
    compiler. This is for the benefit of any new migration projects.
    Thanks a lot.
    Weiguo
    [email protected]
    Choose from 1000s of job listings!
    [email protected]
    [Non-text portions of this message have been removed]

    Thanks a lot Matt and Mike for your prompt replies.
    I agree completely that iMT doesn't introduce the inconsistencies.
    About the three cases I mentioned, the third one happens only in
    manually created JSPs. So it has nothing to do with iMT. The first
    two are mainly due to the existing HTML code, as you rightly pointed
    out.
    The reason I made the suggestion is since we know that case 1 and 2
    won't pass the japser compiler in sp3, we have to do something about
    it. The best place to do this, in my mind, is iMT. Of course, there
    might be some twists that make it impossible or difficult to do this
    kind of case manipulation or attribute discard.
    Weiguo
    --- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
    Weiguo,
    First, Matt is correct, the regular expression tool is perfect for general text substitution situations, and as a completely independent
    tool its use is not restricted to migration situations (or file types
    for that matter).
    >
    Second, I sympathize with the unfortunate trouble you are experiencing due to Jasper's (perhaps more strict) compilation, but
    in what way did the iMT automated translation contribute to these
    inconsistencies that you cited?
    >
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    The iMT does not generate any OnClick or onClick clauses per se. In a translation situation, the only way "OnClick" would have been
    introduced was if it had been part of the pre-existing
    project's "extraHTML" (which was written by the original customer and
    just passed through unchanged by the iMT) or if it was added manually
    by the post-migration developer.
    >
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be similar to the OnClick situation described above?
    >
    >
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    Again, the content tag would never have been generated by the iMT. There was no equivalent in the NetDynamics world, so any content tags
    in your code must have been introduced by your developers manually.
    Its a shame that jasper is so particular, but the iMT could not help
    you out here even if we wanted to. The constants that are used by the
    iMT are defined in
    com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can
    see, the only situation of a closing tag with any space in it is
    public static final String CLOSE_EMPTY_ELEMENT = " />";
    But that should not cause the type of problem you are referring to.
    Mike
    ----- Original Message -----
    From: Matthew Stevens
    Sent: Thursday, September 06, 2001 10:16 AM
    Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
    Weiguo,
    Others will chime in for sure...I would highly recommend the Regex Tool from
    the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
    posted to the group (even recently) on directions and advantages of creating
    your own RULES (rules file) in XML for arbitary batch processing of source.
    >
    matt
    -----Original Message-----
    From: weiguo.wang@b...
    [mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174048139046">weiguo.wang@b...</a>]
    Sent: Thursday, September 06, 2001 12:25 PM
    Subject: [iPlanet-JATO] sp3 jsp compiler problem
    Matt/Mike/Todd,
    We are trying to migrate to sp3 right now, but have had a lot of
    issues with the new jasper compiler.
    The following workaround has been employed to solve the issues:
    1. Changed the case of the tag attribute to be the same as
    what's
    defined in tld.
    example: changed OnClick to onClick
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    As I see it, we have two options to go about solving this problem:
    >>
    1. Write a script which will iterate through all the jsp files and
    call jspc on them. Fix the errors manually when jspc fails. Jspc will
    flag the line number where an error occurs.
    2. Write a utility which scans the jsp files and fix the errors when
    they are encountered. We should define what's an error and how to
    correct it. It's best if we combine this with solution 1 since we
    might miss an error condition.
    Actually, there might be another option, which is seeking help from
    you guys since you have better understanding of JATO and iAS. Can you
    do anything to help us?
    We would be happy to hear your thoughts.
    At last, I would like to suggest modifying the moko tool so that
    these rules are enforced and the generated JSPs work with the new
    compiler. This is for the benefit of any new migration projects.
    Thanks a lot.
    Weiguo
    [email protected]
    Choose from 1000s of job listings!
    [email protected]
    Service.
    >
    >
    >
    [Non-text portions of this message have been removed]

  • Servlet Compilation Problem !

    Hi,
    I am just starting to learn servlets and I got problem in compiling them. I got compilation error in
    import javax.servlet.*;statement. Seems that the compiler cannot find the servlet package. I got J2EE 1.4 beta installed on my machine but there is no servlet.jar package. I am using J2SDK 1.4.1_02, J2EE 1.4 beta and Tomcat 4.1.24.
    Can anyone help me with my servlet compilation problem?
    Thanks in advance!
    Josh

    servlet.jar is here :
    <tomcatdir>\common\lib
    add it to your compiler classpath

  • Compilation problem in a JSP page

    Hi all,
    I'm trying to write a jsp page and some java stuff in it.
    It goes something like this -
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
    "http://www.w3.org/TR/html4/loose.dtd">
    <%@ page contentType="text/html;charset=windows-1255"%>
    <html>
      <head>
        <meta http-equiv="Content-Type" content="text/html; charset=windows-1255"/>
        <title>Michael</title>
      </head>
      <body>
    <%
              String strError="";
    %>
    </body>Now the problem is that I get compilation problem about the use in java -
    "String cannot be resolved to a type"
    I know for sure that in other computers it's work, the question is what I'm missing?
    I have Java VM installed and I've downloaded and installed the latest JDK, what else?
    thanks,
    Michael.

    Michael4488 wrote:
    BalusC wrote:
    Then you should be using JSTL/EL.I don't familiar with this technology, any way - Its work on one computer so in my understanding it should work on the other as well.It is not related to the actual problem. It was just a comment on your code. Using scriptlets is considered as bad practice.
    I understand that of course, but I don't use any configuration file or set any special parameters in my computer.
    What exactly does the compiler need in order to recognize the Java code in the JSP page? If i manually add the JAVA_HOME environment variable it will work?
    where should I refer it to? "..\Java\jre1.6.0_07\lib" will do?It must point to the root installation directory of the JDK (thus not the JRE!).

  • Compilation problem in PXIe-7695R FlexRIO

    Hello,
    I am new to LabVIEW FPGA, before this, i used to do FPGA's in VHDL using ISE suite. In that process, I just need to change the bit files from iMPACT and my FPGA runs with the new bit file. but I am trying to do the same thing here and facing problem as described below;
    So i've created two projects, both with different names and in different locations. Both of the projects are nearly similar (simple DMA FIFO), except the "maximum number of elements" (of DMA FIFO) is different (one contatains 1023 and other contains 4096). Now i am compiling the first project (with 1023), it gives me a bit file and runs on the FlexRIO.
    Now i've compiled the second project (with 4096), got its bit file and runs on FlexRIO.
    Both of the bit files are located in different locations. Now at this point, when i open my first project, it again asks me to compile. why is that so ? for rechecking, I reloaded my FPGA target with that specific bit file, but still i need to compile. Am i doing some sort of mistake here ?
    please help, as this hurdle waste allot of time of mine in compiling again and again.

    Hi Sheraz,
    When you open the reference to the FPGA code using Open FPGA VI Reference.vi, do you have it configured to reference the VI or the bitfile?
    If you have it configured to reference the VI, I'd suggest changing the configuration to reference the bitfile instead. 
    If you're not familiar with how to do this, more information is available the FPGA Module Help under the Configure Open FPGA VI Reference Dialog Box topic.
    If this doesn't work, or you're already doing this, please let us know and we'll continue to troubleshoot as necessary.
    Thanks and regards,
    Dave C.
    Applications Engineer
    National Instruments

  • Compilation problem in Forms 10g

    Currently we are upgrading from 6i to 10g forms
    we have 2 forms which we will complie partially in 10g and the form gets closed as a corrupted file.
    The same form when complied in 6i works fine.
    What can be the possible problem.
    Please help
    Thanks
    Yaaminy
    480-262-7881

    hi
    create a batch file of the following commands and compile them i hope it helps u.
    @ECHO OFF
    cls
    Echo compiling libraries 10g ....
    for %%f IN (*.pll) do frmcmp userid=User_name/pass@orcl module=%%f batch=yes module_type=library compile_all=yes window_state=minimize
    ECHO libraries compilation complete
    ECHO ----------------------------------
    Echo compiling menus 10g ....
    for %%f IN (*.mmb) do frmcmp userid=User_name/pass@orcl module=%%f batch=yes module_type=menu compile_all=yes window_state=minimize
    ECHO menus compilation complete
    ECHO ----------------------------------
    Echo compiling forms 10g ....
    for %%f IN (*.fmb) do frmcmp userid=User_name/pass@orcl module=%%f batch=yes module_type=form compile_all=yes window_state=minimize
    ECHO form compilation complete
    ECHO ----------------------------------
    ECHO Form Compilation completesarah

  • Compilation problem on solaris9  x86

    I am working on JAVA/J2EE . Am new to solaris9 . My requirement is to compile a source distribution of MOD-JK 1.2.21 (apache 2.0 server connector)and to produce binary distribution (*.so file) in solaris9 X86 box. But i got only source distribution of solaris10 X86 platform . Even with this source i tried to compile in solaris9 box its giving some error message and i can't able to make a executable file. Below i pasted the error message .
    # ./configure -with-apxs=/usr/apache2/bin/apxs
    checking build system type... i386-pc-solaris2.10
    checking host system type... i386-pc-solaris2.10
    checking target system type... i386-pc-solaris2.10
    checking for a BSD-compatible install... scripts/build/unix/install-sh -c
    checking whether build environment is sane... yes
    checking for gawk... no
    checking for mawk... no
    checking for nawk... nawk
    checking whether make sets $(MAKE)... no
    checking for gcc... no
    checking for cc... cc
    checking for C compiler default output file name... configure: error: C compiler cannot create executables
    See `config.log' for more details.
    Can any body help me in this regards. Even i don't know, am proceeding in right direction to compile this file. If any body having the binary distribution for the same MOD-JK1.2.21 on solaris9 or solaris10 X86 platform for apache2.0 . please help me to compile this file .I given below the config.log file entries also.
    Thanks in advance..........
    karthikeyan.u
    [email protected]
    AIM or AOL :: karthikeyanu
    CONFIG.log entries......
    This file contains any messages produced by compilers while
    running configure, to aid debugging if configure makes a mistake.
    It was created by configure, which was
    generated by GNU Autoconf 2.59. Invocation command line was
    $ ./configure -with-apxs=/usr/apache2/bin/apxs
    ## Platform. ##
    hostname = Solaris
    uname -m = i86pc
    uname -r = 5.10
    uname -s = SunOS
    uname -v = Generic_118844-26
    /usr/bin/uname -p = i386
    /bin/uname -X = System = SunOS
    Node = Solaris
    Release = 5.10
    KernelID = Generic_118844-26
    Machine = i86pc
    BusType = <unknown>
    Serial = <unknown>
    Users = <unknown>
    OEM# = 0
    Origin# = 1
    NumCPU = 1
    /bin/arch = i86pc
    /usr/bin/arch -k = i86pc
    /usr/convex/getsysinfo = unknown
    hostinfo = unknown
    /bin/machine = unknown
    /usr/bin/oslevel = unknown
    /bin/universe = unknown
    PATH: /usr/sbin
    PATH: /usr/bin
    PATH: /usr/openwin/bin
    PATH: /usr/ucb
    ## Core tests. ##
    configure:1546: checking build system type
    configure:1564: result: i386-pc-solaris2.10
    configure:1572: checking host system type
    configure:1586: result: i386-pc-solaris2.10
    configure:1594: checking target system type
    configure:1608: result: i386-pc-solaris2.10
    configure:1640: checking for a BSD-compatible install
    configure:1695: result: scripts/build/unix/install-sh -c
    configure:1706: checking whether build environment is sane
    configure:1749: result: yes
    configure:1814: checking for gawk
    configure:1843: result: no
    configure:1814: checking for mawk
    configure:1843: result: no
    configure:1814: checking for nawk
    configure:1830: found /usr/bin/nawk
    configure:1840: result: nawk
    configure:1850: checking whether make sets $(MAKE)
    configure:1874: result: no
    configure:2085: checking for gcc
    configure:2114: result: no
    configure:2165: checking for cc
    configure:2181: found /usr/ucb/cc
    configure:2191: result: cc
    configure:2355: checking for C compiler version
    configure:2358: cc --version </dev/null >&5
    /usr/ucb/cc: language optional software package not installed
    configure:2361: $? = 1
    configure:2363: cc -v </dev/null >&5
    /usr/ucb/cc: language optional software package not installed
    configure:2366: $? = 1
    configure:2368: cc -V </dev/null >&5
    /usr/ucb/cc: language optional software package not installed
    configure:2371: $? = 1
    configure:2394: checking for C compiler default output file name
    configure:2397: cc conftest.c >&5
    /usr/ucb/cc: language optional software package not installed
    configure:2400: $? = 1
    configure: failed program was:
    | /* confdefs.h. */
    |
    | #define PACKAGE_NAME ""
    | #define PACKAGE_TARNAME ""
    | #define PACKAGE_VERSION ""
    | #define PACKAGE_STRING ""
    | #define PACKAGE_BUGREPORT ""
    | #define PACKAGE "mod_jk"
    | #define VERSION "1.2.21"
    | /* end confdefs.h. */
    |
    | int
    | main ()
    | {
    |
    | ;
    | return 0;
    | }
    configure:2439: error: C compiler cannot create executables
    See `config.log' for more details.
    ## Cache variables. ##
    ac_cv_build=i386-pc-solaris2.10
    ac_cv_build_alias=i386-pc-solaris2.10
    ac_cv_env_CC_set=
    ac_cv_env_CC_value=
    ac_cv_env_CFLAGS_set=
    ac_cv_env_CFLAGS_value=
    ac_cv_env_CPPFLAGS_set=
    ac_cv_env_CPPFLAGS_value=
    ac_cv_env_CPP_set=
    ac_cv_env_CPP_value=
    ac_cv_env_CXXCPP_set=
    ac_cv_env_CXXCPP_value=
    ac_cv_env_CXXFLAGS_set=
    ac_cv_env_CXXFLAGS_value=
    ac_cv_env_CXX_set=
    ac_cv_env_CXX_value=
    ac_cv_env_F77_set=
    ac_cv_env_F77_value=
    ac_cv_env_FFLAGS_set=
    ac_cv_env_FFLAGS_value=
    ac_cv_env_LDFLAGS_set=
    ac_cv_env_LDFLAGS_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_host=i386-pc-solaris2.10
    ac_cv_host_alias=i386-pc-solaris2.10
    ac_cv_prog_AWK=nawk
    ac_cv_prog_ac_ct_CC=cc
    ac_cv_prog_make_make_set=no
    ac_cv_target=i386-pc-solaris2.10
    ac_cv_target_alias=i386-pc-solaris2.10
    ## Output variables. ##
    ACLOCAL='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run aclocal-1.9'
    AMDEPBACKSLASH=''
    AMDEP_FALSE=''
    AMDEP_TRUE=''
    AMTAR='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run tar'
    APACHE20_OEXT=''
    APACHE_CONFIG_VARS=''
    APACHE_DIR=''
    APXS=''
    APXSCFLAGS=''
    APXSCPPFLAGS=''
    APXSLDFLAGS=''
    AR=''
    AUTOCONF='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run autoconf'
    AUTOHEADER='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run autoheader'
    AUTOMAKE='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run automake-1.9'
    AWK='nawk'
    CC='cc'
    CCDEPMODE=''
    CFLAGS=''
    CP=''
    CPP=''
    CPPFLAGS=''
    CXX=''
    CXXCPP=''
    CXXDEPMODE=''
    CXXFLAGS=''
    CYGPATH_W='echo'
    DEFS=''
    DEPDIR=''
    ECHO='echo'
    ECHO_C=''
    ECHO_N='-n'
    ECHO_T=''
    EGREP=''
    EXEEXT=''
    F77=''
    FFLAGS=''
    GREP=''
    INSTALL_DATA='${INSTALL} -m 644'
    INSTALL_PROGRAM='${INSTALL}'
    INSTALL_SCRIPT='${INSTALL}'
    INSTALL_STRIP_PROGRAM='${SHELL} $(install_sh) -c -s'
    INSTALL_TYPE=''
    JAVA_HOME=''
    JK_JNI_WORKER=''
    LDFLAGS=''
    LIBOBJS=''
    LIBS=''
    LIBTOOL=''
    LIB_JK_TYPE=''
    LN_S=''
    LTLIBOBJS=''
    MAKEINFO='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run makeinfo'
    MAKE_DYNAMIC_APACHE_FALSE=''
    MAKE_DYNAMIC_APACHE_TRUE=''
    MKDIR=''
    OBJEXT=''
    OS=''
    PACKAGE='mod_jk'
    PACKAGE_BUGREPORT=''
    PACKAGE_NAME=''
    PACKAGE_STRING=''
    PACKAGE_TARNAME=''
    PACKAGE_VERSION=''
    PATH_SEPARATOR=':'
    PERL=''
    RANLIB=''
    RM=''
    SED=''
    SET_MAKE='MAKE=make'
    SHELL='/bin/bash'
    STRIP=''
    TEST=''
    VERSION='1.2.21'
    WEBSERVER=''
    ac_ct_AR=''
    ac_ct_CC='cc'
    ac_ct_CXX=''
    ac_ct_F77=''
    ac_ct_RANLIB=''
    ac_ct_STRIP=''
    am__fastdepCC_FALSE=''
    am__fastdepCC_TRUE=''
    am__fastdepCXX_FALSE=''
    am__fastdepCXX_TRUE=''
    am__include=''
    am__leading_dot='.'
    am__quote=''
    am__tar='${AMTAR} chof - "$$tardir"'
    am__untar='${AMTAR} xf -'
    apache_include=''
    bindir='${exec_prefix}/bin'
    build='i386-pc-solaris2.10'
    build_alias=''
    build_cpu='i386'
    build_os='solaris2.10'
    build_vendor='pc'
    datadir='${prefix}/share'
    exec_prefix='NONE'
    host='i386-pc-solaris2.10'
    host_alias=''
    host_cpu='i386'
    host_os='solaris2.10'
    host_vendor='pc'
    includedir='${prefix}/include'
    infodir='${prefix}/info'
    install_sh='/export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/install-sh'
    int32_t_fmt=''
    int32_value=''
    int64_t_fmt=''
    int64_value=''
    libdir='${exec_prefix}/lib'
    libexecdir='${exec_prefix}/libexec'
    localstatedir='${prefix}/var'
    mandir='${prefix}/man'
    mkdir_p='$(install_sh) -d'
    oldincludedir='/usr/include'
    prefix='NONE'
    program_transform_name='s,x,x,'
    sbindir='${exec_prefix}/sbin'
    sharedstatedir='${prefix}/com'
    sysconfdir='${prefix}/etc'
    target='i386-pc-solaris2.10'
    target_alias=''
    target_cpu='i386'
    target_os='solaris2.10'
    target_vendor='pc'
    uint32_t_fmt=''
    uint32_t_hex_fmt=''
    uint64_t_fmt=''
    uint64_t_hex_fmt=''
    ## confdefs.h. ##
    #define PACKAGE "mod_jk"
    #define PACKAGE_BUGREPORT ""
    #define PACKAGE_NAME ""
    #define PACKAGE_STRING ""
    #define PACKAGE_TARNAME ""
    #define PACKAGE_VERSION ""
    #define VERSION "1.2.21"
    configure: exit 77

    You need to make sure the source is for the same version i.e. if you run apache 2.0.52 you need the source of 2.0.52. I successfully ran mixed installs, but I would not recommend it. You can download the required source from Apache.
    As for your compiler problem, make sure you have �/usr/ccs/bin/� in the your path, if you do not have it installed you will have to add the pkg �SUNWsprot�. You do not have 'make' in yout path.
    Make sure you have the following packages installed:
    SUNWbtool, SUNWsprot, SUNWtoo
    SUNWhea, SUNWarc, SUNWlibm, SUNWlibms
    SUNWdfbh, SUNWcg6h, SUNWxwinc, SUNWolinc,
    SUNWxglh,SUNWarcx, SUNWbtoox, SUNWdplx,
    SUNWscpux, SUNWsprox, SUNWlmsx, SUNWlmx
    SUNWlibCx, SUNWtoox, SUNWsra, SUNWsrh

  • AppleTV and compilations that aren't really compilations

    In my iTunes library on the Mac, I have a number of greatest-hits-type albums that used to be marked as compilations. I unmarked them quite some time ago, and cleaned up my library in other ways, and I now have that working just the way I want it. Problem is, on the AppleTV which is sync-ed to that library, quite a few of these still appear under Compilations.
    I have read through other forum posts that have a problem with compilations not being treated exactly the same way between the AppleTV and iTunes. That's not quite my concern here. I wonder how I can get the AppleTV to recognize that these albums are not compilations at all.

    I have songs that are part of compilations. I don't care and I don't see the point of removing the compilations check mark because the songs show up under Artist and Albums.
    I select one song in a compilation to see what happens with removing the compilation check mark.
    1. I open the compilation on the AppleTV and see the song there with others.
    2. I selected the song on my iMac itunes and removed the compilation check mark.
    3. Looked on the AppleTV and it was still in the compilation.
    4. Went out to the menu and back to My Songs and Compilations and it was still there.
    5. Back at my iMac selected sync
    6. Looked on the AppleTV and it was still in the compilation.
    7. Went out to the menu and back to My Songs and Compilations and it was no longer there.
    The song is not listed in the compilations but still shows up in Artists and Albums.
    In my iMac iTunes I use custom sync for the AppleTV, and in the Music tab I have selected Sync Music and Selected Playlists, Artists, and Genres.
    Hope this helps. ..Bob

  • Compilation problems using NVL function in Pro*C subselect

    I have come across a weird oracle problem. When I execute the following query in SQLPlus it works but when
    I include it in Pro*C code in a EXEC SQL statement it gives syntax errors and fails to compile. Any idea what I am doing wrong.
    SELECT DISTINCT
         A.ID_PERSON,
         C.ID_STAGE_PERSON_LINK ,
         A.NM_PERSON_FULL,
         A.NBR_PERSON_AGE,
         A.ADDR_PERSON_ST_LN_1,
         A.ADDR_PERSON_CITY,
         A.ADDR_PERSON_ZIP,
         A.CD_PERSON_STATE,
         A.CD_PERSON_COUNTY,
         A.NBR_PERSON_PHONE,
         C.CD_STAGE_PERS_REL_INT
         FROM
              PERSON A,
              STAGE_PERSON_LINK C
         WHERE
         C.ID_CASE = 88776721
         AND          A.IND_INVALID_PERS IS NULL
         AND          C.CD_STAGE_PERS_TYPE = 'PRN'
         AND          C.ID_PERSON = A.ID_PERSON
         AND C.ID_STAGE_PERSON_LINK =
    NVL (
                   (SELECT MAX(F.ID_STAGE_PERSON_LINK)
                   FROM STAGE_PERSON_LINK F
                   WHERE F.ID_PERSON=C.ID_PERSON
                   AND F.ID_CASE = C.ID_CASE
                        AND F.CD_STAGE_PERS_TYPE = 'PRN'
                        AND F.CD_STAGE_PERS_REL_INT IS NOT NULL)
                   (SELECT MAX(G.ID_STAGE_PERSON_LINK)
                   FROM STAGE_PERSON_LINK G
                   WHERE G.ID_PERSON=C.ID_PERSON
                   AND G.ID_CASE = C.ID_CASE
                        AND G.CD_STAGE_PERS_TYPE = 'PRN')
    AND A.ID_PERSON NOT IN
    SELECT S.ID_PERSON
    FROM STAGE_PERSON_LINK S,STAGE T
    WHERE S.ID_CASE = C.ID_CASE
    AND S.ID_CASE = T.ID_CASE
    AND S.ID_STAGE = T.ID_STAGE
    AND T.CD_STAGE &lt;&gt; 'INT'
    MINUS
    SELECT H.ID_PERSON
    FROM STAGE_PERSON_LINK H, STAGE F
    WHERE H.ID_CASE = F.ID_CASE
    AND H.ID_STAGE = F.ID_STAGE
    AND H.ID_CASE = C.ID_CASE
    AND H.CD_STAGE_PERS_ROLE &lt;&gt; 'XE'
    AND F.CD_STAGE &lt;&gt; 'INT'
    This query returns data when run in sqlplus.When used in a Pro*C C program and compiled the precompiler complains with syntax errors when used with EXEC SQL DECLARE CLSS82D_CURSOR CURSOR FOR &lt; query above &gt;.However removing the NVL function and retaining the subselect clause compiles but that is not what I want to do.
    Syntax error at line 262, column 20, file clss82d.pc:
    Error at line 262, column 20 in file clss82d.pc
    SELECT MAX( F.ID_STAGE_PERSON_LINK )
    ...................1
    PCC-S-02201, Encountered the symbol "MAX" when expecting one of the following:
    ( ) * + - / . @ | at, day, hour, minute, month, second, year,
    The symbol "(" was substituted for "MAX" to continue.
    Syntax error at line 263, column 10, file clss82d.pc:
    Error at line 263, column 10 in file clss82d.pc
    FROM STAGE_PERSON_LINK F
    .........1
    PCC-S-02201, Encountered the symbol "FROM" when expecting one of the following:
    , ) * + - / | at, day, hour, minute, month, second, year,

    Pro*C works bit differently tha sqlplus. try removing the blank line after
    SELECT MAX(G.ID_STAGE_PERSON_LINK)
    FROM STAGE_PERSON_LINK G
    WHERE G.ID_PERSON=C.ID_PERSON
    AND G.ID_CASE = C.ID_CASE
    AND G.CD_STAGE_PERS_TYPE = 'PRN')
    good luck,
    Gauranga

  • Compilation problem with templates while using option -m64

    Hi,
    I have compilation problem with template while using option -m64.
    No problem while using option -m32.
    @ uname -a
    SunOS snt5010 5.10 Generic_127111-11 sun4v sparc SUNW,SPARC-Enterprise-T5220
    $ CC -V
    CC: Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25
    Here is some C++ program
    ############# foo5.cpp #############
    template <typename T, T N, unsigned long S = sizeof(T) * 8>
    struct static_number_of_ones
    static const T m_value = static_number_of_ones<T, N, S - 1>::m_value >> 1;
    static const unsigned long m_count = static_number_of_ones<T, N, S - 1>::m_count + (static_number_of_ones<T, N, S - 1>::m_value & 0x1);
    template <typename T, T N>
    struct static_number_of_ones<T, N, 0>
    static const T m_value = N;
    static const unsigned long m_count = 0;
    template <typename T, T N>
    struct static_is_power_of_2
    static const bool m_result = (static_number_of_ones<T,N>::m_count == 1);
    template <unsigned long N>
    struct static_number_is_power_of_2
    static const bool m_result = (static_number_of_ones<unsigned long, N>::m_count == 1);
    int main(int argc)
    int ret = 0;
    if (argc > 1)
    ret += static_is_power_of_2<unsigned short, 16>::m_result;
    ret += static_is_power_of_2<unsigned int, 16>::m_result;
    ret += static_is_power_of_2<unsigned long, 16>::m_result;
    ret += static_number_is_power_of_2<16>::m_result;
    else
    ret += static_is_power_of_2<unsigned short, 17>::m_result;
    ret += static_is_power_of_2<unsigned int, 17>::m_result;
    ret += static_is_power_of_2<unsigned long, 17>::m_result;
    ret += static_number_is_power_of_2<17>::m_result;
    return ret;
    Compiation:
    @ CC -m32 foo5.cpp
    // No problem
    @ CC -m64 foo5.cpp
    "foo5.cpp", line 20: Error: An integer constant expression is required here.
    "foo5.cpp", line 36: Where: While specializing "static_is_power_of_2<unsigned long, 16>".
    "foo5.cpp", line 36: Where: Specialized in non-template code.
    "foo5.cpp", line 26: Error: An integer constant expression is required here.
    "foo5.cpp", line 37: Where: While specializing "static_number_is_power_of_2<16>".
    "foo5.cpp", line 37: Where: Specialized in non-template code.
    "foo5.cpp", line 20: Error: An integer constant expression is required here.
    "foo5.cpp", line 43: Where: While specializing "static_is_power_of_2<unsigned long, 17>".
    "foo5.cpp", line 43: Where: Specialized in non-template code.
    "foo5.cpp", line 26: Error: An integer constant expression is required here.
    "foo5.cpp", line 44: Where: While specializing "static_number_is_power_of_2<17>".
    "foo5.cpp", line 44: Where: Specialized in non-template code.
    4 Error(s) detected.
    Predefined macro:
    @ CC -m32 -xdumpmacros=defs foo5.cpp | & tee log32
    @ CC -m64 -xdumpmacros=defs foo5.cpp | & tee log64
    @ diff log32 log64
    7c7
    < #define __TIME__ "09:24:58"
    #define __TIME__ "09:25:38"20c20
    < #define __sparcv8plus 1
    #define __sparcv9 1[snipped]
    =========================
    What is wrong?
    Thanks,
    Alex Vinokur

    Bug 6749491 has been filed for this problem. It will be visible at [http://bugs.sun.com] in a day or two.
    If you have a service contract with Sun, you can ask to have this bug's priority raised, and get a pre-release version of a compiler patch that fixes the problem.
    Otherwise, you can check for new patches from time to time at
    [http://developers.sun.com/sunstudio/downloads/patches/]
    and see whether this bug is listed as fixed.

  • Pro*Cobol PCO Compilation problem in Linux

    Hi,
    DB :oracle 11g on RHEL 5.5
    when we are compiling the (Pro*cobol ) PCO code it is giving us the error :
    System default option values taken from: /oracle/oracle11g/app/product/11.2.0/dbhome_1/precomp/admin/pcbcfg.cfg
    Error at line 320, column 35 in file BR2385.PCO
    WHERE A.SOC_NO = :PARAM-SOC
    ..................................1
    PCB-S-00223, Undeclared variable "PARAM-SOC".
    when we change the pcbcfg.cfg file with flag : declare_section=no it's compile without error.
    But in this scenario cobol app doesn't run.
    if we declare the undeclared variable in the section
    EXEC SQL BEGIN DECLARE SECTION END-EXEC.
    PARAM-SOC PIC X(25).
    EXEC SQL END DECLARE SECTION END-EXEC.
    and compile it with declare_section=yes then cobol app. run fine.
    Are different files generated (cob,int,gnt) after compilation with the option declare_section=no and declare_section=yes.
    Pls help us in this regards. we have lot of file which having these issue and we don't want to do manual changes "EXEC SQL BEGIN" in it.
    Thanks in advance..

    Your code is faulty and has to be fixed.
    No compilation problem is present, the compiler correctly barfs.
    As this is not a support forum, kindly keep your non-issues out of this forum.
    Thank you!!!
    Sybrand Bakker
    Senior Oracle DBA

  • Occi::Number compilation problem in Linux

    Hi,
    I got following error when I complile my application which uses OCCI (Oracle C++ Call Interface) shiped with Oracle 9.2. I added the compiler flag -Dlint .
    When I dont add the compiler flag I dont get following error. My machine is running RedHat linux 7.3
    /usr/bin/g++ -c -I/opt/ora9/product/9.2/rdbms/demo -I/opt/ora9/product/9.2/rdbms/public -I/opt/ora9/product/9.2/plsql/public -I/opt/ora9/product/9.2/network/public myapp.cpp -g -Wall -DLiS -Dlint -DORACLE -I../include -DQT_THREAD_SUPPORT
    In file included from /opt/ora9/product/9.2/rdbms/demo/occi.h:40,
    from ../include/DatabaseSupport.h:17,
    from myapp.cpp:4:
    /opt/ora9/product/9.2/rdbms/demo/occiData.h:374: `oracle::occi::Number::Number (char)' has already been
    declared in `oracle::occi::Number'
    /opt/ora9/product/9.2/rdbms/demo/occiData.h:408: `oracle::occi::Number::operator char () const' has
    already been declared in `oracle::occi::Number'
    If I dont compile my application with -Dlint compiler flag I cant run the application.
    I think this is a bug in occi::Number class
    Any solusion??
    Thanking in advance
    nkran

    Your code is faulty and has to be fixed.
    No compilation problem is present, the compiler correctly barfs.
    As this is not a support forum, kindly keep your non-issues out of this forum.
    Thank you!!!
    Sybrand Bakker
    Senior Oracle DBA

  • Before Update Trigger compilation problem

    Hello experts! I have a compilation problem for a trigger I am trying to create.
    As a matter of fact it should update INT_INITIAL with the old value of INT_LOCK.
    The compilation fails and the debugger raises an ORA 01747 error (invalid declaration for user table, user column etc.)
    Do you have an idea what is wrong with my code?
    create or replace
    TRIGGER TRIGGER_INT_INITIAL
    BEFORE UPDATE ON  TBL_MATRIX_INTERMEDIATE_RESULT
    FOR EACH ROW
    Begin
      IF NVL(:new.INT_INITIAL, 0) != :old.INT_LOCK THEN
           UPDATE TBL_MATRIX_INTERMEDIATE_RESULT set
          :NEW.INT_INITIAL = :old.INT_LOCK;
      END IF;
    END;Regards,
    Seb

    Hi Seb,
    You don't need to use UPDATE stmt here as you are updating the same table on which your trigger is fired. So it may cause mutating table error too.
    when you use :new.colname it will immediately take care of the new value to be inserted in the respective column.
    So no need to write Update stmt.
    Hence remove,
    UPDATE TBL_MATRIX_INTERMEDIATE_RESULT set And use := is an assignment operator whereas = is to equate..
    :=Twinkle

Maybe you are looking for