When an application requires a minimum perl module version which is not provided by installed RPM, it can be upgraded manually.
For instance, it is the case of amavis (see create a full and secured emails server), when upgrading some perl rpm packages (perl-CPAN for instance).
To upgrade CPAN perl module manually, opens a perl shell:
perl -MCPAN -e shell
Then request the "install" of the newest available perl module version. For instance:
install File::Temp
sharing knowledge earned into design/development/technical delicate and/or difficult situations ...
Labels
Gnu/Linux
(95)
Administration
(83)
StorageHardware
(17)
Programming
(16)
WebBrowser
(15)
General
(11)
GNU/Bash
(7)
Solaris
(7)
Virtualization
(7)
C
(6)
Domotics
(6)
Musics
(5)
Raspberry
(5)
Desktop
(4)
Java
(4)
VersionControlSystems
(4)
ArtificialIntelligence
(2)
Optimization
(2)
multimedia
(2)
Arduino
(1)
Electronics
(1)
LTS
(1)
MacOS
(1)
Mechanics
(1)
Processing
(1)
Robotics
(1)
Ubuntu
(1)
Upgrade
(1)
ez-robot
(1)
30 April 2008
Define the current version of a perl module
To get the current version of an installed perl module, the following command can be used:
perl -le 'use MODULE_NAME; print MODULE_NAME->VERSION'
With MODULE_NAME the name of the wished perl module.
For instance with File::Temp it gives:
perl -le 'use File::Temp; print File::Temp->VERSION'
perl -le 'use MODULE_NAME; print MODULE_NAME->VERSION'
With MODULE_NAME the name of the wished perl module.
For instance with File::Temp it gives:
perl -le 'use File::Temp; print File::Temp->VERSION'
25 April 2008
Get the list of gcc defined macro after preprocessing
It various situation, it is very useful to get the list of all defined maco after gcc preprocessing.
Particularly when porting C/C++ source code to another OS/Architecture to know what macro to use to identify it.
A simple way is to use gcc with the following options:
-E to end after preprocessing step,
-dM to print all defined macros.
For instance to known the "default" macros, use those options with a simple source code file "test.c" defining a main function:
gcc -E -dM test.c
Particularly when porting C/C++ source code to another OS/Architecture to know what macro to use to identify it.
A simple way is to use gcc with the following options:
-E to end after preprocessing step,
-dM to print all defined macros.
For instance to known the "default" macros, use those options with a simple source code file "test.c" defining a main function:
gcc -E -dM test.c
23 February 2008
Fix empty /var/log/boot.log file issue
The local7 facility is used to write into the /var/log/boot.log file.
But since the Fedora core 4, the system has been disabled waiting for a new generation system which does not seem to be available yet (see this bug report and this one)
A quick way to fix the empty /var/log/boot.log file, is to edit the /etc/rc.d/init.d/functions file.
Into the success, failure, passed and warning functions, you can add a line like the following, just before the return instruction:
/usr/bin/logger -p local7.info "$1"
It works but each time the initscripts package is updated, it is needed to edit the file ...
But since the Fedora core 4, the system has been disabled waiting for a new generation system which does not seem to be available yet (see this bug report and this one)
A quick way to fix the empty /var/log/boot.log file, is to edit the /etc/rc.d/init.d/functions file.
Into the success, failure, passed and warning functions, you can add a line like the following, just before the return instruction:
/usr/bin/logger -p local7.info "$1"
It works but each time the initscripts package is updated, it is needed to edit the file ...
Make Red Hat Graphical Boot detailed
There is unfortunately no configuration file allowing to switch on/off the details of Red Hat Graphical Boot.
Anyway, for it to be detailed, the /etc/rc.d/init.d/functions can be edited:
- simply add --details=yes into the update_boot_stage function on the line using the /usr/bin/rhgb-client.
It works but each time the initscripts package is updated, it is needed to edit the file ...
Anyway, for it to be detailed, the /etc/rc.d/init.d/functions can be edited:
- simply add --details=yes into the update_boot_stage function on the line using the /usr/bin/rhgb-client.
It works but each time the initscripts package is updated, it is needed to edit the file ...
Subscribe to:
Posts (Atom)