Jump to content

3bd0

Inactive Member
  • Posts

    194
  • Joined

  • Last visited

  • Days Won

    1
  • Feedback

    0%

3bd0 last won the day on January 2 2018

3bd0 had the most liked content!

1 Follower

About 3bd0

  • Birthday 02/05/1999

Informations

  • Gender
    Male
  • Country
    Australia

Recent Profile Visitors

1091 profile views

3bd0's Achievements

Community Regular

Community Regular (8/16)

  • Very Popular Rare
  • Dedicated
  • Reacting Well
  • First Post
  • Collaborator

Recent Badges

171

Reputation

  1. Sorry maybe I didn't explain myself clearly. I was asking about how to pass the information inside *args back to the callback. So in the function above, it's saving a reference to event (which is the function), but *args is just lost. so when self.eventOverInItem get called later on, it will be missing the arguments that were provided in *args. Or Am I missing something?
  2. Apologies if it's a stupid question, python is not my thing. But when I refactor it to *args, how do I then pass those arguments to the function? 0, row, j and captured by *args, but then what? should I just save them to a variable in SetOverInItemEvent and unpack them when the event is triggered? Or is there an easier way of doing it?
  3. There seem to be a small bug with DS trade. You can only trade 1 item at a time (even if you have more space). In exchange.cpp, find if (0 == s_vDSGrid[wBasePos]) Replace with if (0 == s_vDSGrid[wPos])
  4. What version of cef are you using? The only unusual thing I have found so far is a error file that seems to be dumped after the client crashes.
  5. Hi, Did anyone manage to use Cef (Chromium Embedded Framework) version 90 or newer with metin 2? While older versions work fine for me, newer version don't. When I open the browser the client just crash without any apparent reason. Thanks.
  6. It looks like mysql 5.7 is compiled with clang, while I compile my sources with g++. Is there any way to make mysql compile with gcc? I have version 4.8 installed
  7. Hi, I am updating my MySQL version to 5.7. I removed old mysql and installed the new version, then tried to recompile dp and game with the new libraries. I get some weird linker issues, tried to work it out but no luck. The output is: /usr/local/bin/ld: /usr/local/lib/mysql/libmysqlclient.a(sha2_password_common.cc.o): in function `sha2_password::Generate_scramble::Generate_scramble(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, sha2_password::Digest_info)': sha2_password_common.cc:(.text+0x30e): undefined reference to `std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::basic_string(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)' /usr/local/bin/ld: sha2_password_common.cc:(.text+0x31e): undefined reference to `std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::basic_string(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)' /usr/local/bin/ld: /usr/local/lib/mysql/libmysqlclient.a(sha2_password_common.cc.o): in function `generate_sha256_scramble': sha2_password_common.cc:(.text+0x72b): undefined reference to `std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::basic_string(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)' /usr/local/bin/ld: sha2_password_common.cc:(.text+0x73d): undefined reference to `std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::basic_string(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)' /usr/local/bin/ld: sha2_password_common.cc:(.text+0x833): undefined reference to `std::__1::__basic_string_common<true>::__throw_length_error() const' /usr/local/bin/ld: sha2_password_common.cc:(.text+0x83d): undefined reference to `std::__1::__basic_string_common<true>::__throw_length_error() const' collect2: error: ld returned 1 exit status gmake: *** [Makefile:82: ../db_r] Error 1 And this is my make file: Thanks.
  8. It wasn't removed. It moved to the top of the thread because I marked it as best answer.
  9. This worked! I copied all the devil libs from the 9.2 machine and compiled it and its working now perfectly! Will try to upgrade it later. I am guessing the static flag makes the linker pack every library needed into the binary, which makes it work on every machine even if that library is not installed, am I right? Is there any disadvantages to using the static flag vs dynamic linking?
  10. Getting tons of errors now in linking process [Hidden Content]
  11. I running and compiling it on the same machine. I tried adding the static flag, but the build failed as it couldn't find gtest library. I checked and I do have the shared lib (.so) but not the static one (.a). Tried googlin on how to build it, but couldn't find anything helpful.
  12. I removed all optimisation flags & removed the hackshield stuff as I don't have the source code for that to rebuild the lib. I updated gdb version to 9.1 as well. Now the game error out with a bus error. This is the output of bt full. #0 0x29073a85 in vtable for __cxxabiv1::__si_class_type_info () from /lib/libcxxrt.so.1 No symbol table info available. #1 0x28c33440 in ?? () from /usr/lib/libstdc++.so.6 No symbol table info available. Backtrace stopped: previous frame inner to this frame (corrupt stack?) Does anyone have any idea what is going on?
  13. I did update all packages and deleted everything in Extern except include/boost. The only thing I am not using the latest version for is cryptopp, I am suing cryptopp700 (I built it myself). But still getting a segmentation fault. Output of bt full is the following. I don't know about the tr1 namespace honestly, do you where that was used and how to fix it? Edit: This is the makefile now after edits [Hidden Content]
  14. This is the list of the command produced and I checked every single one of them, they all exist. libmd.so.6 => /lib/libmd.so.6 (0x28471000) libIL.so.1 => /usr/local/lib/libIL.so.1 (0x2848c000) libpng16.so.16 => /usr/local/lib/libpng16.so.16 (0x285a9000) libtiff.so.5 => /usr/local/lib/libtiff.so.5 (0x285d9000) libmng.so.1 => /usr/local/lib/libmng.so.1 (0x28647000) liblcms.so.1 => /usr/local/lib/liblcms.so.1 (0x286a1000) libjpeg.so.8 => /usr/local/lib/libjpeg.so.8 (0x286d8000) libz.so.6 => /lib/libz.so.6 (0x28761000) libssl.so.8 => /usr/lib/libssl.so.8 (0x28777000) libstdc++.so.6 => /usr/local/lib/gcc48/libstdc++.so.6 (0x287d1000) libm.so.5 => /lib/libm.so.5 (0x288bd000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x288ea000) libthr.so.3 => /lib/libthr.so.3 (0x288fb000) libc.so.7 => /lib/libc.so.7 (0x2891f000) libnvtt.so => /usr/local/lib/libnvtt.so (0x28a7d000) libjasper.so.4 => /usr/local/lib/libjasper.so.4 (0x28a93000) libc++.so.1 => /usr/lib/libc++.so.1 (0x28af0000) libcxxrt.so.1 => /lib/libcxxrt.so.1 (0x28bae000) liblzma.so.5 => /usr/lib/liblzma.so.5 (0x28bc8000) libjbig.so.2 => /usr/local/lib/libjbig.so.2 (0x28bec000) libcrypto.so.8 => /lib/libcrypto.so.8 (0x28bf8000) libnvimage.so => /usr/local/lib/libnvimage.so (0x28d89000) libnvmath.so => /usr/local/lib/libnvmath.so (0x28dab000) libnvcore.so => /usr/local/lib/libnvcore.so (0x28db0000) libImath-2_4.so.24 => /usr/local/lib/libImath-2_4.so.24 (0x28db7000) libIlmImf-2_4.so.24 => /usr/local/lib/libIlmImf-2_4.so.24 (0x28dc8000) libIex-2_4.so.24 => /usr/local/lib/libIex-2_4.so.24 (0x290a5000) libHalf-2_4.so.24 => /usr/local/lib/libHalf-2_4.so.24 (0x290fd000) libIlmThread-2_4.so.24 => /usr/local/lib/libIlmThread-2_4.so.24 (0x29140000) libIexMath-2_4.so.24 => /usr/local/lib/libIexMath-2_4.so.24 (0x29147000) gcc48 is included in the ports. I am planning to update it but sine this is the version I used on 9.2, wanted to make it work with it first then update from there.
×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.