Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: VM
    • Labels:
      None
    • Environment:
      any unix based machine (and cygwin).

      Description

      Allow to use a "standard" way of building BootJVM:
      ../configure --with-java=$JAVA_HOME --with-heap=HEAD_TYPE --with-gc=GC_TYPE
      make
      make install

      1. config_try.tar.gz
        25 kB
        Jean-Frederic Clere
      2. config_try.tar.gz
        26 kB
        Jean-Frederic Clere

        Activity

        Hide
        Bootstrap JVM (Daniel Lydick) added a comment -

        Let us leave this open because I am very
        interested to incorporate the capabilities
        of 'autoconf' into this project. When I get
        the time to [finally] polish off the errata
        items for the base JVM, this will be one of
        the first things to consider.

        Dan Lydick

        (Comment posted first to the harmony-dev@ list.)

        Show
        Bootstrap JVM (Daniel Lydick) added a comment - Let us leave this open because I am very interested to incorporate the capabilities of 'autoconf' into this project. When I get the time to [finally] polish off the errata items for the base JVM, this will be one of the first things to consider. Dan Lydick (Comment posted first to the harmony-dev@ list.)
        Hide
        Geir Magnusson Jr added a comment -

        Is this still needed? can we close this?

        Show
        Geir Magnusson Jr added a comment - Is this still needed? can we close this?
        Hide
        Jean-Frederic Clere added a comment -

        That is no problem to add all the functionalities of config.sh in autoconf/configure, but I am not sure that all the tests are needed.
        For example:

        • why asking for gcc 3.3.2?
        • why testing for sources directories (jvm jni/src/harmony/generic/0.0)?
        • why not buiding everything?
        Show
        Jean-Frederic Clere added a comment - That is no problem to add all the functionalities of config.sh in autoconf/configure, but I am not sure that all the tests are needed. For example: why asking for gcc 3.3.2? why testing for sources directories (jvm jni/src/harmony/generic/0.0)? why not buiding everything?
        Hide
        Daniel Lydick added a comment -

        I like what I have seen so far with
        Jean-Fredric's use of 'autoconf' toward
        configuring 'bootJVM', especially in the
        way that it can deduce the platform
        and C compiler it is running, not to
        mention figuring out if the Java
        compiler and archiver are valid.
        When I wrote the initial 'config.sh'
        script, I kept wishing that I had
        previously written 'autoconf' scripts
        because I have been a user of
        them in many situations for a long time.

        I also like how most of the
        input files are stored in a 'support'
        subdirectory, which can thin out the
        potential clutter in the top level
        directory, which, currently for 'bootJVM',
        has quite a few things in it. Notice
        that the code provided (the November 1
        version, the one I studied most) has a
        number of its input files derived from
        what is the output of the current
        'config.sh' script, meaning that both
        scripts contribute part of the complete
        set of configuration parameters to
        the whole. In order to effectively use
        the 'autoconf' approach, we should
        probably consider either extending
        this example to include all of the
        functionality of the current 'config.sh'
        script (using 'svn update -r HEAD .'
        to get the latest) or consider focusing
        on the core feature set of deducing the
        runtime platform, deducing the
        configuration of the C compiler, and
        perhaps also verifying the validity of
        the JDK programs, then incorporating
        this logic into the current 'config.sh'
        script. I'm open to more suggestions
        here, and I am grateful to Jean-Frederic
        for his work to date on this important
        issue, showing how 'autoconf' can be
        used for 'bootJVM' configuration!

        Dan Lydick

        Show
        Daniel Lydick added a comment - I like what I have seen so far with Jean-Fredric's use of 'autoconf' toward configuring 'bootJVM', especially in the way that it can deduce the platform and C compiler it is running, not to mention figuring out if the Java compiler and archiver are valid. When I wrote the initial 'config.sh' script, I kept wishing that I had previously written 'autoconf' scripts because I have been a user of them in many situations for a long time. I also like how most of the input files are stored in a 'support' subdirectory, which can thin out the potential clutter in the top level directory, which, currently for 'bootJVM', has quite a few things in it. Notice that the code provided (the November 1 version, the one I studied most) has a number of its input files derived from what is the output of the current 'config.sh' script, meaning that both scripts contribute part of the complete set of configuration parameters to the whole. In order to effectively use the 'autoconf' approach, we should probably consider either extending this example to include all of the functionality of the current 'config.sh' script (using 'svn update -r HEAD .' to get the latest) or consider focusing on the core feature set of deducing the runtime platform, deducing the configuration of the C compiler, and perhaps also verifying the validity of the JDK programs, then incorporating this logic into the current 'config.sh' script. I'm open to more suggestions here, and I am grateful to Jean-Frederic for his work to date on this important issue, showing how 'autoconf' can be used for 'bootJVM' configuration! Dan Lydick
        Hide
        Jean-Frederic Clere added a comment -

        now togother with the Makefile to build bootJVM for svn source is that easy as:
        sh buildconf.sh
        ./configure --with-java=/home/jfclere/JAVA/j2sdk1.4.2_06 --with-heap=simple --with-gc=stub
        make

        Show
        Jean-Frederic Clere added a comment - now togother with the Makefile to build bootJVM for svn source is that easy as: sh buildconf.sh ./configure --with-java=/home/jfclere/JAVA/j2sdk1.4.2_06 --with-heap=simple --with-gc=stub make
        Hide
        Jean-Frederic Clere added a comment -

        The submitted version allow to build the config/config.h automaticly. I will prepare the corresponding makefiles.
        The lastest version if available as http://people.apache.org/~jfclere/config_try.jar.gz

        Show
        Jean-Frederic Clere added a comment - The submitted version allow to build the config/config.h automaticly. I will prepare the corresponding makefiles. The lastest version if available as http://people.apache.org/~jfclere/config_try.jar.gz

          People

          • Assignee:
            Unassigned
            Reporter:
            Jean-Frederic Clere
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development