Sponsored Content
Full Discussion: Java and Javac problems
Operating Systems Solaris Java and Javac problems Post 302714953 by jlliagre on Saturday 13th of October 2012 09:21:07 AM
Old 10-13-2012
Quote:
Originally Posted by jim mcnamara
That is an LD_LIBRARY_PATH issue.
What makes you feel it is ?
LD_LIBRARY_PATH is unset by default under Solaris and should stay that way unless inside specific wrapper scripts.
Quote:
Then in your code script to run your new java code try:
Code:
export LD_LIBRARY_PATH=usr/jdk/instances/jdk1.7.0/:${LD_LIBRARY_PATH}

This is both incorrect (you are missing a leading slash) and useless (there are no libraries in the jdk1.7.0 directory).

---------- Post updated at 15:06 ---------- Previous update was at 15:01 ----------

Quote:
Originally Posted by Fingerz
So can anyone point me to the logic behind it all, I mean theres has to be some kind structure yes?
Sure there is a structure.
If you want the jdk1.7 to be your default java environment, just put both of these lines in your .profile or .bash_profile
Code:
PATH=/usr/jdk/instances/jdk1.7.0/bin:$PATH
export JAVA_HOME=/usr/jdk/instances/jdk1.7.0

logout and login again and you are set.

---------- Post updated at 15:21 ---------- Previous update was at 15:06 ----------

Quote:
Originally Posted by jim mcnamara
Windows is derived from UNIX
Windows has very little in common with Unix and is quite unlikely to include anything derived from Unix code outside some tcp/ip utilities borrowed from BSD.
 

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

piping with javac command

how to i use javac on a file after searching for it? example: find . -name '*.java' -size -24 -links -2 -atime -4 what would happen if "find" found >1 .java files? also, i'm a little confused on the -size property... mix up between -2 and +2... what's the difference? (1 Reply)
Discussion started by: quipy
1 Replies

2. UNIX for Dummies Questions & Answers

Installing Java Problems

Hello, When i attempt to install Java. I get this error code Can someone tell me what im doing wrong. (2 Replies)
Discussion started by: Fob Upset
2 Replies

3. Programming

set javac classpath

I have several jar files in a specific folder, but I can't get javac to understand it. How do I set the classpath for javac. It is NOT the same classpath as the java command. And it's not enough with one jar file. I have several. (1 Reply)
Discussion started by: locoroco
1 Replies
SHELL-QUOTE(1p) 					User Contributed Perl Documentation					   SHELL-QUOTE(1p)

NAME
shell-quote - quote arguments for safe use, unmodified in a shell command SYNOPSIS
shell-quote [switch]... arg... DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands or files with embedded white space or shell globbing characters safely. Here are a few examples. EXAMPLES
ssh preserving args When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and passes them to "$SHELL -c". This doesn't work as intended: ssh host touch 'hi there' # fails It creates 2 files, hi and there. Instead, do this: cmd=`shell-quote touch 'hi there'` ssh host "$cmd" This gives you just 1 file, hi there. process find output It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote: eval set -- `find -type f -print0 | xargs -0 shell-quote --` debug shell scripts shell-quote is better than echo for debugging shell scripts. debug() { [ -z "$debug" ] || shell-quote "debug:" "$@" } With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can. save a command for later shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are things the user can't pass through), you can do something like this: user_switches= while [ $# != 0 ] do case x$1 in x--pass-through) [ $# -gt 1 ] || die "need an argument for $1" user_switches="$user_switches "`shell-quote -- "$2"` shift;; # process other switches esac shift done # later eval "shell-quote some-command $user_switches my args" OPTIONS
--debug Turn debugging on. --help Show the usage message and die. --version Show the version number and exit. AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions. AUTHOR
Roderick Schertler <roderick@argon.org> perl v5.8.4 2005-05-03 SHELL-QUOTE(1p)
All times are GMT -4. The time now is 12:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy