aMule Forum
English => Compilation problems => Topic started by: minage on November 30, 2007, 12:29:24 PM
-
Hi,
I have some problems with cvs, i can't compile any version.
I tried 28th 29-30...nothing.
Well, my steps:
1-downloaded the file from http://www.hirnriss.net/?area=cvs
2-tar xvjf aMule
3-./autogen.sh (no error)
4-./configure --enable-optimize (i tried --enable/disable-debug and with/without --prefix=)
config.status: creating po/Makefile.in
config.status: WARNING: po/Makefile.in.in seems to ignore the --datarootdir setting
config.status: creating Compilation.flags
config.status: WARNING: Compilation.flags.in seems to ignore the --datarootdir setting
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing default-1 commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
config.status: executing denoiser commands
Configure script has finished system check.
Configured aMule CVS for 'i686-pc-linux-gnu'.
aMule enabled options:
**** aMule Core ****
Prefix where aMule should be installed? /usr/local
Should aMule be compiled with i18n support? yes
Should aMule be compiled in debug mode? no
Should aMule be compiled with profiling? no
Should aMule be compiled with optimizations? yes
Should aMule be compiled with UPnP support? yes
Should aMule be compiled with IP2country support? yes
Should aMule monolithic application be built? yes
Should aMule daemon version be built? no
Should aMule remote gui be built? (EXPERIMENTAL) no
Crypto++ library/headers style? embedded
**** aMule TextClient ****
Should aMule Command Line Client be built? no
**** aMule WebServer ****
Should aMule WebServer be built? no
**** aMule ED2K Links Handler ****
Should aMule ED2K Links Handler be built? yes
**** aMuleLinkCreator ****
Should aMuleLinkCreator GUI version (alc) be built? no
Should aMuleLinkCreator for console (alcc) be built? no
**** aMule Statistics ****
Should C aMule Statistics (CAS) be built? no
Should aMule GUI Statistics (wxCas) be built? no
**** General Libraries and Tools ****
Should ccache support be enabled? no
Libraries aMule will use to build:
wxWidgets 2.8.4 (gtk2,shared)
crypto++ embedded
zlib 1.2.3
5-make
/usr/include/wx-2.8/wx/gdicmn.h: In member function 'wxStringToColourHashMap_wxImplementation_HashTable::Node** wxStringToColourHashMap_wxImplementation_HashTable::GetNodePtr(const wxString&) const':
/usr/include/wx-2.8/wx/gdicmn.h:544: warning: dereferencing type-punned pointer will break strict-aliasing rules
/usr/include/wx-2.8/wx/protocol/http.h: In member function 'wxStringToStringHashMap_wxImplementation_HashTable::Node** wxStringToStringHashMap_wxImplementation_HashTable::GetNodePtr(const wxString&) const':
/usr/include/wx-2.8/wx/protocol/http.h:21: warning: dereferencing type-punned pointer will break strict-aliasing rules
ECTag.cpp: At global scope:
ECTag.cpp:676: warning: unused parameter 'name'
/tmp/cc5xjWn9.s: Assembler messages:
/tmp/cc5xjWn9.s:6760: Error: unknown pseudo-op: `.weakref'
/tmp/cc5xjWn9.s:6761: Error: unknown pseudo-op: `.weakref'
/tmp/cc5xjWn9.s:6762: Error: unknown pseudo-op: `.weakref'
/tmp/cc5xjWn9.s:6763: Error: unknown pseudo-op: `.weakref'
/tmp/cc5xjWn9.s:6764: Error: unknown pseudo-op: `.weakref'
/tmp/cc5xjWn9.s:6765: Error: unknown pseudo-op: `.weakref'
/tmp/cc5xjWn9.s:6766: Error: unknown pseudo-op: `.weakref'
/tmp/cc5xjWn9.s:6767: Error: unknown pseudo-op: `.weakref'
/tmp/cc5xjWn9.s:6768: Error: unknown pseudo-op: `.weakref'
/tmp/cc5xjWn9.s:6769: Error: unknown pseudo-op: `.weakref'
/tmp/cc5xjWn9.s:6770: Error: unknown pseudo-op: `.weakref'
/tmp/cc5xjWn9.s:6771: Error: unknown pseudo-op: `.weakref'
/tmp/cc5xjWn9.s:6772: Error: unknown pseudo-op: `.weakref'
/tmp/cc5xjWn9.s:6773: Error: unknown pseudo-op: `.weakref'
make[7]: *** [libec_a-ECTag.o] Error 1
make[7]: Leaving directory `/home/enigma/Desktop/amule-cvs/src/libs/ec/cpp'
make[6]: *** [all] Error 2
make[6]: Leaving directory `/home/enigma/Desktop/amule-cvs/src/libs/ec/cpp'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/home/enigma/Desktop/amule-cvs/src/libs/ec'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/home/enigma/Desktop/amule-cvs/src/libs/ec'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/enigma/Desktop/amule-cvs/src/libs'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/enigma/Desktop/amule-cvs/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/enigma/Desktop/amule-cvs'
make: *** [all] Error 2
:'(
I'm having this trouble since i update my gcc from 3.4.6 to 4.1.2
before I got this error after launching make:
Scanner.cpp:527:5: warning: "YY_STACK_USED" is not defined
Scanner.cpp:1461:5: warning: "YY_ALWAYS_INTERACTIVE" is not defined
Scanner.cpp:1755:5: warning: "YY_MAIN" is not defined
./Scanner.l: In function `void LexFree()':
./Scanner.l:191: error: `yylex_destroy' was not declared in this scope
./Scanner.l:205:5: warning: "YY_STACK_USED" is not defined
./Scanner.l:191: warning: unused variable 'yylex_destroy'
Scanner.cpp: At global scope:
Scanner.cpp:1659: warning: 'void yy_fatal_error(const char*)' defined but not used
make[3]: *** [libmuleappcore_a-Scanner.o] Error 1
make[3]: Leaving directory `/tmp/src/amule/amule-cvs/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/src/amule/amule-cvs/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/src/amule/amule-cvs'
make: *** [all] Error 2
and I'm not the only one (i found the same problem on internet)
What can i do?
Thanks
Bye
-
OK, the second problem is caused by an old version of flex. Please use flex 2.5.33, old versions will not work correctly.
The first problem is most probably a compiler error, there are a couple of problems with gcc 4.1 I have heard of. Please upgrade to gcc 4.2, I don't experience errors with this version.
You could use llvm-gcc as well, but it is slower than gcc for compiling aMule.
-
about gcc, i'm a newbie so i don't feel well with compiling it, i'm waiting for an official tgz package for gcc 4.2.x so, nevermind, my gcc is came back to 3.4.6
then...
bash-3.2$ flex --version
flex version 2.5.4
bash-3.2$ flex++ --version
flex++ version 2.5.4
bash-3.2$
flex is already up to date ???
-
Actually it is more than ten years old. 4 < 33. ;)
-
ohh sorry, everytime i confuse 0x for x0 :D
so i thought 2.5.40 and not 2.5.04
ok, i'll try with new version...and i'll edit this post with news
EDIT:
Yeehh everythings done.
Now let' test ;)