Kbase 17408: probuild on V.4 with 7.3E ld error: illegal option - -w
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
probuild on V.4 with 7.3E ld error: illegal option - -w
As of this writing, an attempt to probuild on certain UNIX V.4 platfor
ms may result in ld error: illegal option - -w. This is the result of
Progress building these executables on an NCR platform. As a result,
probuild produces an ldxxx script that uses CCNOPT options that may be
unique to NCR machines only. For example, on a DGUX platform:
CCNOPT contained -w1 -586 -Hon=use_frame_pointer -Hoff=optomize_FP
An attempt to execute this script on DGUX results in:
ux:ld error: illegal option - -w
The UNIX V.4 platforms where this might appear are those that use
Media Codes 83, 159 or 161. Those include DG/UX Intel, ICL Intel
(Unix Ware), NCR, SCO Unix Ware, Sun Solaris Intel and UNISYS.
Also be aware that probuild scripts may be using pathnames that do not
exist on your system, such as:
CISAMLIB=${CISAMLIB-"/gateways
cr/........"
A bug has been submitted to have this looked into (97-11-18-005)
18 Nov 97 JGH
12/19/97 Possible workaround: (This is meant as only a temporary fix)
When receiving this error you may go and edit you buildenv script
located in $DLC/probuild/eucapp directory. Specifically, you will
need to look at the line that contains the CCNOPT line:
CCNOPT contained -w1 -586 -Hon=use_frame_pointer -Hoff=optomize_FP
To edit this line I would recommend copying the original buildenv
scirpt and then remove the -w1 entry from the line. What may occur
is another resulting error that points to the 586 entry. You may
need to remove the -586 option as well. On the DG/UX 4.20 platform
we have also seen that an additional change to the SOCKLIB line:
SOCKLIB=${SOCKLIB-"-lform -lnsl -lsocket -lx -lelf -lresolv"}
The only option that needed to be changed was the -lx option. Once
these changes were removed we were able to successfully probuild.
Progress Software Technical Support Note # 17408