gcj-4.6 4.6.2-2 source package in Ubuntu

Changelog

gcj-4.6 (4.6.2-2) unstable; urgency=medium

  * Sync packaging with gcc-4.6 4.6.2-4.
 -- Matthias Klose <email address hidden>   Thu,  24 Nov 2011 13:45:12 +0000

Upload details

Uploaded by:
Matthias Klose
Uploaded to:
Precise
Original maintainer:
Debian GCC maintainers
Architectures:
any all
Section:
devel
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
gcj-4.6_4.6.2.orig.tar.gz 126 bytes d39d3664a2066154d3c376245a218c9e50b215dcc880e29ba1130d7dbb0e4002
gcj-4.6_4.6.2-2.diff.gz 800.0 KiB 009055aec6f8438cc3e212d44e806626bc0bfb6144c649b5b44383754b4eadb4
gcj-4.6_4.6.2-2.dsc 3.5 KiB f39d03c7868e8d7e8065932703626ea9cdad5e95872fb1d57da7b4ce7b4bc61d

Available diffs

View changes file

Binary packages built by this source

gcj-4.6-base: GCC, the GNU Compiler Collection (gcj base package)

 This package contains files common to all java related packages
 built from the GNU Compiler Collection (GCC).

gcj-4.6-jdk: gcj and classpath development tools for Java(TM)

 GCJ is a front end to the GCC compiler which can natively compile both
 Java(tm) source and bytecode files. The compiler can also generate class
 files. Other java development tools from classpath are included in this
 package.
 .
 The package contains as well a collection of wrapper scripts and symlinks.
 It is meant to provide a Java-SDK-like interface to the GCJ tool set.

gcj-4.6-jre: Java runtime environment using GIJ/classpath

 GIJ is a Java bytecode interpreter, not limited to interpreting bytecode.
 It includes a class loader which can dynamically load shared objects, so
 it is possible to give it the name of a class which has been compiled and
 put into a shared library on the class path.
 .
 The package contains as well a collection of wrapper scripts and symlinks.
 It is meant to provide a Java-RTE-like interface to the GIJ/GCJ tool set.

gcj-4.6-jre-headless: Java runtime environment using GIJ/classpath (headless version)

 GIJ is a Java bytecode interpreter, not limited to interpreting bytecode.
 It includes a class loader which can dynamically load shared objects, so
 it is possible to give it the name of a class which has been compiled and
 put into a shared library on the class path.
 .
 The package contains as well a collection of wrapper scripts and symlinks.
 It is meant to provide a Java-RTE-like interface to the GIJ/GCJ tool set,
 limited to the headless tools and libraries.

gcj-4.6-jre-lib: Java runtime library for use with gcj (jar files)

 This is the jar file that goes along with the gcj front end to gcc.

gcj-4.6-source: GCJ java sources for use in IDEs like eclipse and netbeans

 These are the java source files packaged as a zip file for use in development
 environments like eclipse and netbeans.

libgcj-doc: libgcj API documentation and example programs

 Autogenerated documentation describing the API of the libgcj library.
 Sources and precompiled example programs from the classpath library.

libgcj12: Java runtime library for use with gcj

 This is the runtime that goes along with the gcj front end to
 gcc. libgcj includes parts of the Java Class Libraries, plus glue to
 connect the libraries to the compiler and the underlying OS.
 .
 To show file names and line numbers in stack traces, the packages
 libgcj12-dbg and binutils are required.

libgcj12-awt: AWT peer runtime libraries for use with gcj

 These are runtime libraries holding the AWT peer implementations
 for libgcj (currently the GTK+ based peer library is required, the
 QT bases library is not built).

libgcj12-dbg: Debugging symbols for libraries provided in libgcj12-dev

 The package provides debugging symbols for the libraries provided
 in libgcj12-dev.
 .
 binutils is required to show file names and line numbers in stack traces.

libgcj12-dev: Java development headers for use with gcj

 These are the development headers that go along with the gcj front end
 to gcc. libgcj includes parts of the Java Class Libraries, plus glue
 to connect the libraries to the compiler and the underlying OS.