02-05-2020
Patching might not work - because the patch may assume versions of the link libraries that are different from what you linked in your original build.
Do you have a sandbox to test the patch? Try it there first. We have a couple of virtual boxes that we can play with for testing. We refresh them using the current production version. -- after we trash them.
9 More Discussions You Might Find Interesting
1. Programming
Is there anyone who still uses CMI to connect to the legacy system , my c applications do uses the binaries and libraries for using the CMI functionality but i do not have access to the original source code , and since this is a very old stuff , i just could not get any source to get to knwo the... (0 Replies)
Discussion started by: dino_leix
0 Replies
2. IP Networking
Hello friends I'm running Redhat 9.0 with linux kernel 2.4.20-8 & have iptables version 1.2.7a & encountering a problem that I narrate down.
I need to apply patch to my iptable and netfilter for connection tracking and load balancing that are available in patch-o-matic distribution by netfilter.... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies
3. Red Hat
Hello,
I am using Redhat Linux Enterprise 4 AS.
To upgrade NFS, I had to browse the internet and finally I got the latest rpm https://rhn.redhat.com/errata/RHBA-2005-727.html
That was a time-consuming procedure. On Solaris, I am used to go to sunfreeware.sun.com and download the latest... (3 Replies)
Discussion started by: melanie_pfefer
3 Replies
4. Programming
I need help locating the tables that hold the demograhic data in this system on an AIX box. Does anyone know the path? (0 Replies)
Discussion started by: Chelcye
0 Replies
5. Slackware
Hi!
Let me introduce a project for find and download Slackware packages and browse Slackware repositories.
The site provides following features:
* Large, daily updated database with RPM, DEB, TGZ, TXZ packages for well-known repositories of the Slackware, Fedora, CentOS, RHEL, Debian,... (2 Replies)
Discussion started by: lystor
2 Replies
6. Solaris
I have a Solaris 10 OS having kernal patch level 138888-03 on several servers but recenlty I upgraded it into 142900-12 on some T-Series servers & v890 server after install them my syslog is increasing at a rate of 1GB on average on all servers . I believe its a bug, can somebody help me in... (1 Reply)
Discussion started by: sb200
1 Replies
7. What is on Your Mind?
Watched it. Major disappointment. (10 Replies)
Discussion started by: ni2
10 Replies
8. Ubuntu
Hi folks,
Ubuntu 9.04
I have an old box not running for years. I just dig it out from the store room. On running;
$ sudo aptitude update
......
......
Err http://hk.archive.ubuntu.com jaunty/main Packages
404 Not Found
Err http://hk.archive.ubuntu.com jaunty/restricted Packages
... (1 Reply)
Discussion started by: satimis
1 Replies
9. Solaris
Hi Folks,
Just a quick question here, about Legacy Zones. Well more about how to determine if you are actually in one, on logging into a legacy zone - is there a quick way of checking that?
Regards
Gull04 (7 Replies)
Discussion started by: gull04
7 Replies
LEARN ABOUT REDHAT
perlmachten
PERLMACHTEN(1) Perl Programmers Reference Guide PERLMACHTEN(1)
NAME
README.machten - Perl version 5 on Power MachTen systems
DESCRIPTION
This document describes how to build Perl 5 on Power MachTen systems, and discusses a few wrinkles in the implementation.
Compiling Perl 5 on MachTen
To compile perl under MachTen 4.1.4 (and probably earlier versions):
./Configure -de
make
make test
make install
This builds and installs a statically-linked perl; MachTen's dynamic linking facilities are not adequate to support Perl's use of dynami-
cally linked libraries. (See hints/machten.sh for more information.)
You should have at least 32 megabytes of free memory on your system before running the "make" command.
For much more information on building perl -- for example, on how to change the default installation directory -- see INSTALL.
Failures during "make test" on MachTen
op/lexassign.t
This test may fail when first run after building perl. It does not fail subsequently. The cause is unknown.
pragma/warnings.t
Test 257 fails due to a failure to warn about attempts to read from a filehandle which is a duplicate of stdout when stdout is attached
to a pipe. The output of the test contains a block comment which discusses a different failure, not applicable to MachTen.
The root of the problem is that Machten does not assign a file type to either end of a pipe (see stat), resulting, among other things
in Perl's "-p" test failing on file descriptors belonging to pipes. As a result, perl becomes confused, and the test for reading from
a write-only file fails. I am reluctant to patch perl to get around this, as it's clearly an OS bug (about which Tenon has been
informed), and limited in its effect on practical Perl programs.
Building external modules on MachTen
To add an external module to perl, build in the normal way, which is documented in ExtUtils::MakeMaker, or which can be driven automati-
cally by the CPAN module (see CPAN), which is part of the standard distribution. If you want to install a module which contains XS code (C
or C++ source which compiles to object code for linking with perl), you will have to replace your perl binary with a new version containing
the new statically-linked object module. The build process tells you how to do this.
There is a gotcha, however, which users usually encounter immediately they respond to CPAN's invitation to "install Bundle::CPAN". When
installing a bundle -- a group of modules which together achieve some particular purpose, the installation process for later modules in the
bundle tends to assume that earlier modules have been fully installed and are available for use. This is not true on a statically-linked
system for earlier modules which contain XS code. As a result the installation of the bundle fails. The work-around is not to install the
bundle as a one-shot operation, but instead to see what modules it contains, and install these one-at-a-time by hand in the order given.
AUTHOR
Dominic Dunlop <domo@computer.org>
DATE
Version 1.0.1 2000-03-27
perl v5.8.0 2003-02-18 PERLMACHTEN(1)