T.R | Title | User | Personal Name | Date | Lines |
---|
3674.1 | Uh? | AIMTEC::WICKS_A | WC94 Dream died when Bodin missed | Fri Dec 17 1993 17:08 | 11 |
| Allan,
But the .COM file copies OAFC$SERVER out to SYS$COMMON:[SYSEXE]
afterwards so does it matter where it was built.
Or maybe my hangover is preventing me from understanding what you are
asking?
Regards,
Andrew.D.Wicks
|
3674.2 | Well, I like to know whats happening... | COPCLU::COPLE4::GLARGAARD | Allan Glargaard, DS @DMO | Mon Dec 20 1993 08:25 | 14 |
| Re: .1, Andrew:
> But the .COM file copies OAFC$SERVER out to SYS$COMMON:[SYSEXE]
> afterwards so does it matter where it was built.
>
Well, I just think that following the guidelines should always put
the linked modules in the same place in the build area.
Modules ending up in unusual places always make me worry if the link
procedure picked up things from the correct place.
Best regards,
Allan
|
3674.3 | Yes i agree with that | AIMTEC::WICKS_A | WC94 Dream died when Bodin missed | Mon Dec 20 1993 16:52 | 22 |
| ALLAN,
Yes I understand that - the fact that the MUP relinks from where
ALL-IN-1 v2.4 relinked rather than where v3.0 relinks from does seem
a little silly. By the way I actually QARd this way back in june but I
can't post the answer I got from my good friends in Engineering since
there are ladies who read this conference!!!
I know only too well how crowded OA$BUILD can become when you have
customers who SET DEF to just OA$BUILD (so they get OA$SITE_BUILD_LLV)
Wordperfect who use OA$SITE_BUILD_SHARE: and then ALL-IN-1 and the MUP
using the other two.
Perhaps you like to make a wish for the PFR to have just one
build area?
Regards,
Andrew.D.Wicks
regards,
Andrew.D.Wicks
|
3674.4 | You didn't want to hear this, but... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Tue Dec 21 1993 13:07 | 4 |
| Actually, in order to support AXP, the PFR has lots *more* build
areas...
Graham
|