This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Build error in ecos-current


Joshua Boyd wrote:

I have an ecos current checked out from august 20th.

In the file: packages/services/compress/zlib/current/src/zutil.h
line 458 extern const char * const z_errmsg[10]; /* indexed by 2-zlib_error */
/* (size given to avoid silly warnings with Visual C++) */


What I don't understand is why the const keyword is used twice.

My attention was drawn to this by the following build error:
/home/jdboyd/projects/sw/ecos-current/packages/services/compress/zlib/current/src/zutil.c:16:
conflicting types for `z_errmsg'
make: Leaving directory `/home/jdboyd/tmp/dmxTest_build'
/home/jdboyd/projects/sw/ecos-current/packages/services/compress/zlib/current/src/zutil.h:48:
previous declaration of `z_errmsg'

Now, it appears that neither file has changed in the last 3 months.


I'm using GCC 3.2.1. The ecoscentric provided binaries in fact. Must I upgrade to 3.4.1 to use the current CVS versions? I was planning on testing 3.4.1, but I wanted to take one thing at a time.



Using const twice says a const pointer to const data (so I believe).
This should be entirely OK.

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]