Hi Graham,
Yes, I did run that script as root since I am setting up this machine for multiple users to run simultaneously, but only wanted one Starlink install. In this case, it was preferable to install Starlink outside of any one user's home folder, which lead to permissions problems installing as a standard user.
The only change I made to the build-modules.sh script was to remove the trailing / on line 7 (which I ran from bash):
perlroot=${STARLINK_DIR}/Perl/bin/
since that caused a double slash folder name issue when concatenated with the definition of starperl on line 10:
starperl=${perlroot}/perl
It does look to me like certain perl modules have been placed elsewhere as you suggest. On another system where Starlink was installed under a home folder under a standard user account, there were no such issues. The required module can be found there where expected under:
/home/matt/software/star/Perl/lib/perl5/site_perl/5.16.1/x86_64-linux
On the new system, where Starlink is installed outside a home folder, and build-modules.sh was run as root, the DateTime.pm is not to be found in the expected perl @INC path, but is instead in the usr/bin/cpanm subfolders. I did have cpanminus already installed on that system as well, so in combination with running as root, this may also have contributed to the unexpected conflict with the Starlink install.
Cheers,
Matt
On 2013-01-15, at 1:21 PM, Graham Bell wrote:
>> Here is my output from my latest run of build-modules.sh, and yes, DateTime is installed.
>>
>> EPHIALTES perlmods # ./build-modules.sh
>
> Hello,
>
> Does the # indicate that you're doing that as root? That would mean that if you ran the wrong Perl, you would be able to scribble over your system Perl directories rather than installing into the Starlink Perl directory.
>
>> Skipped mangling interpreter for Perl/bin/autoastrom, not found.
>> Skipped mangling interpreter for Perl/bin/sourceplot, not found.
>
> That shouldn't happen as your build log indicated that SourcePlot had been installed, so it looks like something is in the wrong place.
>
> Did you mention that you had modified build-modules.sh? If so, could I have a look at the changes?
>
> Best regards,
> Graham
|