By any chance, are you building on Windows and using WSL for your source control or editing?
If you are using 62.0, I believe it still compiles with Microsoft Visual Studio. There was an update to Windows that changed the default WSL case sensitivity of file system. If this is your circumstance, moving to a more recent version of Firefox might help as it uses clang even on windows. There are also some tips here https://developercommunity.visualstudio.com/content/problem/276297/clexe-breaks-with-case-sensitive-paths.html If you are using linux, I'm not sure what the issue might be. On Saturday, December 29, 2018 at 12:58:17 PM UTC-5, pubkeypin wrote: > Does someone has an idea, why a .cpp file starting with an uppercase > character fails a browser build, while using lowercase works? > > > The only changes between both situations are the edited name (only the > first letter) of this file and the corresponding lower cased first > letter for this file in the "UNIFIED_SOURCES" of > security/manager/ssl/moz.build . > > This might be related to the preprocessor (?) because, when failing, the > last line of > security/manager/ssl/.deps/Unified_cpp_security_manager_ssl0.o.pp > in the build directory is a reference to my .cpp file. > > The build result remains in both scenarios the same, when flipping > the first letter of the .h file and the header guard lines > in this file. > > > As i'm a beginner regarding nearly everything, please assume dumb > mistakes and lack of knowledge on my side and direct me to a more > appropriate channel, if necessary. > > Currently this happens with source-code version from 62.0 > > > Thanks for any pointers! > > pubkeypin _______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
