|o||Using your favourite browser open the DSM management page and start the Package Center.|
|o||If you want to smoke test Perl, install Perl.|
|o||In Settings, add the following Package Sources:|
|o||Still in Settings, in Channel Update, select Beta Channel.|
|o||Press Refresh. In the left panel the item Community will appear. Click it. Select Bootstrap Installer Beta and install it.|
Likewise, install iPKGui Beta.
The application window should now show an icon for iPKGui.
Start iPKGui. Install the packages make, gcc and coreutils.
If you want to smoke test Perl, install patch.
Here the actual architecture of the Synology system matters. You have to find out where the gcc libraries have been installed. Look in /opt for a directory similar to arm-none-linux-gnueab or powerpc-linux-gnuspe. In the instructions below Ill use powerpc-linux-gnuspe as an example.
|o||On the DSM management page start the Control Panel.|
|o||Click Terminal, and enable SSH service.|
|o||Close Terminal and the Control Panel.|
|o||Open a shell on the Synology using ssh and become root.|
|o||Execute the following commands:|
When the build environment has been set up, building and testing Perl is straightforward. The only thing you need to do is download the sources as usual, and add a file Policy.sh as follows:
# Administrivia. perladmin="email@example.com" # Install Perl in a tree in /opt/perl instead of /opt/bin. prefix=/opt/perl # Select the compiler. Note that there is no cc alias or link. cc=gcc # Build flags. ccflags="-DDEBUGGING" # Library and include paths. libpth="/lib" locincpth="/opt/include" loclibpth="/lib"
You may want to create the destination directory and give it the right permissions before installing, thus eliminating the need to build Perl as a super user.
In the directory where you unpacked the sources, issue the familiar commands:
./Configure -des make make test make install
No known problems yet
Error message No error definitions found. This error is generated when it is not possible to find the local definitions for error codes, due to the uncommon structure of the Synology file system.
This error was fixed in the Perl development git for version 5.19, commit 7a8f1212e5482613c8a5b0402528e3105b26ff24.
ext/DynaLoader/t/DynaLoader.t One subtest fails due to the uncommon structure of the Synology file system. The file /lib/glibc.so is missing.
If building completes successfully, you can set up smoke testing as described in the Test::Smoke documentation.
For smoke testing you need a running Perl. You can either install the Synology supplied package for Perl 5.8.6, or build and install your own, much more recent version.
Note that I could not run successful smokes when initiated by the Synology Task Scheduler. I resorted to initiating the smokes via a cron job run on another system, using ssh:
ssh nas1 wrk/Test-Smoke/smoke/smokecurrent.sh
When local patches are applied with smoke testing, the test driver will automatically request regeneration of certain tables after the patches are applied. The Synology supplied Perl 5.8.6 (at least on the DS413) <B>is NOT capableB> of generating these tables. It will generate opcodes with bogus values, causing the build to fail.
You can prevent regeneration by adding the setting
flags => 0,
to the smoke config, or by adding another patch that inserts
exit 0 if $] == 5.008006;
in the beginning of the regen.pl program.
The above procedure describes a basic environment and hence results in a basic Perl. If you want to add additional libraries to Perl, you may need some extra settings.
For example, the basic Perl does not have any of the DB libraries (db, dbm, ndbm, gdsm). You can add these using iPKGui, however, you need to set environment variable LD_LIBRARY_PATH to the appropriate value:
This setting needs to be in effect while Perl is built, but also when the programs are run.
March 2015, for Synology DSM 5.1.5022.
Johan Vromans <firstname.lastname@example.org> H. Merijn Brand <email@example.com>
|perl v5.22.1||PERLSYNOLOGY (1)||2015-10-17|