Re: [Svxlink-devel] SvxLink 080102 released
Brought to you by:
sm0svx
From: Tobias B. <sm...@us...> - 2008-01-05 11:16:06
|
On Wednesday 02 January 2008 22:01:27 Sid Boyce wrote: > OpenSUSE has changed to gcc version 4.3.0 20071129 (experimental) [trunk > revision 130511] (SUSE Linux) from gcc-4.2. Hmmm. Using an experimental compiler in a released operating system seem a bit strange to me. Have you added a repository that is not part of the main track that could have caused this or did Novell actually change the compiler all of a sudden? > Header files seem have to > been rearranged with some files in async needing "#include <cstring>", > memcpy, memset and others are affected. Got as far as > -------------- async/cpp -------------- > make[3]: *** No rule to make target `pair.h', needed by > `depend/AsyncCppApplication.dpp'. Stop. > make[2]: *** [all] Error 2 > make[1]: *** [all] Error 2 > make: *** [all] Error 2 > Included "/usr/include/c++/4.2.3/backward/pair.h \" in the above file, > still doesn't see it. > BTW, this is a x86_64 build being attempted. You should not have to use include files from another compiler version (4.2.3). There must be a pair.h (or pair without .h) in 4.3 as well. In the worst case, pair is gone. Then you're in trouble. Remember to use "make realclean" before "make" after you change something. > I'm wondering why folk are moving away from GNU make in favour of cmake > etc., tools which seem to be less intuitive and more complicated -- > there has got to be a good reason that isn't obvious. If you mean that SvxLink use cmake, it's not so. The makefiles are pure gmake. They are just a bit complicated. In large software projects, just writing a pure makefile in each directory soon get out of hand and it's hard to maintain. There are two ways to handle this, auto-generation (automake) or writing a makefile structure that centralize the main makefiles. I chose the latter. Automake is probably better for portability though so I'll try it some day. 73 de SM0SVX / Tobias |