08-05-2004 09:30 PM
$make -f Makefile
Fort77: Cannot execute linker /usr/ccs/bin/ld while linking
*** Error exit code 1
Makefile hasn't changed in months.
Any ideas for a non ex developer sysadmin?
Solved! Go to Solution.
08-05-2004 09:41 PM
-r-xr-xr-x 1 bin bin 593920 Feb 1 2001 /usr/ccs/bin/ld
Does it look like this
08-05-2004 09:45 PM
if the ld doesn't look like this(as Steve said) copt the ld from other HP machine(where it is working) and change the permissions and owner/group.
(i had faced this problem long back and this was the solution i found)
08-05-2004 10:59 PM
ll -d / /usr /usr/ccs /usr/ccs/bin
drwxrwxrwx 37 root root 2048 Aug 4 15:59 /
dr-xr-xr-x 24 bin bin 1024 Jun 11 08:47 /usr
dr-xr-xr-x 5 bin bin 96 Jun 16 2001 /usr/ccs
dr-xr-xr-x 2 bin bin 1024 Jun 16 2001 /usr/ccs/bin
HP aC++ B3910B A.03.27 Classic Iostream Library
HP aC++ B3910B A.03.27 Language Support Library
ld_msgs.cat: $Revision: 1.85 $
92453-07 linker command s800.sgs ld PA64 B.11.25 REL 001129
08-05-2004 11:05 PM
drwxr-xr-x 20 root root 4096 Jul 20 10:20 /
dr-xr-xr-x 32 bin bin 1024 Mar 5 2001 /usr
dr-xr-xr-x 5 bin bin 1024 Feb 26 2001 /usr/ccs
dr-xr-xr-x 2 bin bin 1024 Feb 26 2001 /usr/ccs/bin
92453-07 linker linker ld B.10.37 991028
(older version possibly)
On further investigation, if the user rlogins to the machine, it builds, if they log in via the console, it doesn't!
What sort of environment condition could affect it?
08-06-2004 01:26 AM
- add -v & -Wl,-v to the fortran compiler command line to see what options it is calling ld with (it will probably tell you what is exactly happening too)
- run ld manually and see what happens
- check if user's login scripts have anything set differently for different terminal cases
08-06-2004 02:26 AM
env > /tmp/1
set >> /tmp/1
env > /tmp/2
set >> /tmp/2
diff /tmp/1 /tmp/2