aMule Forum
English => Compilation problems => Topic started by: Vollstrecker on July 04, 2009, 10:20:29 PM
-
Hi,
starting with Rev 9630 I get the following error:
i486-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../../.. -D__DEBUG__ -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC -DUSE_WX_EXTENSIONS -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -g -W -Wall -Wshadow -Wundef -ggdb -fno-inline -fmessage-length=0 -pthread -c -o alc-ed2khash.o `test -f 'ed2khash.cpp' || echo './'`ed2khash.cpp
ed2khash.cpp:50: error: ‘wxS’ was not declared in this scope
make[5]: *** [alc-ed2khash.o] Error 1
make[5]: Leaving directory `/usr/src/amule/testbuild/src/utils/aLinkCreator/src'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/usr/src/amule/testbuild/src/utils/aLinkCreator'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/usr/src/amule/testbuild/src/utils'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/amule/testbuild/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/amule/testbuild'
make: *** [all] Error 2
I crosschecked with current 9697 fresh checkout with the same result. I can see some changes for wx-2.9 in this revs, but I can't imagine that this was unrevealed for such a long time. I for myself didn't change the env between these two revs.
-
You should use wxWidgets >= 2.8.8. wxS is not defined in 2.8.7.
(Alternative: Convince developers that supporting people using an outdated (2.8.8 is out for more than a year) wxWidgets version is worth it.)
Edit: >= not =>
-
Instead of convincing devs to support debian at all, I'll just do new packages.
-
It's more about convincing debian to support devs. 2.8.7 is awfully old.
-
You kniow the policy. They won't update the stable distro. And dato won't make enough pressure to get it into testing or sid.
-
Reason for the change was getting errors like
alcc.h:67: error: cannot convert ‘const wchar_t*’ to ‘const char*’ in initialization
with wx 2.9
-
Actually we might change completely. Unless someone with better insight (Kry?) tells us why this would be a bad idea.
But it does make sense to use wxS() in the new code or, rather, not
use wxT/_T any more [...]
¹ Look at the google cache version for the message "wxS(): replacement of wxT/_T in the common code"
-
Pkg build in progress, so no problem. Maybe mention this next time somewhere.