Flex Compile Problems

Hi,
I'm getting a very strange error in my project that seemed to
suddenly start happening out of nowhere. I was simply adding
functions to a class and now whenever I compile I get the error:
An internal build error has occurred. Right-click for more
information.
The location is "Unknown" and right-clicking doesn't seem to
help give me any good info on why this is happening. Does anyone
know what this means?
Any help would be great!

Try Project - Clean... from the menu bar. Then restart
FB.

Similar Messages

  • Error in executing a process for Flex compilation ....exceeds 32K...

    Hi,
    deployin my model i get the following error-message.
    "Error in executing a process for Flex compilation, Error: Branch between 64935 and 97770 around line 0 exceeds 32K span. If possible, please refactor this component.
    Error: Branch between 64935 and 97770 around line 0 exceeds 32K span."
    Do i delete a sort-element from my model it is deployed very well. So what does this message exactly mean and how can I locate where the error occurs and how can i fix that problem because i need this sort-element to be in my model.
    Thanks for your help!
    Tobias

    Hi Tobias,
    You are receiving this error due to a current limitation in the Flex server. How you can fix this is to split the iView you are currently working on into two iViews, and embed one within the other. This will decrease the size of the current iView you are receiving the error for and eliminate this problem.
    Hope this helps
    Cheers,
    Scott

  • Flex compilation error

    Hi All,
    I am getting flex compilation error when i deploy the models which were developed in older version7.0, now it is 7.01.I am getting the following error in 7.01 version.
    Flex2Compiler.Build: Error in executing a process for Flex compilation: /usr/sap/BWD/DVEBMGS30/j2ee/cluster/server0/GUIMachine_Business_Packages/[KCRXK59]MyModels.SMIScoreCard/FLEX_COMPILATION_FOLDER/AAD583.mxml
    Does the older version models doesnot deploy in new versions?
    Thanks
    Srinivas K

    Hello Srinivas,
    Currently i am also facing the same issue , Can you let us know were you able to solve the problem u encountered , if yes how?
    Thanks and Regards,
    Ronniee

  • Flex compilation error: line exceeds 32k span

    Hi All,
    I am trying to execute my application being developed in VC7.0 (nw04s sneak preview version) using tabbed layers. I have 3 layers and has the following UI components
    1 tab/layer: input form
    2 tab/layer: table control
    3 tab/layer: table control
    Following is the error from the source Viewer window
    <b>com.myComp.myProduct.8J.Empdetailsview</b>
    Error in executing a process for Flex compilation, Error: Branch between 8421 and 41193 around line 0 exceeds 32K span. If possible, please refactor this component.
          (E:\usr\sap\J2E\JC01\j2ee\cluster\server0\GUIMachine_Business_Packages\empModel_18608\FLEX_COMPILATION_FOLEDR\AAD8J-generated.as:2188)
    Error: Branch between 8421 and 41193 around line 0 exceeds 32K span.
    Failed to compile AAD8J.mxml
    PS: Initially I had a table and chart controls in my second layer (no 3rd layer then) and got the same error however, after removing the chart contrl, the app begun to run.
    Now I added a 3rd layer which has one table contrl only and now the app is not working. I also have eventing between my layers..
    Please help
    Thanks
    Sathish

    Hi
    The 32k issue id pretty hard to get rid of once it starts, instead of using the 3rd layer, try and create a nested iview, you can also try and use a nested iview for each layer, this is a bit more complicated to do but does seem to workaround the 32k problem.
    Jarrod

  • Flex compiler not using GlobalOptimizer.java?

    hello:
          I dived into the source of the flex compiler and I found that in the package adobe.abc in the Flexsdk/modules/asc/src/adobe/abc.
         as I just use the asc.jar to compile an actionscript file, with the -o2 option on, I found that it optimizes my program well!!
         however, when I read the source code of the mxmlc, I found no sign that the bytecode generated was optimized?why doesn't the compiler use the GlobalOptimizer? is the optimizer not yet completed or just as It did , but I haven't fount it?
         and in the GlobalOptimizer.java, what is the Plugin?
         any suggestions or references are appreciated.
         Thanks!!   ^_^

    I figured out the problem.  You have to Export the release build for the project and use that version of the swf.  I was using the version built by default when you work on the project.  Don't quite know what the difference is, but it works now.

  • QTP Flex Testing Problem

    I am trying to test a Flex Application with QTP. I have a Flex compiled application running at the severside.
    In my scenario I have a Map (dynamically generated) with has some Nodes. Problem - First:  QTP Doesn't recognize it, Second:  It doesn't record any action( as per my knowledge If QTP doesn't recognize any Object it takes it as "WinObject" and record action on it, but Here QTP records nothing.
    Along with that After Clicking that Node(element) a Flex Canvas Opens up, which also has many Controls like Menu bar Dropdown list, Button etc. but nothing is being recorded or recognized by QTP, except the main Canvas (parent Object).
    Any advice is highly appreciated.

    I too have an issue with the QTP Flex Add-in and the FlexDataGrid...
    Apparently the comumnNames property was not implemented for the add-in or isn't working. When I use the GetRoProperty method in conjuction with the comunNames property it always is an empty string.
    What's up with that?
    Also, you cannot use the GetCellData method either.
    Any ideas on a work-around?

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

  • Hierarchical data transfer objects confusing Flex compiler...

    I just posted this same query on FlexCoders... but then I
    thought this might be a better target group to ask, so here goes:
    We are working on a set of data transfer objects where we
    have matching server-side java classes and client-side AS classes.
    Some of these DTO contain lists of other DTOs. As an example:
    A.java:
    public class A {
    List<B> blist
    In A.as we have...
    class A {
    public var blist : ArrayCollection;
    And we have B.java and B.as
    Then we have a RemoteObject call to pull down a bunch of A
    objects....
    Here's the problem, Flex does not compile B.as at build-time.
    So if B.as has a compiler problem, you never know about it,
    except that the 'blist' in A never gets populated. If you break
    down the data transfer and debug it. You find that during
    RemoteObject call, the blist data comes "down the wire", but as an
    ArrayCollection generic Objects, they never get turned into
    instances of Bs...
    I am guessing that this is happening because at compile time,
    there is not direct reference to B in the clientside project. Our
    covering .mxml wants one or more A objects, and inside A the blist
    is an ArrayCollection. So the compiler doesn't see a reference to
    B..
    So anyone know how we can fairly seamlessly make sure B.as
    gets compiled at build time so we'd know of compiler issues with it
    rather than spending lots of time debugging mysterious null values?
    (This appears to happen whether the project is set to compile
    on the client-side or the server-side. We are using Flex and FDS
    2.0.1 and Java 1.5)

    up...

  • Removing compiler problem markers

    Does anybody know why I keep getting a pop up window that is
    telling me it can't find a marker id at some location number? I am
    getting one of these messages about every other time I save and
    compile and it is getting RATHER ANNOYING!!! What does it mean and
    how do I eliminate it???
    Thanks in advance for helping me lower my blood pressure!!!
    Have an Ordinary Day...
    KomputerMan ~|:-)

    Yes, I am now getting the same error - but slightly different
    wording
    Removing compile problem markers (Time of error: blah blah
    blah...)
    The details section states:
    An internal error occurred during "Removing compiler problem
    markers".
    java.lang.NullPointerException
    I'm able to compile the same code with no problem from the
    command line on a Linux box. Running the clean comand doesn't fix
    this unfortunately.
    Some background info: I'm running a FDS project against a
    JBoss server on a windows XP machine.
    So, I deleted my project and shut down flex builder. Then
    removed the project files (.actionScriptProperties, .project, &
    .flexProperties) and removed the project folder from the flex.war
    folder in the jboss server. Restarted Flex Builder and created a
    new project the same way the project was built. And wa-la the
    problem is gone.
    So, something has gone bad with the project, but I am not
    sure what because a look a the previous project files and they all
    seem normal. I was having problems with the project trying to
    create the "Output Directory" early, but a rebuild of the project
    seemed to fix that too.
    hope this helps.
    --Andy

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

  • Flex compilation error 1004

    Compilation is ok, but the deployment is giving this error messages:
    Error in executing a process for Flex compilation, Error 1004: Operator '%' must be followed by an operand
          (D:usrsapJ2EJC01j2eeclusterserverGUIMachine_Business_PackagesTest_59674FLEX_COMPILATION_FOLEDRAAD8G.mxml:154)
    Error 1004: Operator '%' must be followed by an operand
          (D:usrsapJ2EJC01j2eeclusterserverGUIMachine_Business_PackagesTest_59674FLEX_COMPILATION_FOLEDRAAD8G.mxml:154)
    Error 1004: Operator '%' must be followed by an operand
          (D:usrsapJ2EJC01j2eeclusterserverGUIMachine_Business_PackagesTest_59674FLEX_COMPILATION_FOLEDRAAD8G.mxml:154)
    Error 1033: ')' expected
          (D:usrsapJ2EJC01j2eeclusterserverGUIMachine_Business_PackagesTest_59674FLEX_COMPILATION_FOLEDRAAD8G.mxml:154)
    Error 1033: ')' expected
          (D:usrsapJ2EJC01j2eeclusterserverGUIMachine_Business_PackagesTest_59674FLEX_COMPILATION_FOLEDRAAD8G.mxml:154)
    Failed to compile AAD8G.mxml
    I do not succeed in finding the cause of this error

    Compilation is ok, but the deployment is giving this error messages:
    Error in compiling Flex application: Error 1004: Operator '=' must be followed by an operand
          (/usr/sap/NW7/DVEBMGS00/j2ee/cluster/server0/GUIMachine_Business_Packages/Poc_59929/FLEX_COMPILATION_FOLDER/AADHE1_P.mxml:374)
    Error 1142: The class 'vc.custom.SkinAssetDependency' could not be loaded.
          (/usr/sap/NW7/DVEBMGS00/j2ee/cluster/server0/GUIMachine_Business_Packages/Poc__59929/FLEX_COMPILATION_FOLDER/AADHDR.mxml)
    Failed to compile AADHDR.mxml
    Edited by: Rafael Ovidio on Feb 15, 2008 10:28 AM

  • 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!).

  • Flex compiler in FlexBuilder and Flex SDK

    I have downloaded Flex Builder 3.0.2 and Flex SDK 3.2. Are
    they using the same version of Flex compiler?
    Is there a way to check the version of Flex compiler?

    quote:
    Originally posted by:
    mab_bond
    And regarding the Advanced datagrid you must copy the
    dataVisualization.swc.from sdk 3.1
    It sounds like the SDK3.2 download is incomplete. I'm not
    sure if upgrade FB with this download is a good idea.

  • 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

Maybe you are looking for