On Sat, 2007-09-22 at 16:33 +0100, michael bane wrote:> I have built rsync on IA64 using Intel's 'icc' compiler and can
run the
> rsync executable interactively but when attempting to run under
> 'crontab' I get the following error:
>
> + /home/horace/mccssmb2/src/rsync-2.6.9/rsync -z --partial -v --progress
> --recursive --stats --times --links
> --exclude-from=/project/horace/mcc101/.rsync-EXCLUDE
> --timeout=1200 /project/horace/mcc101
> mkb@veri.phy{}:/media/disk/BACKUPS/horace/project
> /home/horace/mccssmb2/src/rsync-2.6.9/rsync: error while loading shared
> libraries: libimf.so.6: cannot open shared object file: No such file or
> directory
>
> Any ideas? A system-proved rsync runs okay.
>
> More info on these executable indicates they are built similarly, I
> think:
>
> ~/bin$ file /usr/bin/rsync
> /usr/bin/rsync: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), for
> GNU/Linux 2.4.0, dynamically linked (uses shared libs), not stripped
>
> ~/bin$ file /home/horace/mccssmb2/src/rsync-2.6.9/rsync
> /home/horace/mccssmb2/src/rsync-2.6.9/rsync: ELF 64-bit LSB executable,
> IA-64, version 1 (SYSV), for GNU/Linux 2.4.0, dynamically linked (uses
> shared libs), not stripped
>
> I'm unsure how to determine which C/C++ compiler was used to build the
> system executable...
>
To answer myself, it's because LD_LIBRARY_PATH (under crontab) doesn't
include the relevant Intel compiler paths