 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Ed Mulroy [TeamB] Guest
|
Posted: Sun Jan 25, 2004 8:21 pm Post subject: Re: Cannot compile with #include <iostream> |
|
|
| Quote: | I am working on a simple command line project, but
every time I include iostream, I get a long list of errors. ...
|
There must have been a cut and paste problem. The message you posted does
not show any errors.
.. Ed
| Quote: | John wrote in message
news:40140baa$1 (AT) newsgroups (DOT) borland.com...
|
|
|
| Back to top |
|
 |
John Guest
|
Posted: Sun Jan 25, 2004 8:41 pm Post subject: Re: Cannot compile with #include <iostream> |
|
|
Ed Mulroy [TeamB] wrote:
| Quote: | I am working on a simple command line project, but
every time I include iostream, I get a long list of errors. ...
There must have been a cut and paste problem. The message you posted does
not show any errors.
. Ed
John wrote in message
news:40140baa$1 (AT) newsgroups (DOT) borland.com...
My mistake. These are the first few errors: |
Error E2451 c:Johnclasscsccsc230include130iosfwd 68: Undefined
symbol 'mbstate_t'
Error E2299 c:Johnclasscsccsc230include130iosfwd 68: Cannot
generate template specialization from 'fpos<_St>'
Error E2040 c:Johnclasscsccsc230include130iosfwd 68: Declaration
terminated incorrectly
Error E2257 c:Johnclasscsccsc230include130iosfwd 69: , expected
Error E2139 c:Johnclasscsccsc230include130iosfwd 77: Declaration
missing ;
|
|
| Back to top |
|
 |
Ed Mulroy [TeamB] Guest
|
Posted: Sun Jan 25, 2004 9:43 pm Post subject: Re: Cannot compile with #include <iostream> |
|
|
The error message shows this path to the header file:
c:Johnclasscsccsc230include130iosfwd
iosfwd.h is a header file supplied by the compiler but the error message you
show indicates that you are using a different header file of the same name,
one specific to you. Things are more likely to work better if the compiler
supplied header files not replaced by other files with the same names.
When you did the compiler installation did you create the bcc32.cfg and
ilink32.cfg configuration files in the compiler's BIN directory as it says
to do in the readme.txt file? If not, please create them now. The file
contents are shown below using the default installation path. If you used a
different path then substitute that path for what is shown below. Note that
the -I is a capital 'i' and not a lower case 'L'.
Contents of c:borlandbcc55binbcc32.cfg, 2 text lines
-Ic:borlandbcc55include
-Lc:borlandbcc55lib
Contents of c:borlandbcc55binilink32.cfg, 1 text line
-Lc:borlandbcc55lib
Hopefully when the default path to the header files is specified in the
bcc32.cfg file it will cause the compiler supplied headers to be found
first.
.. Ed
| Quote: | John wrote in message
news:40142a1d$1 (AT) newsgroups (DOT) borland.com...
My mistake. These are the first few errors:
Error E2451 c:Johnclasscsccsc230include130iosfwd 68: Undefined
symbol 'mbstate_t'
Error E2299 c:Johnclasscsccsc230include130iosfwd 68: Cannot
generate template specialization from 'fpos<_St>'
Error E2040 c:Johnclasscsccsc230include130iosfwd 68: Declaration
terminated incorrectly
Error E2257 c:Johnclasscsccsc230include130iosfwd 69: , expected
Error E2139 c:Johnclasscsccsc230include130iosfwd 77: Declaration
missing ;
|
|
|
| Back to top |
|
 |
John Guest
|
Posted: Sun Jan 25, 2004 9:58 pm Post subject: Re: Cannot compile with #include <iostream> |
|
|
Ed Mulroy [TeamB] wrote:
| Quote: | The error message shows this path to the header file:
c:Johnclasscsccsc230include130iosfwd
iosfwd.h is a header file supplied by the compiler but the error message you
show indicates that you are using a different header file of the same name,
one specific to you. Things are more likely to work better if the compiler
supplied header files not replaced by other files with the same names.
When you did the compiler installation did you create the bcc32.cfg and
ilink32.cfg configuration files in the compiler's BIN directory as it says
to do in the readme.txt file? If not, please create them now. The file
contents are shown below using the default installation path. If you used a
different path then substitute that path for what is shown below. Note that
the -I is a capital 'i' and not a lower case 'L'.
Contents of c:borlandbcc55binbcc32.cfg, 2 text lines
-Ic:borlandbcc55include
-Lc:borlandbcc55lib
Contents of c:borlandbcc55binilink32.cfg, 1 text line
-Lc:borlandbcc55lib
Hopefully when the default path to the header files is specified in the
bcc32.cfg file it will cause the compiler supplied headers to be found
first.
. Ed
|
I did set up the cfg files as the readme said, except I added a line
referencing another include folder that had .h files provided by my
instructor. When I switched machines, I wasn't very selective about wich
files I put there. When I narrowed it down to just those files that were
separate from Borlands included files, it compiled cleanly.
Thanks again Ed.
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|