SDK 1.4 compilation problems

I get the following error when I try to compile a java program in the 1.4 envt. There are no errors in 1.3 envt.
home/skreddy/jsdk14/jre/lib/sparc/client/libjvm.so, because ld.so.1: xjavac: fatal: relocation error: file /home/skreddy/jsdk14/jre/lib/sparc/client/libjvm.so: symbol __1cG__CrunSregister_exit_code6FpG_v_v_: referenced symbol not found
I have added the ..../jre/lib/sparc/client to the LD_LIBRARY_PATH.
Any help is appreciated.
Thanks
Vinod

Out of interest, what is xjavac? Does it work when
you use javac itself?xjavac is javac renamed. i have 1.3, 1.4 and an older SDK environment. this way i make sure that the correct exe file is run.

Similar Messages

  • [svn] 2716: SDK-15848 - Conditional compilation constants defined in flex-config. xml are never used if a single constant is specified on the command line

    Revision: 2716
    Author: [email protected]
    Date: 2008-08-04 01:18:12 -0700 (Mon, 04 Aug 2008)
    Log Message:
    SDK-15848 - Conditional compilation constants defined in flex-config.xml are never used if a single constant is specified on the command line
    * There's a possibility this will break a conditional complication test which disallows overwriting an existing definition -- I don't know if that will break the build, but the test should be removed either way.
    * Using append syntax ("-define+=" on the command line or ant tasks, or append="true" in flex-config) and redefining a value works now if you use an already-defined namespace and name.
    * So your flex-config may have -define=CONFIG::debug,false, and you may want -define+=CONFIG::debug,true from the commandline build, or FB build.
    * Made the ASC ConfigVar fields final as a sanity check since overwriting is now allowed. It would be harder to track changes and subtle bugs if they were mutable. This means that you must build a new ConfigVar object if you need to make changes.
    Bugs: SDK-15848
    QA: Yes. Please read the updated javadocs in CompilerConfiguration. Tests need to be added to validate that overwriting is allowed, and happens correctly in different situations: I believe the order should be that flex-config is overwritten by a custom config (can we have more than one user config? is the order deterministic? I forget...), is overwritten by commandline or OEM. Did I miss any? (I didn't write code which changes this, it works however the existing configuration system allows overwriting and appending; if we have tests for that, maybe we don't need them duplicated for this feature.)
    Doc: Yes. Please read the updated javadocs in CompilerConfiguration.
    Reviewer: Pete
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-15848
    http://bugs.adobe.com/jira/browse/SDK-15848
    Modified Paths:
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/embedding/ConfigVar.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/common/CompilerConfiguration.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/oem/internal/OEMConfiguration.java

    Please note: I AM USING:
    JkOptions ForwardKeySize ForwardURICompat -ForwardDirectories
    And that's what's supposed to fix this problem in the first place, right??

  • [svn:fx-trunk] 11707: Fix incremental compilation problem with styles.

    Revision: 11707
    Author:   [email protected]
    Date:     2009-11-12 10:52:49 -0800 (Thu, 12 Nov 2009)
    Log Message:
    Fix incremental compilation problem with styles.
    QE notes: None.
    Doc notes: None.
    Bugs: SDK-24173
    Reviewer: Paul
    Tests run: checkintests
    Is noteworthy for integration: No.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24173
    Modified Paths:
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StylesContainer.java

    You have used elements like header, footer, footer1 and nav without using the correct DOCTYPE declaration. Replace the first line of your code with
    <!doctype html>
    Also have a look here for other problems http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fhome.surewest.net%2Fstorytales%2F test%2Fforposting.html
    After the above has been fixed, please come back here to fix the remaining problem(s)
    Gramps

  • 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 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

  • 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

  • Compiling problem in oracle 11g environment

    Hello mates,
    We have recently migrated from oracle10g to oracle11g. we have lot of pro*c and forms programs.
    my requirement is to compile all those pro*c and form programs in 11g.
    for compiling pro*c programs we have compilation scripts. these compilation scripts are prepared
    based on oracle10g. pro*c programs are compiling fine by using this compilation scripts.
    after migrated to 11g, ihave used same 10g compilation scripts to compile pro*c programs.
    1.while compiling the programs first time, i got these errors
    /oracle/app/product/11.2.0.3_cli/lib32/libsql10.a: No such file or directory
    /oracle/app/product/11.2.0.3_cli/rdbms/lib32/kpudfo.o: No such file or directory
    /oracle/app/product/11.2.0.3_cli/lib32/libpls10.a: No such file or directory
    /oracle/app/product/11.2.0.3_cli/lib32/libpls10.a: No such file or directory
    /oracle/app/product/11.2.0.3_cli/lib32/libpls10.a: No such file or directory
    so i have replace all libsql10.a,libpls10.a,libpls10.a,libpls10.a to libsql11.a,libpls11.a,libpls11.a,libpls11.a
    2.then these errors got resolved but second time compilation it shown below error.
    /oracle/app/product/11.2.0.3_cli/rdbms/lib/kpudfo.o: No such file or directory
    so i have removed kpudfo.o file from compilation script.
    3. i have compiled third time then it shown diffrent error as shown below
    ld: fatal: library -lnapt: not found
    ld: fatal: file /oracle/app/product/11.2.0.3_cli/lib/libclntsh.so: wrong ELF class: ELFCLASS64
    ld: fatal: file /oracle/app/product/11.2.0.3_cli/rdbms/lib/cdf.o: wrong ELF class: ELFCLASS64
    ld: fatal: File processing errors. No output written to ./ebsparam
    i have changed script
    "/usr/local/bin/gcc -m32 -g -DSOLARIS -DSOLARIS2 -I$HOME/include"
    to
    "/usr/local/bin/gcc -m64 -g -DSOLARIS -DSOLARIS2 -I$HOME/include"
    4. then i have compiled again then it shown error as below
    ld: fatal: file /usr18/SIR02551/mydomain/BD/obj/ebsparam.o: wrong ELF class: ELFCLASS32
    ld: fatal: File processing errors. No output written to ./ebsparam
    collect2: ld returned 1 exit status
    because of 32 bit problem i have changed script to 32 to 64. but now it is showing this error
    what is the problem i am not able to understand.
    please help on this
    Thanks
    Edited by: ramadurga.v on Jan 25, 2013 3:10 PM
    Edited by: ramadurga.v on Jan 25, 2013 3:26 PM

    Pl do not post duplicates -
    Compilaton problem in 11g environment
    Compilation problem in 11g environment
    Compilation problem in 11g environment

  • RE: RE : Compile problems

    Doug,
    I also had a very similar error. At first I thought it might have been
    similar to the technote 38525, but in the end I force compiled the workspace
    and re made the distribution and the fcompile worked like normal. So if you
    don't think the technote matches your situation then I recommend force
    compiling your workspace.
    Regards,
    Allister
    -----Original Message-----
    From: [email protected]
    [<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of Ajith Kallambella
    Sent: Thursday, 6 May 1999 23:01
    To: [email protected]; [email protected]
    Subject: RE : Compile problems
    Doug,
    Your method is probably returning a data type that the codegenerator
    is misinterpreting.
    It could be related to a documented problem where a return statement
    returning an unsigned long( or a few other type ) value generates a
    GENERICRETURN instruction, which codegen erroneously believed
    to have no
    operands, causing decompilation errors.
    Take a look at Bug # 38525.
    The suggested work around is not to return unsigned long( or a few other
    data types ).
    Ajith Kallambella M
    Subject: Compile problems
    Has anyone ever seen this error when using fcompile to compile their
    partitions?? The create/compile of the workspace & the
    partitioning of the
    application all went fine. It seems to indicate there may be a
    problem with
    the fetchEncounterWithItsClaim method. What's the IRBlock ?? Any
    help would
    be greatly appreciated!!
    Processing partition generation file:
    /usr/local/bin/forte3j/appdist/hcssdeve/hcssmain/cl27/codegen/hcss
    ma8/hcssma
    8.pgf
    Creating and initializing code generator, this could take some time.
    ERROR: Exiting due to following exception:
    SYSTEM ERROR: Client partition FTCompile_cl0_Client was terminated by
    escaped
    exception. See the remainder of the error stack for more information.
    Class: qqsp_ResourceException
    Error #: [1001, 3]
    Detected at: qqrt_ForteExecAgent::LoadPartition at 1
    Error Time: Wed May 5 17:38:50
    Exception occurred (locally) on partition "Forte_Executor",
    (partitionId
    =
    25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1, taskId =
    [25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1.6]) in application
    "FTCompile_cl0", pid 13061 on node gromit.HealthPartners.com in
    environment <unknown>.
    SYSTEM ERROR: Variable index 71 is outside the range 0 to 26 for the
    IRBlock fetchEncounterWithItsClaim.
    Class: qqsp_Exception
    Error #: [1001, 203]
    Detected at: qqrt_IRBlock::GetTypeIndex at 1
    Last TOOL statement: method ForteCompiler.ProcessPGF
    Error Time: Wed May 5 17:38:50
    Exception occurred (locally) on partition "Forte_Executor",
    (partitionId =
    25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1, taskId =
    [25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1.6]) in application
    "FTCompile_cl0", pid 13061 on node gromit.HealthPartners.com in
    environment <unknown>.
    Doug Scurr
    HealthPartners
    8100 34th Avenue South
    9th Floor
    Minneapolis, MN 55440-1309
    (612)883-7317
    - att-1.unk
    Get Free Email and Do More On The Web. Visit <a href=
    "http://www.msn.com">http://www.msn.com</a>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
    >
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

    Allister,
    That's the only thing(force compile) I could think of to try, so I did & re
    made the distribution last night & it worked fine!!
    Doug Scurr
    HealthPartners
    8100 34th Avenue South
    9th Floor
    Minneapolis, MN 55440-1309
    (612)883-7317
    -----Original Message-----
    From: Allister Dickson [SMTP:[email protected]]
    Sent: Friday, May 07, 1999 1:23 AM
    To: Ajith Kallambella; [email protected];
    [email protected]
    Subject: RE: RE : Compile problems
    Doug,
    I also had a very similar error. At first I thought it might have
    been
    similar to the technote 38525, but in the end I force compiled the
    workspace
    and re made the distribution and the fcompile worked like normal. So
    if you
    don't think the technote matches your situation then I recommend
    force
    compiling your workspace.
    Regards,
    Allister
    > -----Original Message-----
    > From: [email protected]
    > [<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of Ajith
    Kallambella
    > Sent: Thursday, 6 May 1999 23:01
    > To: [email protected]; [email protected]
    > Subject: RE : Compile problems
    >
    >
    > Doug,
    >
    > Your method is probably returning a data type that the
    codegenerator
    > is misinterpreting.
    >
    > It could be related to a documented problem where a return
    statement
    > returning an unsigned long( or a few other type ) value generates
    a
    > GENERICRETURN instruction, which codegen erroneously believed
    > to have no
    > operands, causing decompilation errors.
    >
    > Take a look at Bug # 38525.
    >
    > The suggested work around is not to return unsigned long( or a few
    other
    > data types ).
    >
    >
    > Ajith Kallambella M
    >
    >
    > Subject: Compile problems
    >
    >
    > Has anyone ever seen this error when using fcompile to compile
    their
    > partitions?? The create/compile of the workspace & the
    > partitioning of the
    > application all went fine. It seems to indicate there may be a
    > problem with
    > the fetchEncounterWithItsClaim method. What's the IRBlock ?? Any
    > help would
    > be greatly appreciated!!
    >
    > Processing partition generation file:
    > /usr/local/bin/forte3j/appdist/hcssdeve/hcssmain/cl27/codegen/hcss
    > ma8/hcssma
    > 8.pgf
    > Creating and initializing code generator, this could take some
    time.
    > ERROR: Exiting due to following exception:
    >
    > SYSTEM ERROR: Client partition FTCompile_cl0_Client was terminated
    by
    > escaped
    > exception. See the remainder of the error stack for more
    information.
    > Class: qqsp_ResourceException
    > Error #: [1001, 3]
    > Detected at: qqrt_ForteExecAgent::LoadPartition at 1
    > Error Time: Wed May 5 17:38:50
    > Exception occurred (locally) on partition "Forte_Executor",
    > (partitionId
    > =
    > 25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1, taskId =
    > [25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1.6]) in application
    > "FTCompile_cl0", pid 13061 on node gromit.HealthPartners.com
    in
    > environment <unknown>.
    >
    > SYSTEM ERROR: Variable index 71 is outside the range 0 to 26
    for the
    > IRBlock fetchEncounterWithItsClaim.
    > Class: qqsp_Exception
    > Error #: [1001, 203]
    > Detected at: qqrt_IRBlock::GetTypeIndex at 1
    > Last TOOL statement: method ForteCompiler.ProcessPGF
    > Error Time: Wed May 5 17:38:50
    > Exception occurred (locally) on partition
    "Forte_Executor",
    > (partitionId =
    > 25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1, taskId =
    > [25771770-033B-11D3-9BC9-A45FAEA2AA77:0x1.6]) in
    application
    > "FTCompile_cl0", pid 13061 on node
    gromit.HealthPartners.com in
    > environment <unknown>.
    >
    > Doug Scurr
    > HealthPartners
    > 8100 34th Avenue South
    > 9th Floor
    > Minneapolis, MN 55440-1309
    > (612)883-7317
    >
    >
    > - att-1.unk
    >
    >
    > _______________________________________________________________
    > Get Free Email and Do More On The Web. Visit <a href=
    "http://www.msn.com">http://www.msn.com</a>
    > -
    > To unsubscribe, email '[email protected]' with
    > 'unsubscribe forte-users' as the body of the message.
    > Searchable thread archive
    <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
    >
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:<a href=
    "http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

  • Help!!! I have a compiling problem using rfcsdk

    Hello.
    I have a compiling problem.
    My server is  SUN OS 5.9.
    And I made a rfcsdk folder.
    When I used gcc comiler I had a error message as below.
    %>cat mk_gcc2
    gcc  -funsigned-char  -Wcast-align -fPIC -c -I.  -I/home/user/rfcsdk_32/include        -L/home/user/rfcsdk_32/lib  $1.c
    gcc    -funsigned-char    -L/home/user/rfcsdk_32/lib    -o $1 $1.o  -I/home/user/rfcsdk_32/lib/librfccm.so  -laio  -lm   -lrfc   -L.  -lsocket -lnsl -lw -ldl
    %>
    %>
    %>mk_gcc2 plantcl
    &#51221;&#51032;&#46104;&#51648; &#50506;&#51020;                   &#52395;&#48264;&#51704; &#52280;&#51312;&#46108;
    &#44592;&#54840;                       &#54028;&#51068;&#51032;
    __1cG__CrunKpure_error6F_v_         /home/user/rfcsdk_32/lib/librfc.a(cpictlib.o)
    __1cG__CrunKvector_con6FpvIIpF1_vp2_v_ /home/user/rfcsdk_32/lib/librfc.a(cpictlib.o)
    __1cG__CrunMex_rethrow_q6F_v_       /home/user/rfcsdk_32/lib/librfc.a(cpictlib.o)
    c::c(N6,  (int0_t))                 /home/user/rfcsdk_32/lib/librfc.a(cpictlib.o)
    c::c(n6,  (int0_t))                 /home/user/rfcsdk_32/lib/librfc.a(cpictlib.o)
    __1c2K6Fpv_v_                       /home/user/rfcsdk_32/lib/librfc.a(cpictlib.o)
    __1c2k6Fpv_v_                       /home/user/rfcsdk_32/lib/librfc.a(cpictlib.o)
    ld: &#52824;&#47749;&#51201;: &#44592;&#54840; &#52280;&#51312; &#50724;&#47448;. plantcl&#50640; &#52636;&#47141;&#51060; &#44592;&#47197;&#46104;&#51648; &#50506;&#51020;
    collect2: ld returned 1 exit status
    %>
    %>
    Do anyone have a idea about this kinds of errors ?
    I couldn't find any reference from the internet and documents.
    I'll thank you very much if you recommend me.

    Trying
    <description><![CDATA[About 4 PM , March 31,1917.
    The salute from the Fort Christian&rsquo;s Saluting Battery as
    the Captain and officers leave the USS Hancock on their way to
    shore to take over the Danish West
    Indies.]]></description>
    This fixes the
    onmouseover="ShowToolTip('{dsPhotos::description}') problem,
    BUT
    <p>{dsPhotos::description}</p>
    now appears as
    'About 4 PM , March 31,1917. The salute from the Fort
    Christian&rsquo;s Saluting ..."
    with the undesireable &rsquo; instead of '.
    So my problem requires both html translation and javascript
    argument quoting/non-parsing.
    Any ideas?

  • Jdev 10G Custom Tag compilation problems

    Hi,
    I noticed that new tld's are added to "src/META-INF/."
    When i compile my jsp to reference the tld it is not successful b/c it is looking for the tlds within the "public_html" or somewhere within it. I turned off tld and web.xml validation, but jdev 10G still validates the location of the tld. Is there way to configure Jdev to put the tld in another location?
    I know i can work around this by building w/ ant or someother compiler external to Jdev, but would like to remedy this problem so i can use jdeveloper as it is.
    hope someone can shed some light, i've been working on this all day long...
    Thanks in advance,
    Eugene

    i am referenceing the tld via the web.xml alias entry. I found a work around where i copy the tld to somewhere in the public_html location of the project. I guess Jdeveloper doesn't look for the tld within META-INF which is embedded in the src directory structure of the project. For some reason, Jdeveloper doesn't look there for the TLD where it writes the tld to. it's interesting that jdeveloper doesn't look for the tld where it writes to. :)
    from the server side, when i deploy, it works okay. but to get around the compilation problem, i have to copy the tld or softlink it to the META-INF location of the original tld.
    I tried turning off web.xml, tld, and jsp validation of TLDs to get around this problem, but that doesn't seem to "turn it off."
    How do you approach this problem? do you use ant or some other external build process?
    thanks!

Maybe you are looking for