Sponsored Content
Full Discussion: find jdk 1.3.1
Top Forums UNIX for Dummies Questions & Answers find jdk 1.3.1 Post 302139658 by madmat on Monday 8th of October 2007 12:25:11 PM
Old 10-08-2007
find jdk 1.3.1

Hello,

I try to find the file jdk-1.3.1_03-fcs.rpm (pre-requisite for Oracle Applications 11.5.8) for Linux x86 but it doesn't available anywhere...

Maybe here, somebody have it ? Smilie

Rgds
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

instfix lslpp JDK

Hi, some questions please : 1- what does do instfix ? 2- what does lslpp -l ? 3- how to verify JDK version on a UNIX server (AIX) ? Many thanks before. (2 Replies)
Discussion started by: big123456
2 Replies

2. UNIX for Dummies Questions & Answers

JDK Installation

I'm trying to install JDK (Java Development tools) and i get this: WARNING: The <SUNWj6dev> package "JDK 6.0 Dev. Tools (1.6.0)" is a prerequisite package and should be installed. WARNING: The <SUNWj6rtx> package "JDK 6.0 64-bit Runtime Env. (1.6.0)" is a prerequisite package and should be... (0 Replies)
Discussion started by: idan_cn
0 Replies

3. Red Hat

jdk installation question

hi, i just "yum install jdk*.i386" and installation was complete without any error. however, i tried to #javac helloworld " and javac is not found in the $PATH. i tried to locate it and didn't find it. would anyone shed some light on where the "yum install" installed my jdk to? where can i find... (0 Replies)
Discussion started by: k2k
0 Replies

4. Solaris

Jdk 1.6 Installtion

How to install the jdk 1.6 in the solaris sparc 10 64bit. Any patch is required for jdk 1.6 for solaris (2 Replies)
Discussion started by: saktiviji
2 Replies

5. Solaris

How to start tomcat with 2 jdk?

Current platform: Sun OS 5.9 Solaris isainfo -v 64-bit sparcv9 applications 32-bit sparc applications Problem: Fail to start tomcat server ps -ef | grep tomcat nothing displays... Steps: Installed jakarta-tomcat-5.0.30 Installed jdk 1.6 and set path in profile... (11 Replies)
Discussion started by: sbox
11 Replies

6. Programming

JDK 1.6 error - simple

Please look at below and let me know if some one has solution for this issue. when the code is trying to import the class directly an error is displayed saying " '.' expected ". I tires with JDK 1.5 , JDK 1.3 and JDK 1.4 , results are same.. If this is resolved with any updated version of... (3 Replies)
Discussion started by: shafi2all
3 Replies

7. Ubuntu

JDK path

Hello, I have installed the default JDK from Software centre, but when i type whereis JDK on the terminal.. i don't see any path :mad: i need JDk to install a tool ... Hurry!!! please HELP:confused::confused: (4 Replies)
Discussion started by: paramad
4 Replies

8. Programming

Installing jdk

I just downloaded jdk, but am unsure about updating the PATH variable. What steps should I follow ? Evidently I have to/prefer to be logged in as root to install jdk on my UBUNTU 10.04 linux.BTW, this question needs to go in another forum, but out of disuse I have forgotten my root... (1 Reply)
Discussion started by: sundaresh
1 Replies

9. HP-UX

jdk

How can i see if jdk is installed or not on my system. I am on HP UX B.11.31 (3 Replies)
Discussion started by: bang_dba
3 Replies

10. UNIX and Linux Applications

Version of Jdk on my machine

Hello, Please, i ask what command linux used to know the version of jdk installed on my machine ? Thank you so much. (8 Replies)
Discussion started by: chercheur857
8 Replies
build(1)						      General Commands Manual							  build(1)

NAME
build - build SuSE Linux RPMs in a chroot environment SYNOPSIS
build [--clean|--no-init] [--rpms path1:path2:...] [--arch arch1:arch2:...] [--root buildroot] [specfile|srcrpm] build --help build --verify DESCRIPTION
build is a tool to build SuSE Linux RPMs in a safe and clean way. build will install a minimal SuSE Linux as build system into some direc- tory and will chroot to this system to compile the package. This way you don't risk to corrupt your working system (due to a broken spec file for example), even if the package does not use BuildRoot. build searches the spec file for a BuildRequires: line; if such a line is found, all the specified rpms are installed. Otherwise a selec- tion of default packages are used. Note that build doesn't automatically resolve missing dependencies, so the specified rpms have to be sufficient for the build. If a spec file is specified on the command line, build will use this file and all other files in the directory for building the package. If a srcrpm is specified, build automatically unpacks it for the build. If neither is given, build will use all the specfiles in the current directory. OPTIONS
--clean remove the build system and reinitialize it from scratch. --no-init skip the build system initialization and start with build immediately. --list-state list rpms that would be used to create a fresh build root. Does not create the build root or perform a build. --rpms path1:path2:path3... Where build can find the SuSE Linux RPMs needed to create the build system. This option overrides the BUILD_RPMS environment vari- able. --arch arch1:arch2:arch3... What architectures to select from the RPMs. build automatically sets this to a sensible value for your host if you don't specify this option. --root buildroot Specifies where the build system is set up. Overrides the BUILD_ROOT enviroment variable. --useusedforbuild Tell build not to do dependency expansion, but to extract the list of packages to install from "# usedforbuild" lines or, if none are found, from all "BuildRequires" lines. This option is useful if you want to re-build a package from a srcrpm with exactly the same packages used for the srcrpm build. --norootforbuild --help Print a short help text. --verify verify the files in an existing build system. .spec FILE OPTIONS The build command interprets some special control comments in the specfile: # norootforbuild # needsrootforbuild build uses either user root or user abuild in the build system to do the build. For non-SUSE distros as well as since SUSE 10.2, the default build user is abuild. For 10.2 and before, the default build user is root. These two flags in the spec file allow to deviate from the defaults and force-set the build user to abuild and root (for # norootforbuild and # needsrootforbuild respec- tively. # needsbinariesforbuild provide the binary rpms that have been used to set up the build root in /.build.binaries within the build root. ENVIRONMENT
BUILD_ROOT The directory where build should install the chrooted build system. "/var/tmp/build-root" is used by default. BUILD_RPMS Where build can find the SuSE Linux RPMs. build needs them to create the build system. "/media/dvd/suse" is the default value which will do the trick if you have the SuSE Linux DVD mounted. BUILD_RPM_BUILD_STAGE The rpm build stage (-ba, -bb, ...). This is just passed through to rpm, check the rpm manpage for a complete list and descrip- tions. "-ba" is the default. You can use this to add more options to RPM. SEE ALSO
rpm(1), Maximum RPM: http://www.rpm.org/max-rpm/ cross distribution packaging: http://en.opensuse.org/Build_Service/cross_distribution_package_how_to SUSE packaging standards and guidelines: http://en.opensuse.org/Packaging (c) 1997-2008 SuSE Linux AG Nuernberg, Germany build(1)
All times are GMT -4. The time now is 06:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy