Re: MAKing bilf on Alpha
From: Bob Koehler (koehler_at_eisner.nospam.encompasserve.org)
Date: 10/30/03
- Next message: Rob Young: "Re: Concurrent users from Accounting"
- Previous message: P.Lj: "Re: EV7 and HPTC: Itanic isn't even safe there"
- In reply to: Didier Morandi: "MAKing bilf on Alpha"
- Next in thread: Nom de Plume: "Re: MAKing bilf on Alpha"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 30 Oct 2003 07:43:19 -0600
In article <3fa0f3d8$0$250$636a55ce@news.free.fr>, Didier Morandi <no@spam.com> writes:
> %CC-I-IMPLICITFUNC
A common occurance, but since it's an -I-, you can ignore it. Or you
for RTL functions you can track down the missing header file and #include
it, and for BILF functions you can write the missing header file and
include it. There's a lot of software out there which is sloppy
about this.
$ link bilf,sys$input:/opt
> sys$share:decc$crtl.exe/shareable
> %LINK-W-MULDEF, symbol DECC$STRDUP multiply defined
> in module DECC$SHR file SYS$COMMON:[SYSLIB]DECC$SHR.EXE;1
You should not have to explicitly reference decc$rtl.exe, try linking
BILF without the options file.
- Next message: Rob Young: "Re: Concurrent users from Accounting"
- Previous message: P.Lj: "Re: EV7 and HPTC: Itanic isn't even safe there"
- In reply to: Didier Morandi: "MAKing bilf on Alpha"
- Next in thread: Nom de Plume: "Re: MAKing bilf on Alpha"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]