Re: [Firebird-devel] Error compiling ScanDir.cpp

[Jim S. <ja...@ne...>]

Dimitry Sibiryakov wrote:

>  Hello, All!
>
>  How can I fix this:
>
>g++  -DBOOT_BUILD -I../src/include/gen -I../src/include -I../src/vulcan -I../src/../extern/icu/include -ggdb -march=i586 -mcpu=i686 -DMINGW -mno-cygwin -Wall -Wshadow -Wundef -pedantic -Wno-long-long -Wno-unused-variable -Wno-unknown-pragmas -Wno-parentheses -Wno-switch -fmessage-length=0 -Dlint -DWIN32_LEAN_AND_MEAN -MMD -mthreads -DDEV_BUILD -c ../src/config/ScanDir.cpp -o ../temp/boot/config/ScanDir.o
>In file included from ../src/config/ScanDir.cpp:42:
>../src/config/ScanDir.h:34:5: warning: "_MSC_VER" is not defined
>  
>
This is a standard boilerplate generated by Visual Studio 6 and 
earlier.  I haven't a clue why g++ is giving a diagnostic.  Since 
"#pragma once" isn't portable, feel free to remove the complete 
conditional block around it.  There are dozens of other modules in 
Vulcan can contain the same boilerplate.

>In file included from ../src/config/ScanDir.h:47,
>                 from ../src/config/ScanDir.cpp:42:
>../src/vulcan/JString.h: In member function `void JString::allocSpace(int)':
>../src/vulcan/JString.h:100: warning: declaration of `length' shadows a member of `this'
>  
>
It isn't ambiguous, but if you don't like the inappropriate warning, 
change the name of the parameter.

>../src/config/ScanDir.cpp: In member function `const char* ScanDir::getFilePath()':
>../src/config/ScanDir.cpp:109: ambiguous overload for `JString + CHAR[260]' operator
>../src/config/ScanDir.cpp:109: candidates are: operator+(int, CHAR*) <built-in>
>../src/vulcan/JString.h:86:                 JString operator+(const JString&, const char*)
>../src/vulcan/JString.h:86:                 JString operator+(const JString&, const char*)
>make[2]: *** [../temp/boot/config/ScanDir.o] Error 1
>  
>

Serious, I don't know.  The line numbers don't match the Vulcan version 
and concatenation apparently responsible for the error was replaced with 
a call to Format.  But event then, the string in struct dirent should be 
defined.  I also don't understand where "operator+(int, CHAR*) 
<built-in>" came from.  It isn't part of the language and, as far as I 
can tell, wasn't included.

-- 

Jim Starkey
Netfrastructure, Inc.
978 526-1376