Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Problem with Java + Processing 'media language'. Post 302404642 by andrew1618 on Wednesday 17th of March 2010 02:31:28 AM
Old 03-17-2010
Problem with Java + Processing 'media language'.

Essentially processing is a programming language written in java. My university has decided to use it for it's first computer science subject. Now I am running Debian Lenny 5.04 on my IBM x31 laptop. I downloaded processing-1.1.tgz from processing.org and tar -zxvf-ed it then chmod +x the processing script. When I start it I get the following error message:

Code:
 Exception in thread "main" java.lang.UnsatisfiedLinkError: libawt: libawt.so: cannot open shared object file: No such file or directory
   at java.lang.Runtime._load(libgcj.so.90)
   at java.lang.Runtime.loadLibrary(libgcj.so.90)
   at java.lang.System.loadLibrary(libgcj.so.90)
   at sun.font.FontManager$1.run(FontManager.java:227)
   at java.security.AccessController.doPrivileged(libgcj.so.90)
   at sun.font.FontManager.<clinit>(FontManager.java:223)
   at java.lang.Class.initializeClass(libgcj.so.90)
   at com.sun.java.swing.plaf.gtk.PangoFonts.lookupFont(PangoFonts.java:175)
   at com.sun.java.swing.plaf.gtk.GTKLookAndFeel.getGTKStyleFactory(GTKLookAndFeel.java:1543)
   at com.sun.java.swing.plaf.gtk.GTKLookAndFeel.loadStyles(GTKLookAndFeel.java:1507)
   at com.sun.java.swing.plaf.gtk.GTKLookAndFeel.initialize(GTKLookAndFeel.java:1394)
   at javax.swing.UIManager.setLookAndFeel(libgcj.so.90)
   at javax.swing.UIManager.setLookAndFeel(libgcj.so.90)
   at processing.app.linux.Platform.setLookAndFeel(Unknown Source)
   at processing.app.Base.main(Unknown Source)

Now before you ask me, yes I do have jre installed and besides the linux package is meant to include all the required dependancies anyway. Does anyone have an idea as to what my system is lacking here?

here is some output regarding libawt:

Code:
andrew@debtop:~/processing-1.1$ locate libawt
/home/andrew/.local/share/Trash/files/processing-1.1/java/lib/i386/libawt.so
/home/andrew/Desktop/processing-1.1/java/lib/i386/libawt.so
/home/andrew/processing-1.1/java/lib/i386/libawt.so

Thanks for taking some time to have a look at my problem, regards, Andrew. Smilie

Last edited by pludi; 03-17-2010 at 03:54 AM.. Reason: code tags, please...
 

We Also Found This Discussion For You

1. Programming

can i have an optimal solution for this java code ? Facing Java heap space problem even at 3GB heaps

My desired output is run: for this 1 for this 2 for this 3 for this 4 for this 5 for this 1,2 1->2 for this 2,3 2->3 for this 3,4 3->4 for this 4,5 4->5 for this 1,2,3 1->2,3 (2 Replies)
Discussion started by: vaibhavkorde
2 Replies
MAVEN(1)							   User Commands							  MAVEN(1)

NAME
Maven - Installs a jar into /usr/share/maven-repo. SYNOPSIS
mh_installjar [option]... [pom] [jar] [link]... DESCRIPTION
Installs the jar file in /usr/share/maven-repo, at the correct location for Maven. The jar is copied into the build directory. It can also create additional links to the jar, usually located in /usr/share/java. Where [pom] is the location of the POM associated with the jar to install. GroupId, artifactId and version will be extracted from this file. [jar] is the path to the jar to install, usually located in the build folder. [link] is an additional link to the jar to install, usually there should be a link to usr/share/java/$jar.jar and usr/share/java/$jar-$version.jar to comply with the Java packaging guidelines. Note that there is no need to specify those particular links if the --java-lib option is used. OPTIONS
-h --help: show this text -V --version: show the version -p<package> --package=<package>: name of the Debian package which will contain this jar file -e<version>, --set-version=<version>: set the version for the jar, do not use the version declared in the POM file. -r<rules> --rules=<rules>: path to the file containing the rules to apply when cleaning the POM. Optional, the default location is debian/maven.rules Maven rules are used here to extract the groupId, artifactId and version from the POM file. -l --java-lib: Optional, if given it will install the jar into /usr/share/java to comply with the Debian Java specification. The jar will be installed as /usr/share/java/$name-$version.jar and a versionless link /usr/share/java/$name.jar will point to it, as well as the links installed in /usr/share/maven-repo -n<name> --usj-name=<name>: Optional, the name to use when installing the library in /usr/share/java when --java-lib is used. Defaults to the artifact id found in the POM. -j<version> --usj-version=<version>: Optional, the version to use when installing the library in /usr/share/java when --java-lib is used. Defaults to the version found in the POM. -s --no-usj-versionless: Optional, don't install the versionless link in /usr/share/java. This flag is used only when the -l or --java-lib option is given. -d<path> --dest-jar=<path>: Optional, the destination for the real jar. The other places where the jar appears, in the repository or in the list of links, will be symlinks to this jar. Defaults to /usr/share/java/$name-$version.jar if --java-lib is used, otherwise the jar is installed in the versioned path in the Maven reposi- tory. -c<classifier> --classifier=<classifier>: Optional, the classifier for the jar. Empty by default. -v --verbose: show more information while running -n --no-act: don't actually do anything, just print the results --skip-clean-pom: don't clean the pom, assume that a previous action ran mh_cleanpom with the correct options. mh_cleanpom is run only to extract the groupId, artifactId and version of the jar See also: mh_installpom(1), mh_installsite(1) Maven Repo Helper version 1.7.1 January 2012 MAVEN(1)
All times are GMT -4. The time now is 02:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy