Steve Hay wrote:
Unfortunately something seems to be amiss. The bcc smoke (Fri night)
and the gcc smoke (Sat night) both failed with rather unhelpful logs.
I will investigate to see what the problem is.
This diff fixes the gcc build and removes 1 of 2 errors in the bcc build:
==== //depot/maint-5.8/perl/util.c#85 - c:\p5p\maintperl\util.c ====
@@ -1470,7 +1470,7 @@
#else /* WIN32 || NETWARE */
void
-Perl_my_setenv(pTHX_ const char *nam, char *val)
+Perl_my_setenv(pTHX_ char *nam, char *val)
{
register char *envstr;
const int nlen = strlen(nam);
(This just makes the signature in the Win32 case consistent with the
other cases on line 1399 and the prototype in proto.h. BCC and GCC
regard the inconsistency as an error, but VC++ only warned about it!)
BCC additionally regards an inconsistency in Perl_find_script() as an
error (whereas GCC and VC++ only warn):
Perl_find_script(pTHX_ char *scriptname, bool dosearch, char
**search_ext, I32 flags)
{
...
const char *exts[] = { SEARCH_EXTS };
const char **ext = search_ext ? search_ext : exts;
In bleadperl, the search_ext argument is a const char **. Without the
const qualifier BCC complains:
Error E2354 ..\util.c 2761: Two operands must evaluate to the same type
in function Perl_find_script
So it looks like you just need to continue integrating more consting
changes, and hopefully it'll all come out in the wash eventually.
------------------------------------------------
Radan Computational Ltd.
The information contained in this message and any files transmitted with it are
confidential and intended for the addressee(s) only. If you have received this
message in error or there are any problems, please notify the sender
immediately. The unauthorized use, disclosure, copying or alteration of this
message is strictly forbidden. Note that any views or opinions presented in
this email are solely those of the author and do not necessarily represent
those of Radan Computational Ltd. The recipient(s) of this message should check
it and any attached files for viruses: Radan Computational will accept no
liability for any damage caused by any virus transmitted by this email.
