07-10-2008
HPUX 11.00 ?
Well not supported anymore (well officially anyway...)
So my advice would be make sure you have a good ignite tape done before you attempt and go and look if you have no patch requirements .
If you are up to date with your patches, there should not be any problem...(Is it for Oracle needs?)
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I'm running on UNIX with Solaris. I need to change the Timezone on the box and was going to make the changes to the files and then reboot the box.
Someone warned me that this method should not be used and that a util (unconfig.sys I think it was) should be used to make the changes.
Any ideas... (2 Replies)
Discussion started by: Lextar
2 Replies
2. HP-UX
Hello,
New to the board. Experienced solaris admin, unexperienced HP admin.
I'm trying to install the acc compiler package B3913DB off of the HP-UX 11.0 application software CD. I have the cd mounted on another system, and nfs mounted as /mnt on the HP-UX box.
I don't have a whole lot... (3 Replies)
Discussion started by: tb0ne
3 Replies
3. HP-UX
- I ran the command:
swinstall -p -v -s /home/garybowd/aCC-11.11-3.55ws.depot
- I selected the S800 Package (I also tried this with the S700, but i'm pretty sure our server is S800)
- I selected install, and these are the errors i got:
ERROR: Exclude ... (1 Reply)
Discussion started by: gbowdridge
1 Replies
4. HP-UX
I got this error while compiling in aCC compiler.
Error 173: "/opt/aCC/include_std/limits", line 694 # Redefined symbol
'numeric_limits<int>'; previously defined at
.
_RWSTD_SPECIALIZE_LIMITS (bool, int, _RWSTD_BOOL)
^^^^^^^^^^^^^^^^^^^^^^^^
Error... (2 Replies)
Discussion started by: onlyforforum
2 Replies
5. HP-UX
Hi,
Can anybody guide as to whether the aCC compiler for RISC (9000/785) be used with ia64 processor? (2 Replies)
Discussion started by: slash_blog
2 Replies
6. HP-UX
hello,
i'm now working on a traduction of a makefile from HP_UX environnement to IBM_AIX environnement, so , first of all i need help about aCC compiler and the meaning of each option of compilation, and if possible its equivalent in AIX
it's urgent, any help will be highly appreciated (0 Replies)
Discussion started by: kingmastersimo
0 Replies
7. HP-UX
We've just moved to a new iTanium development system at my place of business, as the previous one is going to be diverted to other uses. Our product uses a locally produced library built from over 2,300 C++ sources.
We just noticed that our libraries are 2/3s smaller on the new system than they... (1 Reply)
Discussion started by: Mark F. Cook
1 Replies
8. Programming
To make a programming language you need a compiler, so what was the first programming language and how was is created if you need the compiler first?
The compiler itself is considered as a high language comparing to the machine! since the compiler is not created in 1's and 0's...
Eventhough i... (12 Replies)
Discussion started by: f.ben.isaac
12 Replies
9. AIX
In our operating procedures, if a workstation has a space problem in the /var filesystem, one of the most frequent case we were told is the size of the /var/adm/wtmp file.
Someone once told me it is dangerous to do this. Is it ?
I cannot say for certain that whomever wrote that procedure is... (2 Replies)
Discussion started by: Browser_ice
2 Replies
10. UNIX for Advanced & Expert Users
Our computing enviornment consists for Linux, Solaris , AIX, Windows. /etc/resolv.conf file of each *nix has two entries. When the 2nd one goes down we are seeing impacts on AIX hosted services. We are breaking our head, to no avail yet. We have not seen any impact on non-AIX hosted services. While... (12 Replies)
Discussion started by: broy32000
12 Replies
LEARN ABOUT OSX
svk::command::patch
SVK::Command::Patch(3) User Contributed Perl Documentation SVK::Command::Patch(3)
NAME
SVK::Command::Patch - Manage patches
SYNOPSIS
patch --ls [--list]
patch --cat [--view] PATCHNAME
patch --regen [--regenerate] PATCHNAME
patch --up [--update] PATCHNAME
patch --apply PATCHNAME [DEPOTPATH | PATH] [-- MERGEOPTIONS]
patch --rm [--delete] PATCHNAME
OPTIONS
--depot DEPOTNAME : operate on a depot other than the default one
DESCRIPTION
To create a patch, use "commit -P" or "smerge -P". To import a patch that's sent to you by someone else, just drop it into the "patch"
directory in your local svk repository. (That's usually "~/.svk/".)
svk patches are compatible with GNU patch. Extra svk-specific metadata is stored in an encoded chunk at the end of the file.
A patch name of "-" refers to the standard input and output.
INTRODUCTION
"svk patch" command can help out on the situation where you want to maintain your patchset to a given project. It is used under the
situation that you have no direct write access to remote repository, thus "svk push" cannot be used.
Suppose you mirror project "foo" to "//mirror/foo", create a local copy on "//local/foo", and check out to "~/dev/foo". After you've done
some work, you type:
svk commit -m "Add my new feature"
to commit changes from "~/dev/foo" to "//local/foo". If you have commit access to the upstream repository, you can submit your changes
directly like this:
svk push //local/foo
Sometimes, it's useful to send a patch, rather than submit changes directly, either because you don't have permission to commit to the
upstream repository or because you don't think your changes are ready to be committed.
To create a patch containing the differences between "//local/foo" and "//mirror/foo", use this command:
svk push -P Foo //local/foo
The "-P" flag tells svk that you want to create a patch rather than push the changes to the upstream repository. "-P" takes a single flag:
a patch name. It probably makes sense to name it after the feature implemented or bug fixed by the patch. Patch files you generate will be
created in the "patch" subdirectory of your local svk repository.
Over time, other developers will make changes to project "foo". From time to time, you may need to update your patch so that it still
applies cleanly.
First, make sure your local branch is up to date with any changes made upstream:
svk pull //local/foo
Next, update your patch so that it will apply cleanly to the newest version of the upstream repository:
svk patch --update Foo
Finally, regenerate your patch to include other changes you've made on your local branch since you created or last regenerated the patch:
svk patch --regen Foo
To get a list of all patches your svk knows about, run:
svk patch --list
To see the current version of a specific patch, run:
svk patch --view Foo
When you're done with a patch and don't want it hanging around anymore, run:
svk patch --delete Foo
To apply a patch to the repository that someone else has sent you, run:
svk patch --apply - < contributed_feature.patch
perl v5.10.0 2008-08-04 SVK::Command::Patch(3)