![HP eld Скачать руководство пользователя страница 200](http://html.mh-extra.com/html/hp/eld/eld_manual_165023200.webp)
Output Listings and Error Handling
eld Manual—527255-009
6-90
Error Messages
the official version of the public DLL registry automatically. If you specify this option, it
is your responsibility to provide
eld
with a correct public DLL registry file, and it is
beyond the scope of this manual to describe how this file should be created. If
eld
could not find it on its own, and you didn’t specify the -public_registry option, then there
is something wrong with your installation. The message told the name of the file that
eld
thought was the public DLL registry file. Perhaps that will help you figure out
what’s wrong.
Cause.
eld
uses the public DLL registry file to look up information about the operating
system and other standard DLLs. There are various ways that
eld
may find this file.
For example, if you are running
eld
on TNS/E then the operating system tells
eld
where the file is. In other cases,
eld
looks for it in an appropriate place, expecting it to
have the name “zreg”. Or, you can override these methods by explicitly telling
eld
where it is with the -public_registry option.
eld
did find a file by these methods, but the
file turned out not to have the proper structure for a public DLL registry file.
eld
parses the contents of the file into “statements”, which in turn can have “attributes”, and
this particular message comes out when
eld
detected a problem parsing the “file”
attribute after seeing the filename. The message tells the line number at which this
attribute began in the file.
Effect.
Fatal error (
eld
immediately stops without creating an output file).
Recovery.
If you specified the -public_registry option, are you sure you need to do
that? There usually is no need to give this option, because
eld
should be able to find
the official version of the public DLL registry automatically. If you specify this option, it
is your responsibility to provide
eld
with a correct public DLL registry file, and it is
beyond the scope of this manual to describe how this file should be created. If
eld
could not find it on its own, and you didn’t specify the -public_registry option, then there
is something wrong with your installation. The message told the name of the file that
eld
thought was the public DLL registry file. Perhaps that will help you figure out
what’s wrong.
Cause.
eld
uses the public DLL registry file to look up information about the operating
system and other standard DLLs. There are various ways that
eld
may find this file.
For example, if you are running
eld
on TNS/E then the operating system tells
eld
where the file is. In other cases,
eld
looks for it in an appropriate place, expecting it to
have the name “zreg”. Or, you can override these methods by explicitly telling
eld
where it is with the -public_registry option.
eld
did find a file by these methods, but the
file turned out not to have the proper structure for a public DLL registry file.
eld
parses
the contents of the file into “statements”, which in turn can have “attributes”, and this
particular message comes out when
eld
detected a problem parsing the “file” attribute
1545 Bad syntax for the file attribute on line <number> of
<filename>.
1546 Filename expected for 'file' attribute on line <number>
of <filename>.
Содержание eld
Страница 4: ......
Страница 8: ...Contents eld Manual 527255 009 iv ...
Страница 12: ...What s New in This Manual eld Manual 527255 009 viii Changes to the 527255 005 Manual ...
Страница 34: ...Introduction to eld eld Manual 527255 009 1 14 Example of Use ...
Страница 54: ...eld Input and Output eld Manual 527255 009 2 20 Using Archives ...
Страница 98: ...Other eld Processing eld Manual 527255 009 4 20 Merging Source RTDUs ...
Страница 242: ...Output Listings and Error Handling eld Manual 527255 009 6 132 Glossary of Errors ...