[DiscordArchive] It may not be the cause in your case. Did you try deleting the build folder and doing a fresh compil
[DiscordArchive] It may not be the cause in your case. Did you try deleting the build folder and doing a fresh compil
Original source
It may not be the cause in your case. Did you try deleting the build folder and doing a fresh compile?
rektbyfaith
10-10-2023, 08:33 PM #1Archived author: Revision • Posted: 2023-10-10T20:33:44.634000+00:00
Original source
It may not be the cause in your case. Did you try deleting the build folder and doing a fresh compile?
Original source
No, but I'll do that now : )
rektbyfaith
10-10-2023, 08:33 PM #2Archived author: ritzmenardi • Posted: 2023-10-10T20:33:53.534000+00:00
Original source
No, but I'll do that now : )
Original source
If you didn't clear the cache after updating the packages, and maybe didn't even compile the core after doing so, it will cause this issue because it's still using the old libraries prior to the update.
rektbyfaith
10-10-2023, 08:34 PM #3Archived author: Revision • Posted: 2023-10-10T20:34:54.935000+00:00
Original source
If you didn't clear the cache after updating the packages, and maybe didn't even compile the core after doing so, it will cause this issue because it's still using the old libraries prior to the update.
Original source
The cache as in the build directory? That makes sense to me!
rektbyfaith
10-10-2023, 08:36 PM #4Archived author: ritzmenardi • Posted: 2023-10-10T20:36:12.790000+00:00
Original source
The cache as in the build directory? That makes sense to me!
Original source
Probably needed to update the makefile or something
rektbyfaith
10-10-2023, 08:36 PM #5Archived author: ritzmenardi • Posted: 2023-10-10T20:36:29.275000+00:00
Original source
Probably needed to update the makefile or something
Original source
Still didn't work - I uninstalled mysql++ and mysql++-devel and then recompiled and still same issue : (
rektbyfaith
10-10-2023, 08:40 PM #6Archived author: ritzmenardi • Posted: 2023-10-10T20:40:34.630000+00:00
Original source
Still didn't work - I uninstalled mysql++ and mysql++-devel and then recompiled and still same issue : (
Original source
I think this line here is my issue
![[Image: image.png?ex=690c5f28&is=690b0da8&hm=5fe...f74c99749&]](https://cdn.discordapp.com/attachments/284406375495368704/1161403081385312366/image.png?ex=690c5f28&is=690b0da8&hm=5fe5da3a7aae51f2aa22babf345cbe8594d77699364be20dd01f759f74c99749&)
rektbyfaith
10-10-2023, 08:41 PM #7Archived author: ritzmenardi • Posted: 2023-10-10T20:41:12.445000+00:00
Original source
I think this line here is my issue
Original source
So if my intuition is correct then somewhere the authserver is being told to use a different version of mysql (MariaDB) than the compilation process. But I don't think I ever specified which version to use.
rektbyfaith
10-10-2023, 08:52 PM #8Archived author: ritzmenardi • Posted: 2023-10-10T20:52:45.242000+00:00
Original source
So if my intuition is correct then somewhere the authserver is being told to use a different version of mysql (MariaDB) than the compilation process. But I don't think I ever specified which version to use.
Original source
It uses the one set as default. The typical answer to this issue is: use mysql instead of mariadb. With the issues that always pop up when it comes to azerothcore just makes it easier to switch. I'm not super happy about having to run both mariadb and mysql but the issues related only to azerothcore is just worse to deal with.
rektbyfaith
10-10-2023, 09:08 PM #9Archived author: Revision • Posted: 2023-10-10T21:08:23.370000+00:00
Original source
It uses the one set as default. The typical answer to this issue is: use mysql instead of mariadb. With the issues that always pop up when it comes to azerothcore just makes it easier to switch. I'm not super happy about having to run both mariadb and mysql but the issues related only to azerothcore is just worse to deal with.
1 Guest(s)
1 Guest(s)