Comment # 7
on bug 8775
from Roland Knall
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > This is "interesting" as autotools are supposed to use the same flag.
> > > Can you please build that particular file in verbose mode (on cmake created
> > > systems, that's "make ... VERBOSE=1 ...") once with cmake and once with
> > > autotools so I can compare the actual compiler calls and please include the
> > > error message as well.
> >
> > Before comparing actual compiler output, I would suggest something
> > different. What helped me was, that I deleted the build directory (I use an
> > out-of-source build directory) and reconfigured the setup. Also, do not copy
> > CMakeCache.txt, as it will contain switches.
> >
> > After that, everything got detected in the correct way.
>
> I not use the out-of-soruce build directory (i remember to already try to
> make a make clean and rebuild...)
For a more radical approach, either delete CMakeCache.txt or change the
compiler with cmake -DCMAKE_C_COMPILER=<path_to_new_compiler>
-DCMAKE_CXX_COMPILER=<path_to_new_c++_compiler> <src_directory>. Both should
trigger cmake to throw away all kept settings. The issue here is not residues
of the build itself (which would go away with make clean), but of the cmake
meta-build system. In principal this step is equivalent to deleting
config.status from autotools.
I would allways prefer to use an out-of-source build, which enables you to
easily retain a clean src-code repo.
You are receiving this mail because:
- You are watching all bug changes.